It is also called win-win spiral model because in this model customer and designer daily interact with each other so when a part of the project is complete in the first-day customer think that I win because some work has been done on the project and will be definitely complete within the time limit and designer think I had complete my today work and some part is complete and I win.
- This model is used for high-risk projects. It provides the potential for the rapid development of an incremental version of the software.
- In the spiral model, the software is developed in a series of incremental releases.
- The spiral model combines the idea of iterative development with the systematic, controlled aspects of the waterfall model.
- This Spiral model is a combination of the iterative development process model and sequential linear development model i.e. the waterfall model with a very high emphasis on risk analysis.
- It allows incremental releases of the product or incremental refinement through each iteration around the spiral.
Phases of the spiral model are:-
- Requirement gathering
- Analysis
- Design
- Coding
- Testing
- Maintenance
1. Requirement gathering:- Requirement gathering is the first step of the spiral model. It is a very important step in the spiral model. In requirement gathering step of the spiral model, the developer and the customer do a meeting to discuss the requirement of the project or software. Or we can say, that in this step of the spiral model, the customer tells about
its requirement regarding the project or software.
2. Analysis:- Analysis is the second step of the spiral model. It is also a very important step in the spiral model. This step is done after the requirement gathering. In the analysis, the developer collects all information about the project or software. Or we can say that the developer collects all content which helps the developer to build the project.
3. Design:- This is the third step of the spiral model. It is also a very important step in the spiral model. This step is done after the analysis step of the spiral model. In the design step of the spiral model, the developer creates written documentation of the project or software. This written documentation is called SRS documentation. The SRS documentation is helpful to explain the project or software to the customer.
4. Coding:- It is the fourth step of the spiral model or we can say, that coding is the fourth step of the spiral model. It is also a very important step in the spiral model. This step takes place after the third step or the design step of the spiral model. In this step programmer or developer, actually do programming or coding. The developer starts programming takes SRS documentation as input. In this, the programmer starts programming by seeing the documentation.
5. Test:- It is the fifth step of the spiral model. or we can say, that the test is the fifth step of the spiral model. It is also a very important step in the spiral model. This step of the spiral model is done after the fourth step or after the coding step of the spiral model. In this step of the spiral model, the developer checks the project that it is working or not. And check that there is an error in the project or not. And see that the project or software is working properly or not. Overall basically we can say, that in this step of the spiral model developer make sure that the project fine or not.
6. Maintenance:- It is the sixth step of the spiral model. or we can say, that maintenance is a sixth step of the spiral model. It is also the last step of the spiral model. It is also a very important step in the spiral model. Maintenance is the phase/step to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment. Maintenance, phase/step is used to update the project/software.
In the spiral model after the maintenance of the project the developer handover the project to the customer. If the customer is satisfied with the project than it is ok but, if the customer is not satisfied with the project than the meeting of the developer and the customer and again the customer tells about its requirement of the project to the developer. And after all six steps repeat again and again till customer satisfaction.
3. Design:- This is the third step of the spiral model. It is also a very important step in the spiral model. This step is done after the analysis step of the spiral model. In the design step of the spiral model, the developer creates written documentation of the project or software. This written documentation is called SRS documentation. The SRS documentation is helpful to explain the project or software to the customer.
4. Coding:- It is the fourth step of the spiral model or we can say, that coding is the fourth step of the spiral model. It is also a very important step in the spiral model. This step takes place after the third step or the design step of the spiral model. In this step programmer or developer, actually do programming or coding. The developer starts programming takes SRS documentation as input. In this, the programmer starts programming by seeing the documentation.
5. Test:- It is the fifth step of the spiral model. or we can say, that the test is the fifth step of the spiral model. It is also a very important step in the spiral model. This step of the spiral model is done after the fourth step or after the coding step of the spiral model. In this step of the spiral model, the developer checks the project that it is working or not. And check that there is an error in the project or not. And see that the project or software is working properly or not. Overall basically we can say, that in this step of the spiral model developer make sure that the project fine or not.
6. Maintenance:- It is the sixth step of the spiral model. or we can say, that maintenance is a sixth step of the spiral model. It is also the last step of the spiral model. It is also a very important step in the spiral model. Maintenance is the phase/step to enhance the product some better versions are released. Maintenance is done to deliver these changes in the customer environment. Maintenance, phase/step is used to update the project/software.
In the spiral model after the maintenance of the project the developer handover the project to the customer. If the customer is satisfied with the project than it is ok but, if the customer is not satisfied with the project than the meeting of the developer and the customer and again the customer tells about its requirement of the project to the developer. And after all six steps repeat again and again till customer satisfaction.
ADVANTAGE OF SPIRAL MODEL:-
- It is a very flexible model.
- Less documentation is needed.
- Changing needs are accommodated.
- It allows in-depth use of prototypes.
- Requirements are captured a lot of accurately.
- Users see the system early.
- Development is divided into smaller elements and also the risky elements are developed earlier that helps in higher risk management.
DISADVANTAGES OF THE SPIRAL MODEL:-
- No particular beginning or ending of a particular step.
- Management is a lot of advanced.
- The end of the project might not be glorious early.
- Not appropriate for tiny or low risk comes and will be pricy for tiny comes.
- The process is advanced.
- The spiral could proceed indefinitely.
- A large number of intermediate stages need excessive documentation.
USE OF SPIRAL MODEL:-
- When the project is massive.
- When releases square measure needed to be frequent.
- When the creation of a paradigm is applicable.
- When risk and price analysis is vital.
- For medium to unsound comes.
- When needs square measure unclear and sophisticated.
- When changes could need at any time.
- When future project commitment isn't possible because of changes in economic priorities.
Post a Comment
Post a Comment