Javatpoint Logo
Javatpoint Logo

Spiral Model

The Spiral Model is one of the most essential Software Development Life Cycle models, that guides Risk Handling. In its diagrammatic image, it looks like a spiral with several loops. The precise number of loops of the spiral is unknown and may vary from project to project. Every loop of the spiral is known as Phase of the software development process. The exact number of phases required to develop the product can change by the project manager depending upon the project risks. Because the project manager dynamically defines the number of stages, so the project manager has a crucial role to develop a product using the spiral model.

Spiral Model

The various phases of Spiral model are as follows:

1. Planning: This phase starts by collecting the requirements from the business. In this phase, classifying of the system requirements and unit requirements are done. By continuing communication between the customer and the analyst, it includes the conception of system requirements. And in the end, the product is deployed.

2. Design: The design phase starts from the base and includes the architectural, logical design of modules, physical product design and final design in a continuous spiral.

3. Construct or build: In every spiral, construct refers to the development of the final software product. In the spiral, when the product just imagined and the design is developed, a Proof of Concept is developed to get the user's feedback. After that, a working model which is known as build is developed with a specific version number and this version sent to the users to get the feedback.

4. Evaluation and Risk analysis: The risk analysis phase includes distinctive, estimating and observing technical feasibility. When testing the build, at the starting of the first creation, the user evaluates the software and provides feedback. Based on the client assessment, development method enters the next iteration and subsequently follows the linear approach to implement the feedback provided by the user. The method of repetition in the spiral model runs with the software throughout life.

When to use Spiral Model?

  • When deliverance is required to be frequent.
  • When the project is large
  • When requirements are unclear and complex
  • When changes may require at any time
  • Large and high budget projects

Advantage(Pros) of Spiral Model:

  • Highly flexible Model
  • Focus on Documentation Control
  • Works well for complex lifestyle
  • Monitoring is easy and effective/li>
  • Fast and cost-effective development

Disadvantage(Cons) of Spiral Model:

  • Not a perfect fit for less or low-risk projects
  • Success may depend hugely on the risk analysis
  • The risk analysis side of the project may require a specialist.
  • Can be expensive to implement.

Next TopicV-model

Please Share

facebook twitter google plus pinterest

Learn Latest Tutorials


B.Tech / MCA