The Classical Waterfall Model in Software Development
The Waterfall Model is a linear, sequential software development lifecycle where each phase must be completed before the next begins. No overlapping or iteration between phases.
Six Phases
- Requirements Gathering & Analysis – Document all functional/non-functional requirements; produce SRS (Software Requirements Specification)
- Design – Architectural (high-level) and detailed (low-level) design; data models, interfaces, algorithms
- Implementation (Coding) – Write, compile, unit-test code modules per design specs
- Testing (Verification/Validation) – Integration, system, acceptance testing against requirements
- Deployment – Install in production environment; user training, data migration
- Maintenance – Bug fixes, enhancements, patches post-release
Characteristics
- Rigid: No backtracking; changes require restarting from affected phase
- Document-heavy: Extensive specs at each gate
- Predictable: Clear milestones, budgets, timelines if requirements are stable
Criticism
Inflexible for evolving requirements; late defect discovery; poor fit for complex, uncertain projects. Largely superseded by iterative (Agile, Spiral) models, but still used in regulated domains (medical, aerospace, defense) where traceability and certification mandate sequential rigor.