STLH:

"THE BEST WAY TO MAKE YOUR DREAMS COME TRUE IS TO WAKE UP..."

Search This Blog

Spiral Model Development Process

 

Spiral Model is a combination of a waterfall model and iterative model. Each phase in spiral model begins with a design goal and ends with the client reviewing the progress. 

This model is also known as Iterative/ Intended Model.

Spiral model starts with a small set of requirement and goes through each development phase for those set of requirements. The software engineering team adds functionality for the additional requirement in every-increasing spirals until the application is ready for the production phase.

This model was defined by Barry Boehm in the year 1986.

 

 

The Spiral model is a risk-driven Software Development Process model. This model process combines the advantages of Top-down and Bottom-up approach concept.

 

Different phases of Spiral model Software Development Cycle

  • Objectives determination and identify alternative solutions - Requirements are gathered from the customers and the objectives are identified, elaborated and analyzed at the start of every phase. Then alternative solutions possible for the phase are proposed in this quadrant.   

  • Identify and resolve Risks - During the second quadrant all the possible solutions are evaluated to select the best possible solution. Then the risks associated with that solution is identified and the risks are resolved using the best possible strategy. At the end of this quadrant, Prototype is built for the best possible solution. 

  • Develop next version of the Product - During the third quadrant, the identified features are developed and verified through testing. At the end of the third quadrant, the next version of the software is available. 

  • Review and plan for the next Phase - In the fourth quadrant, the Customers evaluate the so far developed version of the software. In the end, planning for the next phase is started.


Spiral Model Advantages:

  • Spiral Model is the best development model to follow due to the risk analysis and risk handling at every phase. 

  • Additional functionality or changes can be done at a later stage.

  • Cost estimation becomes easy as the prototype building is done in small fragments

  • There is always a space for customer feedback.

 

Spiral Model Disadvantages:

  • For its smooth operation spiral model protocol needs to be followed strictly.

  • Risk of not meeting the schedule or budget.

  • Documentation is more as it has intermediate phases, so it is time consuming process. 

  • It works best for large projects only also demands risk assessment expertise. It is not advisable for smaller project, it might cost them a lot