Gist: The absolute opposite to the previous approach, this methodology is strict and linear. A new stage can only be started if the previous one is completed. In other words, each phase gradually flows into the next one. What is more, there is no going back to the previous stage. This approach is easy to understand as it presupposes a strict sequence of completed tasks. Waterfall methodology is often regarded as a classic representation of software development.
- Benefits: It is simple, functional, gradual and analytical.
- Drawbacks: Works good with exact requirements and needs only. Weak for long or ongoing projects.
Post a Comment