Iterative Waterfall Model

In practice, it is not possible to strictly follow the classical waterfall model for software development work. In this context, we can view the iterative waterfall model as making necessary changes to the classical waterfall model so that it becomes applicable to practical software development projects.

In Iterative waterfall model, the feedback paths are provided from every phase to its preceding phase.

The feedback paths allow for correction of the errors committed during a phase, as and when these are detected in a later phase.

For example, if during a testing a design error is identified, then the feedback path allows the design to be reworked and the changes to be reflected in the design documents. However, observe that there is no feedback path to the feasibility stage. This means that the feasibility study errors cannot be corrected.

Advantages of Iterative Waterfall Model

• Feedback Path: iterative waterfall allows the mechanism of error connection because there is a feedback path from one phase to its preceding phase which it lacks in the Waterfall Model.
• Simple: iterative waterfall model is simple to understand and use. It is the most widely used software development model evolved so far.
• Parallel development: can be done.

Disadvantage of Iterative Waterfall Model

• More resource: may be required to implement the iterative waterfall model.
• Design can be changed again and again because of imperfect requirements.
• Requirement changes can cause over budget.
• Project completion date not confirmed because of changing requirements.
• Not suitable for a small project.