PRESTIGE INSTITUTION OF ENGINEERING
MANAGEMENT AND RESEARCH
SESSION 2025 – 26
Topic : Waterfall Model
Presented
•By
Varsha Punase Name of the faculty :
:
• Vrati Jain Prof. Himanshu
Bagwaiya
Waterfall Model
The Waterfall Model is a foundational methodology in soft ware development that follows a linear
sequential approach. This document provides an overview of the Waterfall Model, its historical
context, the phases involved, and its advantages and disadvantages. By understanding this model,
developers and project managers can better assess its applicability to their projects
Introduction
•The Waterfall Model is a linear sequential model that represents the first process model in soft ware
development.
•It emphasizes a structured approach where the entire applicati on is developed in a sequential
manner.
•It was the first Process Model.
•It is very simple to understand and use.
•In this model each phase must be completed fully before the next phase begin
History
• It was first introduced by Winston W. Royce in 1970.
• Royce present The Waterfall Model is a classical
soft ware development methodology.
• Presented this model as an example of a fl awed, non-
working model.
• Despite its initial criticism, it has been widely adopted
for soft ware projects ever since .
Phases of Waterfall Model
The Waterfall Model consists of the following phases:
[Link] Analysis:
• Analyze whether the project is technically,
economically, and operationally feasible.
[Link] Analysis:
• Gather and document all user requirements.
[Link] Design:
• Define system architecture and design
specifications.
[Link] (Coding):
• Develop soft ware based on design documents.
[Link]:
• Validate the soft ware against requirements and
identify bugs.
[Link]:
• Provide updates, bug fixes, and enhancements.
Advantages of Waterfall Model
• Simple and easy to understand.
• Clear documentati on at each phase.
• Well-defi ned stages and milestones.
• Best suited for smaller projects with stable
requirements
Disadvantages of Waterfall Model
• Lacks feedback mechanisms.
• Not suitable for projects with changing requirements.
• Does not allow for parallel development of phases .
Applications of the Waterfall Model
The Waterfall Model is best suited for projects with well-
defined requirements and low likelihood of changes. It is
commonly used in industries such as:
•Government projects
•Construction and manufacturing
•Projects with strict regulatory requirements
Conclusion
The Waterfall Model remains a foundational approach in software
development, particularly for projects where requirements are stable
and well-understood. While it has its limitations, its structured
methodology can be beneficial in certain contexts. Understanding the
Waterfall Model allows teams to evaluate its applicability and make
informed choices about their development processes.