4.
SOFTWARE MODEL USED
4.1 WATERFALL MODEL METHODOLOGY
The Waterfall methodology — also known as the Waterfall model
— is a sequential development process that flows like a waterfall
through all phases of a project (analysis, design, development,
and testing, for example), with each phase completely wrapping
up before the next phase begins.
It is said that the Waterfall methodology follows the adage to
“measure twice, cut once.” The success of the Waterfall method
depends on the amount and quality of the work done on the front
end, documenting everything in advance, including the user
interface, user stories, and all the features’ variations and
outcomes.
With the majority of the research done upfront, estimates of the
time needed for each requirement are more accurate, and this
can provide a more predictable release date. With a Waterfall
project, if parameters change along the way, it’s harder to
change course than it is with Agile methodology.
Following are the waterfall Methodology phases:
• Requirement
• Design
• Implementation
• Verification or Testing
• Deployment & Maintenance