What is Spiral Model?When to use spiral model?Advantages & disadvantages
In the Spiral Model development of software is carried out in part wise manner or iterative manner.
In Spiral Model requirement changes can be handled in two phases :
Minor Change: In the same iteration we carry out changes plus add new features. Minor changes do not impact the design.
Major Changes: Separate iteration is carried out in case of major changes and the previous changes are destroyed. Major changes impact the design.
3. Let us understand the Spiral Model with the help of the figure illustrated below.
Requirement Collection :
Coding: In this phase, the actual development of software is done.
Testing: In this phase Module which is developed are tested and if any bugs are found are reverted back to developers so that they can fix it.
- When the requirement is given part by part or in iterative manner spiral model is best suitable.
- When the requirement is unclear.
- When changes can occur at any time.
- Every phase is being tested.
- Requirement changes can be handled easily.
- At the end of every iteration, a demo is given to customer.
- It is time-consuming.
NOTE: In Spiral model after every iteration demo is given to the customer and inputs are taken from the customer and based on that input new changes are done and
if no inputs or change are mentioned by the customer then the next feature development starts.
Comments
Post a Comment