Spiral Model Used In Software Development

Introduction

Software Process Model Articles Series,

The spiral model combines the idea of iterative development with the controlled and systematic aspects of the first waterfall model.

Spiral Model Design

Spiral Model has four phases. The software development process has repeatedly passed from these phases called iterations. It allows us to release the product in iteration.

Step 1. Identification

This phase includes the identification of system requirements by continuously communicating with customers and developers and Business analysts (BA). This phase begins with the gathering of business requirements of the system in the baseline of the spiral. In the subsequent spiral, when the product grows up, the subsystem requirement and unit requirements gather in this phase.

Step 2. Design

The design phase begins with the conceptual design in the baseline of the spiral model. It involves the architectural and logical design of the module, physical design, and final product in the subsequent spiral.

Step 3. Build

The constructed phase refers to the production of the actual product in the baseline. We just construct the conceptual design of the product from customer feedback. Then the subsequent spiral is the clarity of requirement and design details; a working model of software is called build with a version number.

Step 4. Evaluation of Risks

Risk Analysis involves identifying and estimating, and monitoring the technical feasibility and management risks. At the end of the software development, process testers test the build and give it to the customer for evaluation, and the customer provides feedback.

Applications

Spiral Model is widely used in the software development industry. Given below points explains the usage of the spiral model in the industry.

For medium to high-risk software projects.
Major changes are expected during the development phase
Requirements are complex and need evaluation to get more clarity

Advantages of the Iterative Model

Changing requirements at any stage can be accommodated
The spiral model allows us to make extensive use of the prototype.
Users see the actual outcomes early due to the stage of the spiral
Development is divided into smaller tasks and risky parts. This makes the development easy and better for risk management
The requirement can be gathered more accurately

Disadvantages of the Iterative Model

Management of all activities of the software product is more complex
Software development is more complex
Many stages of the spiral model need more and excessive documentation
Not Suitable for small and less risky projects.