What is Waterfall Methodology?
Waterfall is traditional approach of software development. It is very easy to understand and use. In a waterfall methodology, previous stage must be completed fully before the next stage can start. There is also typically a stage gate between each phase; for example, requirements must be reviewed and approved by the client before design can begin. This process of development model is usually used for the for the project which is small and there is no change in requirements. In this methodology, the sequence of event follows like below
- Requirement Gathering
What are Pros of waterfall model?
The following are important pros of waterfall methodology:
- It is very easy to understand and simple method
- It is quite easy to manage process due to its rigidity.
- Progress is more easy to identify, as the full scope of the work is known in advance.
- Waterfall model works well for smaller projects, when the change of requirement is minimal.
What are the Cons of waterfall model?
The following are cons of waterfall methodology:
- It is difficult to change, if something doesn’t work well in the testing phase.
- No working software is available till the late phase of the model.
- High risk and uncertainty is associated with this method.
- Customer may be dissatisfied with product delivered at the end because the customer involvement is only during the first few phases.
Client interaction is very less during the development of the product. Once the product is developed then only it can be showcased to the end users. Once the product is developed and if any defect/failure are found then the cost of fixing such defects are very high, because we need to update everywhere from document till the logic.
Application of waterfall model
Every software developed is quite different from each other and need a suitable development approach, which need to be followed based on the internal and external factors. Some situations where the use of Waterfall model is most appropriate are –
- Requirements are understood well and clear.
- There is no ambiguity in the requirement.
- The project is short