Waterfall model

Waterfall model
Name	Waterfall model
Type	Software development process model
First proposed	1970
Origin	Industrial engineering
Proponents	Winston W. Royce
Related	Spiral model, V-model, Incremental model, Agile software development

Waterfall model The Waterfall model is a linear-sequential development process used in software engineering and systems engineering. It prescribes a series of distinct phases with formal handoffs, emphasizing documentation, predefined requirements, and milestone approvals. The model influenced industrial project management practices across computing, defense, aerospace, and corporate information technology.

Overview

The Waterfall model organizes work into ordered stages such as system specification, architecture, implementation, verification, and maintenance, with reviews and deliverables at phase boundaries. It draws on management practices from Winston W. Royce's 1970 paper and earlier engineering traditions exemplified by Frederick Winslow Taylor, Henry Gantt, Herbert Simon, Norbert Wiener, and Eric S. Raymond. Prominent organizations and projects that used waterfall-style processes include Hewlett-Packard, IBM, Lockheed Martin, Boeing, General Electric, Siemens, Raytheon, and NASA development programs. The model's artifacts—requirements documents, design specifications, test plans, and maintenance logs—became staples at institutions such as Bell Labs, Bellcore, AT&T, Microsoft, Oracle Corporation, Sun Microsystems, and Xerox PARC.

History and Origins

Origins trace to industrial-era project control and systems engineering practices used in Bell Telephone Laboratories and early computing initiatives like ENIAC and Project Whirlwind. The paradigm was formalized in Royce's work and adopted in large-scale government procurements exemplified by United States Department of Defense contracts, MIL-STD-498, and standards promulgated by IEEE and ISO. Waterfall concepts migrated into commercial software during the rise of mainframe computing at IBM and minicomputer systems at Digital Equipment Corporation and Honeywell. The model was influential in regulated sectors overseen by agencies such as the Federal Aviation Administration, European Space Agency, National Aeronautics and Space Administration, and defense ministries of United Kingdom, France, Germany, and Japan.

Phases

Typical named phases derive from systems engineering and project lifecycle frameworks used by NASA Systems Engineering Handbook, IEEE 12207, and ISO/IEC 15288. Common phase names appear in program documentation at Lockheed Martin Skunk Works, Northrop Grumman, and BAE Systems: - Requirements analysis and specification, with stakeholder sign-off involving entities like Department of Defense program managers and contractors such as Sikorsky Aircraft. - System and software architecture or high-level design, influenced by patterns cataloged at Carnegie Mellon University and MIT research labs. - Detailed design and module-level engineering, following practices used in Intel Corporation and Advanced Micro Devices chip projects. - Implementation (coding, fabrication) as undertaken in projects by Microsoft Windows teams, Apple Inc. hardware-software integration, and Google infrastructure builds. - Verification and validation testing in the style of IEEE test suites and certification efforts for Airbus and Boeing 737 programs. - Deployment and operations with maintenance cycles managed by agencies such as United States Postal Service IT modernization efforts and corporate IT departments at General Motors and Ford Motor Company.

Advantages and Limitations

Advocates highlight traceability, contractual clarity, and predictability, valued in procurements by Pentagon programs, National Security Agency contracts, and regulated certification cases like FAA type certification. Waterfall suits projects with fixed specifications such as Space Shuttle subsystems or Hubble Space Telescope instruments. Limitations surfaced in dynamic domains exemplified by Silicon Valley startups and rapid web platforms from Facebook, Amazon.com, Netflix, and Twitter, where evolving requirements required iterative models. Critics pointed to late discovery of defects in large enterprise projects at Deutsche Bank and Barclays, and to schedule slips seen in public-sector IT projects in United Kingdom and Australia.

Variations and Derivatives

Derivatives and hybrids emerged in response to limitations. The V-model maps verification to each design phase and is used by European Space Agency and Siemens. The Spiral model from Barry Boehm introduced risk-driven iteration and saw use at Defense Advanced Research Projects Agency. Incremental and staged delivery approaches influenced development at Sun Microsystems and were precursors to Agile software development movements centered around practitioners from Kent Beck, Martin Fowler, and Jim Highsmith. Organizations such as Scrum Alliance, Scaled Agile, Inc., and Agile Alliance formalized alternatives. Hybrid lifecycle patterns appeared in programs at NASA Jet Propulsion Laboratory and ESA missions, combining waterfall milestones with iterative subproject sprints.

Adoption and Criticism

Adoption was strong in defense, aerospace, telecommunications, banking, and pharmaceuticals—domains regulated by FDA, EMA, and national standards bodies like DIN and BSI. High-profile criticisms came from practitioners at Bell Labs, academics at University of California, Berkeley and Carnegie Mellon University, and industry commentators including Joel Spolsky and Ward Cunningham. Empirical studies by researchers at Standish Group and MIT Sloan School of Management compared waterfall outcomes to iterative methods in projects at General Electric, Siemens AG, and Toyota. Policy debates over procurement rules and contracting influenced transitions in ministries such as UK Cabinet Office and U.S. Office of Management and Budget.

Practical Applications and Examples

Waterfall-style processes remain common where safety, certification, or fixed contracts dominate, such as avionics suites for Airbus A320neo, control systems for Boeing 787, embedded controllers in Siemens industrial systems, and medical device software validated under FDA guidance. Large-scale enterprise resource planning implementations at SAP, Oracle Corporation, and national tax IT projects in Canada, New Zealand, and India have used waterfall planning. Historical examples include early versions of Microsoft Windows NT, certain IBM mainframe system deliveries, and legacy telecommunications switches from AT&T and Alcatel-Lucent.

Category:Software development methodologies