Iterative Waterfall Model in SDLC
Iterative Waterfall Model
- Iterative Waterfall Model is the extension of the Waterfall model.
- This model is almost same as the waterfall model except some modifications are made to improve the performance of the software development.
- The iterative waterfall model provides customer’s feedback paths from each phase to its previous phases.
- There is no feedback path provided for feasibility study phase, so if any change is required in that phase then iterative model doesn’t have scope for modification or making corrections.
- Iterative waterfall allows to go back on the previous phase and change the requirements and some modification can done if necessary.
- This model reduces the developer’s effort and time required to detect and correct the errors.
- In iterative waterfall model, next phase can only begins when the previous phase is completed as waterfall model.
Phases of Iterative Waterfall Model :-
- Requirement Analysis
- Feasibility Study
- Software Design
- Software Testing
- Software Deployment
- Software Maintenance
Advantages of Iterative Waterfall Model :-
- Iterative waterfall model is very easy to understand and use.
- Every phase contains feedback path to its previous phase.
- This is an simple to make changes or any modifications at any phase.
- By using this model, developer can completer project earlier.
- Customer involvement is not required during the software development.
- This model is suitable for large and complex projects.
Disadvantages of Iterative Waterfall Model :-
- There is no feedback path for feasibility study phase.
- This model is not suitable if requirements are not clear.
- It can be more costly.
- There is no process for risk handling.
- Customer can view the final project. there is no prototype for taking customer reviews.
- This model does not work well for short projects.
- If modifications are required repeatedly then it can be more complex projects.