When should you use Waterfall Model
The Waterfall Model is the earliest SDLC approach that was used for software development. This model is an example of a sequential model. So it is also referred to as a linear sequential life cycle model.
The waterfall model is very simple to understand and use. In a waterfall model, each phase must be completed before the next phase can begin. Also called as classic life cycle model.
When Should You Use It ?
- Requirements are clear and fixed that may not change.
- There are no ambiguous requirements (no confusion).
- It is good to use this model when the technology is well understood.
- The project is short and cast is low.
- Risk is zero or minimum.
These are some advantages of Waterfall Model.
- It is simple and easy to understand and use.
- It is easy to manage.
- It works well for smaller and low budget projects where requirements are very well understood.
- Clearly defined stages and well understood.
- It is easy to arrange tasks.
- Process and results are well documented.
These are some disadvantages of Waterfall Model.
- It is difficult to measure progress within stages.
- Poor model for long and ongoing projects.
- No working software is produced until late during the life cycle.
- High amounts of risk and uncertainty.
- Not a good model for long and object oriented projects.
- Cannot accommodate changing requirements.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.