Waterfall Method
Version 1.0.0 · Updated 2026-07-30
CORE DEFINITION
A linear sequential development process: requirements → design → implementation → testing → deployment, where each phase is completed before moving to the next. Scaffold role: clear but rigid. Suitable for projects with clear and stable requirements, not suitable for situations with frequent requirement changes.
SCAFFOLDING EFFECT
Reduce cognitive load
Clear but rigid. Suitable for projects with clear and stable requirements, not suitable for situations with frequent requirement changes.
Anchor fast decisions
The waterfall model is characterized by strictly ordered and unidirectional flow of phases, where the output of the previous phase is the input of the next, emphasizing comprehensive upfront planning and documentation. Its applicability presupposes stable and predictable requirements, as the cost of rework increases exponentially with each phase. It uses 'sequential locking' to achieve controllability and auditability.
MINIMUM ACTION
In progress 0/3Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Waterfall_modelverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS