Waterfall model

Waterfall model. The Waterfall model is a sequential software development process that structures project phases into a linear, non-iterative flow. First formally described by Winston W. Royce in a 1970 paper, it emphasizes thorough documentation and sign-off at each stage before proceeding to the next. While influential in establishing structured engineering disciplines, it has been widely criticized for its inflexibility in the face of changing requirements, leading to the adoption of various Agile software development methodologies.

Overview

The model conceptualizes the systems development life cycle as a cascade, where progress flows steadily downward through distinct phases. This approach was heavily influenced by structured manufacturing and construction processes used in industries like those managed by the United States Department of Defense. Its linear nature requires that each phase, such as requirements analysis or system design, be completed fully before the next begins, a principle that demands rigorous upfront planning. The model assumes that requirements can be fully and correctly specified at the project's outset, a notion challenged by later thinkers like Frederick Brooks in works such as The Mythical Man-Month. This framework was historically mandated in many large-scale contracts, particularly those involving organizations like NASA and the United States Armed Forces.

History

Although the sequential approach predates formal documentation, the model is most famously articulated in Winston W. Royce's 1970 paper presented at the IEEE WESCON conference. Royce, an engineer with experience at Lockheed Corporation and TRW Inc., actually critiqued the purely linear model, advocating for iterative feedback loops. However, his diagram of the sequential process became the definitive representation. The model gained formal traction through its adoption in standards like the DOD-STD-2167, which governed contracts for the United States Air Force. Its principles were also echoed in early software engineering methodologies promoted by institutions like the Software Engineering Institute at Carnegie Mellon University.

Phases

The classic model delineates several distinct and sequential phases. The process begins with **Requirements Gathering**, where all system and user needs are documented, often resulting in a Software Requirements Specification document. This is followed by **System Design**, which translates requirements into architecture, frequently using tools like data-flow diagrams and entity-relationship models. The **Implementation** phase involves the actual coding by programmers, building the system as specified in the prior designs. Subsequently, **Integration and Testing** combines individual modules and verifies functionality against the original Software Requirements Specification, a process sometimes managed under frameworks like the V-Model. Finally, **Deployment** releases the system to the end-user, and **Maintenance** addresses post-release issues, a phase that often reveals the high cost of changes, as noted in studies by the IBM Systems Research Institute.

Applications

Due to its structured nature, the model found early and sustained application in large, well-defined projects with fixed requirements and high regulatory scrutiny. It was extensively used in defense and aerospace projects for contractors like Boeing and Lockheed Martin, as well as in government systems for agencies such as the Internal Revenue Service. The model is also applicable in the development of physical hardware and embedded systems, where design changes are prohibitively expensive after production begins, such as in projects for Intel or Texas Instruments. Furthermore, it remains a basis for certain Capability Maturity Model Integration assessments and is taught in foundational computer science curricula at universities like Massachusetts Institute of Technology and Stanford University.

Criticism and alternatives

The model has been extensively criticized for its rigidity and inability to accommodate changing requirements, a problem highlighted in Frederick Brooks' The Mythical Man-Month. Critics argue it leads to late discovery of flaws, as testing only occurs after implementation, a point emphasized by advocates of Test-driven development. The famous CHAOS Report from the Standish Group often cited waterfall-like processes as a factor in project failures. These shortcomings catalyzed the development of iterative and incremental models, such as the Spiral model proposed by Barry Boehm. The most significant shift came with the Agile Manifesto in 2001, which championed Adaptive software development, Scrum, and Extreme Programming over rigid planning. Modern frameworks like DevOps and practices from Lean software development further emphasize continuous delivery and integration, representing a fundamental departure from the sequential systems development life cycle paradigm. Category:Software development process