Spiral Model in Software Testing

This section will discuss various models for testing. Definitions of these models will differ. However, the fundamental principles are agreed on by experts and practitioners alike. There are many models used to describe the sequence of activities that make a Systems Development Life Cycle (SDLC). SLDC is used to describe activities of both development and maintenance work.

Developed by Barry Boehm in 1988. it provides the potential for rapid development of incremental versions of the software. In the spiral model, software is developed in a series of incremental releases. During early iterations , the incremental release might be a paper model or prototype.
Each iteration consists of
Planning, Risk Analysis, Engineering, Construction & Release & Customer Evaluation.

• Customer Communication:
Tasks required to establish effective communication between developer and customer.
• Planning:
Tasks required to define resources, timelines, and other project related information.
• Risk Analysis:
Tasks required to assess both technical and management risks.
• Engineering:
Tasks required to build one or more representatives of the application.
• Construction & Release:
Tasks required to construct, test, install and provide user support (e.g., documentation and training)
• Customer evaluation:
Tasks required to obtain customer feedback based on evaluation of the software representations created during the engineering stage and implemented during the installation state.