Risk Handling in Spiral Model
A risk is any adverse situation that might affect the successful completion of a software project. The most important feature of the spiral model is handling these unknown risks after the project has started. Such risk resolutions are easier done by developing a prototype.
- The spiral model supports coping with risks by providing the scope to build a prototype at every phase of software development.
- The Prototyping Model also supports risk handling, but the risks must be identified completely before the start of the development work of the project.
- But in real life, project risk may occur after the development work starts, in that case, we cannot use the Prototyping Model.
- In each phase of the Spiral Model, the features of the product dated and analyzed, and the risks at that point in time are identified and are resolved through prototyping.
- Thus, this model is much more flexible compared to other SDLC models.
What is Spiral Model in Software Engineering?
The Spiral Model is one of the most important Software Development Life Cycle models. The Spiral Model is a combination of the waterfall model and the iterative model. It provides support for Risk Handling. The Spiral Model was first proposed by Barry Boehm. This article focuses on discussing the Spiral Model in detail.
Table of Content
- What is the Spiral Model?
- What Are the Phases of Spiral Model?
- Risk Handling in Spiral Model
- Why Spiral Model is called Meta Model?
- Advantages of the Spiral Model
- Disadvantages of the Spiral Model
- When To Use the Spiral Model?
- Conclusion
- Questions For Practice
- Frequently Asked Questions related to Spiral Model – Software Engineering
Contact Us