“SYSTEM DESIGN AND SOFTWARE E ENGINEERING”
Content
• What is Waterfall model
• Phases of the Waterfall Model
• Advantages of the Waterfall Model
• Disadvantages of the Waterfall Model
• When to Use the Waterfall Model
What is Waterfall model
The Waterfall Model is a traditional and linear
software development methodology that
follows a sequential approach. Each phase of
the project must be completed before the
next phase begins, and there is no overlapping
of phases
Phases of the Waterfall Model
1. Requirement Analysis:
• Gather and document all the requirements of
the project.
• Create a Software Requirement Specification
(SRS) document that outlines all the
functionalities the software must have.
2. System Design:
• Develop the architecture and design of the system based
on the requirements.
3 Development (or Coding):
The Development phase include implementation
involves coding the software based on the
design specifications.
4. Testing
• Integrate all the modules and test the system
as a whole.
5. Deployment:
• Deploy the software to the production environment
where users can begin using it.
• .
6.Maintenance:
• Perform maintenance activities such as fixing
bugs, implementing updates, and making
enhancements based on user feedback.
Advantages of the Waterfall Model
• Easy to Understand: The Classical Waterfall Model is very
simple and easy to understand.
• Individual Processing: Phases in the Classical Waterfall model
are processed one at a time.
• Properly Defined: In the classical waterfall model, each stage
in the model is clearly defined.
• Clear Milestones: The classical Waterfall model has very clear
and well-understood milestones.
Disadvantages of the Waterfall Model
• Inflexibility: Once a phase is completed, going
back to make changes is difficult and costly.
• Late Testing: Testing occurs only after the
development phase, making it harder to
identify and fix issues early in the process.
• High Risk and Uncertainty: Not suitable for
projects where requirements are not well
understood or are expected to change.
When to Use the Waterfall Model
• Projects with Clear and Stable Requirements:
When the requirements are well-understood
and unlikely to change.
• Short-Term Projects: Small projects where the
scope is limited and well-defined.
• Projects with Low Complexity:
Thank you
