Waterfall Methodology

Waterfall Methodology

1. Split up into multiple stages

   • Each end of stage is called a milestone

2. Sequential order

   • Once a stage is passed you can't go back if it is using the "pure" waterfall method
   • However most people use a modified waterfall method so they can go back to a stage.

3. Stages in order are

   • Define requirements (The problem, solution and stakeholders), Analysis, Design, Implement, Test, Install and Maintain

4. Advantages

   • The project is managed in a well- structured manner.
   • Easy for someone outside the project to understand how the project is managed and progressed
   • Spending time and effort at requirements stage saves time and money overall.

5. Disadvantages

   • Clients very often don't know exactly what they want at the beginning of project
   • Not good for high-risk or challenging projects.
   • Not suitable when the requirements are vague or being changed constantly.
   • Difficult to plan ahead if team is unfamiliar with technology required.

Images and files in the map