×

Courses

Chapters

>
<

Software Engineering

Software Engineering Waterfall Model | CrackEase

Waterfall Model

What is the Waterfall Model?

  • The Waterfall model is one of the earliest SDLC models, proposed by Winston W. Royce in 1970.
  • It is a linear-sequential (step-by-step) model where each phase must finish before the next begins.
  • The output of one phase becomes the input to the next phase.
  • Typical phases include: Requirements > Design > Implementation > Verification > Maintenance.
  • Because phases do not overlap, it is difficult to go back and change earlier phases once they are complete.
  • The model is simple, easy to manage and suitable for projects with well-understood requirements.

Advantages of the Waterfall Model

  • Simple and easy to understand and use.
  • High visibility since deliverables for each phase are well-defined.
  • Produces good documentation which helps maintenance and onboarding.
  • Works well for small projects with clear, fixed requirements.
  • Phases are easy to manage due to their sequential nature.
  • Cost and schedule estimates are easier to prepare early in the project.

Disadvantages of the Waterfall Model

  • Not suitable for large or complex projects where requirements may change.
  • Very limited flexibility to accommodate requirement changes after a phase is completed.
  • Late discovery of issues because testing is performed after implementation.
  • Customer may have to wait long before seeing a working product.
  • High risk and uncertainty for long-duration projects.
  • Assumes requirements are fully known at the start which is rarely true in practice.
Footer Content | CrackEase
→
←