What is 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.
Table of Content
In Iterative waterfall model, the feedback paths are provided from every phase to its preceding phase as shown in Figure 2.
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.
The iterative waterfall model is the most widely used software development model evolved so far.
When to use Iterative Waterfall Model
- The requirement of the defined and clearly understood.
- New technology is being learned by the development team.
- There are some high risk features and goals which might in the future.
Application of Iterative Waterfall Model
- Major requirements are defined but the minor details might involve when time goes.
- New technologies are being used and there is a learning curve for the programmers to learn.
- Resource are limited to do a huge project as if a small project automates are in contact rather than permanent.
- Very high risk as a goal of the project might change from time to time.
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.
- Difficult to include change requests: In the iterative waterfall model, all the requirements must be clearly defined before starting of the development phase but sometimes customer requirement changes which is difficult to incorporate change requests that are made after development phase starts.
- Not support Intermediate delivery: Project has to be fully completed before it delivered to the customer.
- Risk handling: Project is prone to many types of risk but there is no risk handling mechanism.
- Not suitable for a small project.
Read Further: Wikipedia