RapiTime can be used at a number of stages during the lifecycle of a project.

• Early in the life cycle, RapiTime can give indications of the WCET and profiling information about the software. In particular, using RapiTime before the target hardware is available by executing the software on a simulator can give important feedback to developers on how efficient their software is, and early indications to integration teams on the processing requirements of software.
• During active development, RapiTime is used for regression testing software, monitoring how the execution times vary week by week. This allows the project managers to understand and investigate whether particular components are exceeding processing budgets and whether the resulting system will suffer deadline misses and performance problems.
• RapiTime is used extensively for optimization support. RapiTime demonstrates where the key opportunities for optimization are. RapiTime focuses on the worst case, not the average case: this capability ensures that the software executes on time, every time.
• Late in development, calculation and validation of WCET is provided by RapiTime. WCET is vital for understanding and ensuring correct real-time behaviour.