Wikipedia

Waterfall model

(Redirected from Waterfall Model)

The waterfall model is a breakdown of development activities into linear sequential phases, meaning each phase is passed down onto each other, where each phase depends on the deliverables of the previous one and corresponds to a specialization of tasks.[1] This approach is typical for certain areas of engineering design. In software development,[1] it tends to be among the less iterative and flexible approaches, as progress flows in largely one direction (downwards like a waterfall) through the phases of conception, initiation, analysis, design, construction, testing, deployment, and maintenance.[2] The waterfall model is the earliest Systems Development Life Cycle (SDLC) approach used in software development.[3]

The waterfall development model originated in the manufacturing and construction industries,[citation needed] where the highly structured physical environments meant that design changes became prohibitively expensive much sooner in the development process.[citation needed] When it was first adopted for software development, there were no recognized alternatives for knowledge-based creative work.[4]

History

edit

The first known presentation describing the use of such phases in software engineering was held by Herbert D. Benington at the Symposium on Advanced Programming Methods for Digital Computers on 29 June 1956.[5] This presentation was about the development of software for SAGE. In 1983, Benington republished his paper with a foreword explaining that the phases were on purpose organized according to the specialization of tasks, and pointing out that the process was not in fact performed in a strict top-down fashion, but depended on a prototype.[6][better source needed]

Although the term "waterfall" is not used in the paper, the first formal detailed diagram of the process later known as the "waterfall model" is often[7] cited as coming from a 1970 article by Winston W. Royce.[8][9][10] However, he commented that it had major flaws stemming from how testing only happened at the end of the process, which he described as being "risky and [inviting] failure".[8] The rest of his paper introduced five steps which he felt were necessary to "eliminate most of the development risks" associated with the unaltered waterfall approach.[8]

Royce's five additional steps (which included writing complete documentation at various stages of development) never took mainstream hold, but his diagram of what he considered a flawed process became the starting point when describing a "waterfall" approach.[11] [12]

The earliest use of the term "waterfall" may have been in a 1976 paper by Bell and Thayer.[13][better source needed]

In 1985, the United States Department of Defense adopted the waterfall model in the DOD-STD-2167 standard for working with software development contractors. This standard referred for iterations of a software development[14] to "the sequential phases of a software development cycle" and stated that "the contractor shall implement a software development cycle that includes the following six phases: Software Requirement Analysis, Preliminary Design, Detailed Design, Coding and Unit Testing, Integration, and Testing".[14][15]

Model

edit

Although Royce never recommended nor described a waterfall model,[16] rigid adherence to the following phases are criticized by him:

  1. System and software requirements: captured in a product requirements document
  2. Analysis: resulting in models, schema, and business rules
  3. Design: resulting in the software architecture
  4. Coding: the development, proving, and integration of software
  5. Testing: the systematic discovery and debugging of defects
  6. Operations: the installation, migration, support, and maintenance of complete systems

Thus, the waterfall model maintains that one should move to a phase only when its preceding phase is reviewed and verified.

Various modified waterfall models (including Royce's final model), however, can include slight or major variations on this process.[8] These variations include returning to the previous cycle after flaws are found downstream, or returning to the design phase if downstream phases are deemed insufficient.

Supporting arguments

edit

Time spent early in the software production cycle can reduce costs at later stages. For example, a problem found in the early stages (such as requirements specification) is cheaper to fix than the same bug found later on in the process (by a factor of 50 to 200).[17]

In common practice, waterfall methodologies result in a project schedule with 20–40% of the time invested for the first two phases, 30–40% of the time to coding, and the rest dedicated to testing and implementation. With the project organization needing to be highly structured, most medium and large projects will include a detailed set of procedures and controls, which regulate every process on the project.[18][failed verification]

A further argument supporting the waterfall model is that it places emphasis on documentation (such as requirements documents and design documents) as well as source code.[citation needed] In less thoroughly designed and documented methodologies, knowledge is lost if team members leave before the project is completed, and it may be difficult for a project to recover from the loss. If a fully working design document is present (as is the intent of big design up front and the waterfall model), new team members and new teams should be able to familiarise themselves to the project by reading the documents.[19]

The waterfall model provides a structured approach; the model itself progresses linearly through discrete, easily understandable and explainable phases and thus is easy to understand. It also provides easily identifiable milestones in the development process, often being used as a beginning example of a development model in many software engineering texts and courses.[20]

Similarly, simulation can play a valuable role within the waterfall model. By creating computerized or mathematical simulations of the system being developed, teams can gain insights into how the system will perform before proceeding to the next phase. Simulations allow for testing and refining the design, identifying potential issues or bottlenecks, and making informed decisions about the system's functionality and performance.

Criticism

edit

Clients may not know the exact requirements before they see working software and thus change their requirements further on, leading to redesign, redevelopment, and retesting, and increased costs.[21]

Designers may not be aware of future difficulties when designing a new software product or feature, in which case revising the design initially can increase efficiency in comparison to a design not built to account for newly discovered constraints, requirements, or problems.[22]

Organisations may attempt to deal with a lack of concrete requirements from clients by employing systems analysts to examine existing manual systems and analyse what they do and how they might be replaced. However, in practice, it is difficult to sustain a strict separation between systems analysis and programming,[23] as implementing any non-trivial system will often expose issues and edge cases that the systems analyst did not consider.

Some organisations, such as the United States Department of Defense, now have a stated preference against waterfall-type methodologies, starting with MIL-STD-498 released in 1994, which encourages evolutionary acquisition and Iterative and Incremental Development.[24]

Modified waterfall models

edit

In response to the perceived problems with the "pure" waterfall model, many 'modified waterfall models' have been introduced. These models may address some or all of the criticisms of the "pure" waterfall model.

These include the Rapid Development models that Steve McConnell calls "modified waterfalls":[17] Peter DeGrace's "sashimi model" (waterfall with overlapping phases), waterfall with subprojects, and waterfall with risk reduction. Other software development model combinations such as "incremental waterfall model" also exist.[25]

Royce's final model

edit
 
Royce final model

Winston W. Royce's final model, his intended improvement upon his initial "waterfall model", illustrated that feedback could (should, and often would) lead from code testing to design (as testing of code uncovered flaws in the design) and from design back to requirements specification (as design problems may necessitate the removal of conflicting or otherwise unsatisfiable/undesignable requirements).[citation needed] In the same paper Royce also advocated large quantities of documentation, doing the job "twice if possible" (a sentiment similar to that of Fred Brooks, famous for writing the Mythical Man Month — an influential book in software project management — who advocated planning to "throw one away"), and involving the customer as much as possible (a sentiment similar to that of extreme programming).

Royce notes on the final model are the following:

  1. Complete program design before analysis and coding begins
  2. Documentation must be current and complete
  3. Do the job twice if possible
  4. Testing must be planned, controlled, and monitored
  5. Involve the customer

See also

edit

References

edit
  1. ^ a b Petersen, Kai; Wohlin, Claes; Baca, Dejan (2009). "The Waterfall Model in Large-Scale Development". In Bomarius, Frank; Oivo, Markku; Jaring, Päivi; Abrahamsson, Pekka (eds.). Product-Focused Software Process Improvement. Lecture Notes in Business Information Processing. Vol. 32. Berlin, Heidelberg: Springer. pp. 386–400. Bibcode:2009pfsp.book..386P. doi:10.1007/978-3-642-02152-7_29. ISBN 978-3-642-02152-7.
  2. ^ Tom Gilb. "Evolutionary Delivery versus the 'waterfall model'". ACM SIGSOFT Software Engineering Notes. 10 (3): 49–61. doi:10.1145/1012483.1012490.  
  3. ^ Linda Sherrell (2013). "Waterfall Model". Encyclopedia of Sciences and Religions (A.L.C. Runehov; L. Oviedo (Eds.)). Dordrecht, The Netherlands: Springer: 2343–2344. doi:10.1007/978-1-4020-8265-8_200285. ISBN 978-1-4020-8264-1.
  4. ^ Andreas P. Schmidt; Christine Kunzmann (September 16, 2014). Designing for knowledge maturing: from knowledge-driven software to supporting the facilitation of knowledge development. i-KNOW '14: Proceedings of the 14th International Conference on Knowledge Technologies and Data-driven Business. ACM. pp. 1–7. doi:10.1145/2637748.2638421.
  5. ^ United States, Navy Mathematical Computing Advisory Panel (29 June 1956), Symposium on advanced programming methods for digital computers, [Washington, D.C.]: Office of Naval Research, Dept. of the Navy, OCLC 10794738
  6. ^ Benington, Herbert D. (1 October 1983). "Production of Large Computer Programs" (PDF). IEEE Annals of the History of Computing. 5 (4). IEEE Educational Activities Department: 350–361. doi:10.1109/MAHC.1983.10102. S2CID 8632276. Retrieved 2011-03-21. Archived July 18, 2011, at the Wayback Machine
  7. ^ Larman, Craig; Basili, Victor (June 2003). "Iterative and Incremental Development: A Brief History" (PDF). Computer. 36 (6): 47–56. doi:10.1109/MC.2003.1204375.
  8. ^ a b c d Royce, Winston (1970), "Managing the Development of Large Software Systems" (PDF), Proceedings of IEEE WESCON, 26 (August): 1–9
  9. ^ "Waterfall". Bremen University - Mathematics and Computer Science.
  10. ^ Abbas, Noura; Gravell, Andrew M.; Wills, Gary B. (2008). "Historical Roots of Agile Methods: Where Did "Agile Thinking" Come From?" (PDF). In Abrahamsson, Pekka; Baskerville, Richard; Conboy, Kieran; Fitzgerald, Brian; Morgan, Lorraine; Wang, Xiaofeng (eds.). Agile Processes in Software Engineering and Extreme Programming. Lecture Notes in Business Information Processing. Vol. 9. Berlin, Heidelberg: Springer. pp. 94–103. doi:10.1007/978-3-540-68255-4_10. ISBN 978-3-540-68255-4.
  11. ^ Conrad Weisert, Waterfall methodology: there's no such thing!
  12. ^ Lineberger, Rob (Apr 25, 2024). Inheriting Agile: The IT Practitioner's Guide to Managing Software Development in a Post-Agile World. Durham, NC: Sandprint Press. p. 36. ISBN 9798989149605.
  13. ^ Bell, Thomas E., and T. A. Thayer.Software requirements: Are they really a problem? Proceedings of the 2nd international conference on Software engineering. IEEE Computer Society Press, 1976.
  14. ^ a b DOD-STD-2167 - Military Standard : Defence System Software Development". Department of Defence, United States of America. 1985-06-04. p. 11.
  15. ^ "Military Standard Defense System Software Development" (PDF).
  16. ^ Lineberger, Rob (Apr 25, 2024). Inheriting Agile: The IT Practitioner's Guide to Managing Software Development in a Post-Agile World. Durham, NC: Sandprint Press. p. 37. ISBN 9798989149605.
  17. ^ a b McConnell, Steve (1996). Rapid Development: Taming Wild Software Schedules. Microsoft Press. ISBN 1-55615-900-5.
  18. ^ "Waterfall Software Development Model". 5 February 2014. Retrieved 11 August 2014.
  19. ^ Arcisphere technologies (2012). "Tutorial: The Software Development Life Cycle (SDLC)" (PDF). Retrieved 2012-11-13.
  20. ^ Hughey, Douglas (2009). "Comparing Traditional Systems Analysis and Design with Agile Methodologies". University of Missouri – St. Louis. Retrieved 11 August 2014.
  21. ^ Parnas, David L.; Clements, Paul C. (1986). "A rational design process: How and why to fake it" (PDF). IEEE Transactions on Software Engineering (2): 251–257. doi:10.1109/TSE.1986.6312940. S2CID 5838439. Retrieved 2011-03-21.
  22. ^ McConnell, Steve (2004). Code Complete, 2nd edition. Microsoft Press. ISBN 1-55615-484-4.
  23. ^ Ensmenger, Nathan (2010). The Computer Boys Take Over. MIT Press. p. 42. ISBN 978-0-262-05093-7.
  24. ^ Larman, Craig; Basili, Victir (2003). "Iterative and Incremental Development: A Brief History". IEEE Computer. 36 (6) (June ed.): 47–56. doi:10.1109/MC.2003.1204375. S2CID 9240477.
  25. ^ "Methodology:design methods".
edit
 
Wikimedia Commons has media related to Waterfall models.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Waterfall_model&oldid=1258230196"