ABSTRACT

The life-cycle development methodology consists of distinct phases from requirements to coding. Life-cycle testing means that testing occurs in parallel with the development life cycle and is a continuous process. Testers need to know the objectives of the software product, how it is intended to work, how it actually works, the development schedule, any proposed changes, and the status of reported problems. Testing can be difficult unless a systematic process has been established for developing prototypes. Some include the following: The following describes a methodology to reduce development time through reuse of the prototype and knowledge gained in developing and using the prototype. The team should emphasize the results of the prototype and its impact on development tasks still to be performed. The risk analysis should include the problems and changes that incorporated into the prototype and the probable impact that they would have on development of the full system and subsequent operation.