Open In App

When should you use Waterfall Model

Improve
Improve
Like Article
Like
Save
Share
Report

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 ?

  1. Requirements are clear and fixed that may not change.
  2. There are no ambiguous requirements (no confusion).
  3. It is good to use this model when the technology is well understood.
  4. The project is short and cast is low.
  5. Risk is zero or minimum.

Advantages:
These are some advantages of Waterfall Model.

  1. It is simple and easy to understand and use.
  2. It is easy to manage.
  3. It works well for smaller and low budget projects where requirements are very well understood.
  4. Clearly defined stages and well understood.
  5. It is easy to arrange tasks.
  6. Process and results are well documented.

Disadvantages:
These are some disadvantages of Waterfall Model.

  1. It is difficult to measure progress within stages.
  2. Poor model for long and ongoing projects.
  3. No working software is produced until late during the life cycle.
  4. High amounts of risk and uncertainty.
  5. Not a good model for long and object oriented projects.
  6. Cannot accommodate changing requirements.

Last Updated : 30 Mar, 2020
Like Article
Save Article
Previous
Next
Share your thoughts in the comments
Similar Reads