The spiral model is a systems development lifecycle model used for large, expensive, and complicated projects. It combines elements of prototyping and risk analysis by iterating through steps of defining requirements, designing, prototyping, testing, and evaluating. This iterative process allows for refinement of prototypes and risk assessment until the customer is satisfied, at which point the final system is constructed. The spiral model is advantageous for risk avoidance but costly, requiring expertise in risk analysis.

1. EVOLUTIONARY MODEL, take the concept of “evolution” into the engineering paradigm. Therefore
Evolutionary model are iterative. They are built in a manner that enables software engineers to develop
increasingly more complex versions of the software.
SPIRAL MODEL
The spiral model, also known as the spiral lifecycle model, is a systems development lifecycle
SDLC) model used in information technology (IT). This model of development combines the
features of the prototyping model. The spiral model is favored for large, expensive, and
complicated projects.
The steps in the spiral model can be generalized as follows:
1. The new system requirements are defined in as much detail as possible. This usually
involves interviewing a number of users representing all the external or internal users and
other aspects of the existing system.
2. A preliminary design is created for the new system.
3. A first prototype of the new system is constructed from the preliminary design. This is
usually a scaled-down system, and represents an approximation of the characteristics of
the final product.
4. A second prototype is evolved by a fourfold procedure: (1) evaluating the first prototype
in terms of its strengths, weaknesses, and risks; (2) defining the requirements of the
second prototype; (3) planning and designing the second prototype; (4) constructing and
testing the second prototype.
5. At the customer's option, the entire project can be aborted if the risk is deemed too great.
Risk factors might involve development cost overruns, operating-cost miscalculation, or
any other factor that could, in the customer's judgment, result in a less-than-satisfactory
final product.
6. The existing prototype is evaluated in the same manner as was the previous prototype,
and, if necessary, another prototype is developed from it according to the fourfold
procedure outlined above.
7. The preceding steps are iterated until the customer is satisfied that the refined prototype
represents the final product desired.
8. The final system is constructed, based on the refined prototype.
9. The final system is thoroughly evaluated and tested. Routine maintenance is carried out
on a continuing basis to prevent large-scale failures and to minimize downtime

2. Diagram of Spiral model:
Advantages of Spiral model:
High amount of risk analysis hence, avoidance of Risk is enhanced.
Good for large and mission-critical projects.
Strong approval and documentation control.
Additional Functionality can be added at a later date.
Software is produced early in the software life cycle.
Disadvantages of Spiral model:
Can be a costly model to use.
Risk analysis requires highly specific expertise.
Project’s success is highly dependent on the risk analysis phase.
Doesn’t work well for smaller projects.
When to use Spiral model:
When costs and risk evaluation is important
For medium to high-risk projects
Long-term project commitment unwise because of potential changes to economic
priorities
Users are unsure of their needs
Requirements are complex
New product line
Significant changes are expected (research and exploration)