Waterfall Methodology
The Waterfall Model was the first Process Model to be introduced and this model was
developed for software development. The waterfall model is a breakdown of project
activities into linear sequential phases. It means that any phase of the development process
begins only when the previous phase is over. In this model, the phases don’t overlap. The
success of this method depends on the amount and quality of the work done. There are 5
common stages in a waterfall model process. Requirements, Design, Implementation,
Verification or Testing and Maintenance.
Requirements: All possible requirements of the system to be developed are
captured in this phase and documented in a requirement specification document. In that
document, are used to describe each stage of the project, including the costs, risks,
dependencies, success, and timelines for completion.
Design: In this phase Developers design a technical solution to the problems set out
by the product requirements. Like layouts, and data models. Design helps in specifying
hardware and helps in defining the overall system architecture.
Implementation: After the Design phase is complete, implementation starts. This
is the shortest phase in this model. Cause design and researches have already been done. In
the Implementation phase, with inputs from the system design, programmers code apps
based on project requirements and specifications.
, Verification or Testing: Before an app can be released to customers, testing
needs to be done. All the units developed in this phase are integrated into a system after
testing each unit. To ensure the product has no errors, ensuring a good user experience with
the software and all of the requirements have been completed.
Maintenance: After the software is released to customers, the maintenance phase
begins. This is the last phase in the waterfall model. There are some problems in the client
area. To fix those issues, new updates and patches are released. And to improve the
product some better versions are released.
Strengths of the waterfall model.
• This model is very simple to understand and use.
• This can provide a more predictable release date.
• Easy to manage
• Works well for smaller projects.
• Clearly defined stages.
• Well understood milestones.
• Easy to arrange tasks.
Weakness of the waterfall model.
• High amounts of risk.
• One phase must be complete before the next phase starts.
• It’s harder to change course.
• Not a good model for complex projects.
• Poor model for ongoing projects.
The Waterfall Model was the first Process Model to be introduced and this model was
developed for software development. The waterfall model is a breakdown of project
activities into linear sequential phases. It means that any phase of the development process
begins only when the previous phase is over. In this model, the phases don’t overlap. The
success of this method depends on the amount and quality of the work done. There are 5
common stages in a waterfall model process. Requirements, Design, Implementation,
Verification or Testing and Maintenance.
Requirements: All possible requirements of the system to be developed are
captured in this phase and documented in a requirement specification document. In that
document, are used to describe each stage of the project, including the costs, risks,
dependencies, success, and timelines for completion.
Design: In this phase Developers design a technical solution to the problems set out
by the product requirements. Like layouts, and data models. Design helps in specifying
hardware and helps in defining the overall system architecture.
Implementation: After the Design phase is complete, implementation starts. This
is the shortest phase in this model. Cause design and researches have already been done. In
the Implementation phase, with inputs from the system design, programmers code apps
based on project requirements and specifications.
, Verification or Testing: Before an app can be released to customers, testing
needs to be done. All the units developed in this phase are integrated into a system after
testing each unit. To ensure the product has no errors, ensuring a good user experience with
the software and all of the requirements have been completed.
Maintenance: After the software is released to customers, the maintenance phase
begins. This is the last phase in the waterfall model. There are some problems in the client
area. To fix those issues, new updates and patches are released. And to improve the
product some better versions are released.
Strengths of the waterfall model.
• This model is very simple to understand and use.
• This can provide a more predictable release date.
• Easy to manage
• Works well for smaller projects.
• Clearly defined stages.
• Well understood milestones.
• Easy to arrange tasks.
Weakness of the waterfall model.
• High amounts of risk.
• One phase must be complete before the next phase starts.
• It’s harder to change course.
• Not a good model for complex projects.
• Poor model for ongoing projects.
