WATERFALL
MODEL
Presented by Cuties
System design methodologies are structured approaches used to
plan, analyze, and construct complex systems.
The Waterfall Model
• one of the oldest and most traditional approaches
to software and system development.
• a linear and sequential methodology that was first
introduced in the 1970s.
• the first SDLC Model to be used widely in Software
Engineering to ensure success of the project.
SEQUENTIAL PHASES OF
Requirement
Gathering WATERFALL MODEL
Design
Implementation
Testing
Deployment
Maintenance
REQUIREMENTS GATHERING
AND ANALYSIS
• In this initial phase, project • The goal is to create a • This phase often involves
stakeholders, including comprehensive and meetings, interviews, and
clients, end-users, and detailed specification that documentation to ensure a
development teams, work outlines what the system complete understanding of
together to define and should do, its features, and user needs.
document the project's constraints.
requirements.
SYSTEM DESIGN
• Once the requirements • System architects and • The output of this phase
are finalized, the system designers create detailed is a design document or
design phase begins. plans for the system's blueprint that serves as a
architecture, data guide for the
structures, user development team.
interfaces, and other
technical aspects.
IMPLEMENTATION (CODING)
• In the implementation phase, developers
write the actual code based on the design
specifications.
TESTING
• Once the implementation is • Testing encompasses various
complete, the system goes levels, including unit testing
through rigorous testing to (testing individual
identify and fix defects and components), integration
ensure that it meets the testing (testing interactions
specified requirements. between components), and
system testing (testing the
entire system).
DEPLOYMENT
• After successful testing and approval, the system is deployed to the
production environment or delivered to the client.
• This phase involves installing the software on target hardware and
ensuring it is operational for end- users.
MAINTENANCE AND SUPPORT
• The final stage of the Waterfall Model involves maintaining and
supporting the system in its operational environment.
• This includes addressing bug fixes, making necessary updates, and
providing ongoing support to users.
ADVANTAGES OF
WATERFALL MODEL
• Easy to manage due to the rigidity of the model. Each phase has specific
deliverables and a review process.
• Phases are processed and completed one at a time.
• Works well for smaller projects where requirements are very well
understood.
• Clearly defined stages.
• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented.
DISADVANTAGES OF
WATERFALL MODEL
• Inflexibility
• Late feedback
• High Risk
• Long Delivery Time
MICROSOFT
BOEING
NASA
THANK
YOU
