Spiral Model Advantages and Disadvantages

Spiral Model is developed by Barry Boehm. Its emphasis is on a continuous reassessment of the risks and combining iterative and sequential approaches. Due to continuous emphasis on risk analysis this model is relevant to the realities of software development.

Risk Handling in Spiral Model:

A risk is an unexpected consequence that could endanger the successful execution of a software project. This risk can be reduced by establishing an access subsystem prototype and experimenting with the exact access rate. This model provides direct help dealing with risks by enabling the establishment of a prototype at every stage of the software development.

Phases of Model:

This model is divided into four phases or quadrants which are as:

• Quadrant 1:
  • Features of the product are identified on the difficulty of the risk.
  • Identified features are implemented and form the objective of the phase.
  • Objectives are investigated, elaborated, and analyzed.
  • Possible alternative solutions are proposed.
• Quadrant 2:
  • By developing an appropriate prototype best possible alternative solutions are evaluated.
• Quadrant 3:
  • Developing and verifying the next level of the product.
  • Identified features are implemented and the next version of the product is available.
• Quadrant 4:
  • Reviewing the result of stages traversed far with the customer and planning the next iteration along the spiral
  • Different Features of the product can be developed simultaneously to make the model more efficient,

Advantages of Model:

• For Variety of Situations model is very flexible such as reuse, component-based development, and prototyping.
• For every spiral risk analysis is performed as it is an integral part of the life cycle which leads to an increase in confidence in the project.

Disadvantages of Spiral Model:

• Knowledgeable and experienced staff is required.
• For developers, it is a more complicated and risk-driven model.

When to Use Spiral Model:

• The spiral model is well suited to the development of technically complex projects.
• It’s useful when risks are harder to know at the beginning of a project but are probably to arise as the work proceeds.