Catalog
concept#Software Engineering#Governance#Delivery#Quality Assurance

Waterfall Model

A sequential development model with clearly separated phases and rigid handover points.

The Waterfall model is a sequential planning and development approach that executes phases such as requirements analysis, design, implementation, testing and maintenance in strict order.
Established
Medium

Classification

  • Medium
  • Organizational
  • Organizational
  • Intermediate

Technical context

Configuration management tools (e.g., SCM)Test management and QA toolsDocument management and audit tools

Principles & goals

Sequential phases with clear handovers and responsibilities.Define scope and requirements stably before start.Extensive documentation as primary artifact for traceability.
Build
Enterprise, Domain, Team

Use cases & scenarios

Compromises

  • High cost for subsequent changes.
  • Excessive documentation effort instead of functional delivery.
  • Wrong early assumptions propagate throughout the project.
  • Validate critical assumptions early (proof-of-concept).
  • Implement explicit change control processes.
  • Conduct regular stakeholder reviews at milestones.

I/O & resources

  • Complete requirements specification
  • Project plan with milestones
  • Test and acceptance plans
  • Completed release packages by phase
  • Acceptance and verification records
  • Complete technical documentation

Description

The Waterfall model is a sequential planning and development approach that executes phases such as requirements analysis, design, implementation, testing and maintenance in strict order. It emphasizes documentation, fixed milestones and clear handovers. Suitable for stable requirements, but inflexible and costly to change when faults surface late.

✔

  • Clear planning enabling budget and schedule commitments.
  • Easy traceability and auditability via documentation.
  • Structured milestones simplify acceptance processes.

✖

  • Low flexibility for changing requirements.
  • Defects are often discovered late in the process.
  • Slow feedback cycles can hinder innovation capability.

  • Schedule adherence

    Measure of how well phase milestones were met.

  • Rework effort

    Effort required for fixes arising from late-discovered defects.

  • Documentation completeness

    Degree of formal documentation relative to required artifacts.

Large government procurement project

Stable requirements and contractual milestones led to a waterfall process with formal acceptance.

Medical device manufacturer

Regulatory constraints required documented phases and traceability, so waterfall-like processes were used.

Embedded development for industrial automation

Hardware dependencies and long test cycles made sequential phases practical.

1

Capture requirements completely and approve formally.

2

Create detailed phase and milestone plan.

3

Define and instrument documentation, testing and acceptance processes.

⚠️ Technical debt & bottlenecks

  • Deferred refactorings accumulate into major technical burden.
  • Outdated components remain due to costly adaptations.
  • Lack of test automation hinders later changes.
Late testing phasesChange costsDocumentation effort
  • Starting a complex innovation project without iterations.
  • Applying it where requirements are highly uncertain and change quickly.
  • Skipping tests until the final test phase in high-risk projects.
  • Assumptions in requirements document go unchallenged.
  • Stakeholder feedback is collected too late.
  • Change requests lead to uncontrolled project delays.
Requirements analysis and domain knowledgeFormal testing and verification skillsProject management with waterfall phase control
Stable requirements and specificationsRegulatory traceabilityPredictable time and cost constraints
  • • Requirements must be stable before project start.
  • • Formal acceptance and review procedures extend schedules.
  • • Limited iteration opportunities during execution.