Spiral Model generally shows the repetitive nature of the prototyping model and control proper well-defined approaches of the linear sequential model. The spiral model is also known to be a meta-model because all the other process models are included in the spiral model.
The waterfall model is also represented by the single loop of the spiral model. To develop the prototype before the establishment of the actual product, the prototyping approach is used by the spiral model. The evolutionary model is also supported by the spiral model as iterations along the spiral represent evolutionary levels, using which a complete system can be built. Risk reduction can be done in a spiral model using a prototyping approach. From the waterfall model, the systematic proper development approach is adopted.
For obtaining the project requirements, customer communication is very important and essential in the spiral model, the WIN-WIN model also suggests and supports well and proper communication with the customer. In actual practice, the process of negotiation which simply means to compromise has to be faced by the customers and developers. When both sides agree, only then successful negotiation occurs. This is called the WIN-WIN situation.
- Customer’s win means –
Obtaining the system that fulfill most of the requirements of customers.
- Developer’s win means –
Getting the work done by fulfilling the realistic requirements of customers in a given deadline and achievable budgets.
At the beginning of each pass of the spiral, the negotiation activities are carried out in a WIN-WIN spiral model.
Various activities that can be carried out in a WIN-WIN spiral model are shown in the following diagram –
- Identification of ‘stakeholders’.
- Determination of stakeholders to make great efforts to achieve or obtain a win condition.
- Negotiations of stakeholders struggling vigorously for win condition. Software project team conciliate for a win-win result with concern. Then determine next level objectives, constraints, and alternatives.
- Evaluation of the process and product and then analyzing and resolving or reducing the risks to make it easy.
- Defining the next level of product and process for proper working.
- Validation of process and product definitions is must.
- Reviewing of the product and giving the necessary and important comments on it.
Three anchor points are available that can be defined in the WIN-WIN spiral model that are given below –
- Life Cycle Objective (LCO) –
LCO defines the objectives that are essential for activities of software engineering.
- Life Cycle Architecture (LCA) –
LCO defines the software architectures that can be produced with all the objectives that are set.
- Initial Operational Capability (IOC) –
IOC represent the software with all the initial required operational capabilities.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Difference between Waterfall Model and Spiral Model
- Difference between Prototype Model and Spiral Model
- Difference between Spiral model and Incremental model
- Difference between RAD Model and Spiral Model
- Difference between V-model and Spiral model
- Stages of Defect Management Process
- Various Phases of RAD Model
- Software Engineering | Spiral Model
- Advantages and Disadvantages of using Spiral Model
- Software Engineering | Pham-Nordmann-Zhang Model (PNZ model)
- Difference between Waterfall model and Incremental model
- Difference between V-model and Waterfall model
- Difference between RAD Model and Waterfall Model
- Difference between Agile Model and V-Model
- Difference between Prototype Model and RAD Model
- Difference between RAD Model and Incremental Model
- Difference between Prototype Model and Incremental Model
- Difference between Waterfall model and Prototype model
- Difference between V-model and Incremental model
- Difference between V-model and RAD model
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to firstname.lastname@example.org. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.