Timing analysis in OO system life-cycles

The paper discusses the role of timing analysis through the whole system life cycle. It is suggested that the handling of non functional requirements, especially timing requirements, should be regulated by a life cycle model in the same way as other system development activities. Timing analysis should first be applied at the requirements phase and continued, in different forms and with different objectives, right up until the retirement phase. The feasibility and necessity of timing analysis in each stage of the lifecycle is then discussed. A set of procedures is proposed based on GOOSE (Guidelines for Object Oriented Software Engineering) and TOM (Timed Object Modelling). The paper concludes by considering the application of these techniques in the design and development of a case based reasoning tool-Bridge.