Waterfall Model
- Reference work entry
- pp 2343–2344
- Cite this reference work entry
- Linda Sherrell Ph.D. 3
715 Accesses
2 Citations
4 Altmetric
The Waterfall Model is a software development life cycle model that was originally defined by Royce around 1970. This model has the advantage of dividing the life cycle into phases that are easily understood by management. The phases follow:
Requirements (the needs of the customer are collected).
Specification (a formal document containing the requirements is constructed).
Architectural – the modules for the program are specified.
Detailed Design – the algorithms and the data structures are defined.
Implementation (coding is completed).
Unit Testing (the components are tested individually).
Integration Testing (the components are combined and tested).
Post-delivery Maintenance (corrections or enhancements are made to the code).
Retirement (the code can no longer be maintained or is obsolete so it is removed from service) (Fig. 1 ).
A modern waterfall model (Adapted from Schach 2007)
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Subscribe and save.
- Get 10 units per month
- Download Article/Chapter or eBook
- 1 Unit = 1 Article or 1 Chapter
- Cancel anytime
- Available as PDF
- Read on any device
- Instant download
- Own it forever
- Available as EPUB and PDF
- Durable hardcover edition
- Dispatched in 3 to 5 business days
- Free shipping worldwide - see info
Tax calculation will be finalised at checkout
Purchases are for personal use only
Institutional subscriptions
Schach, S. R. (2007). Object-oriented and classical software engineering (7th ed.). New York: McGraw-Hill.
Google Scholar
Download references
Author information
Authors and affiliations.
Department of Computer Science, The University of Memphis, 375 Dunn Hall, Memphis, TN, 38017, USA
Prof. Linda Sherrell Ph.D. ( Visiting Associate Professor )
You can also search for this author in PubMed Google Scholar
Corresponding author
Correspondence to Linda Sherrell Ph.D. .
Editor information
Editors and affiliations.
Department of Systematic Theology, Faculty of Theology, Copenhagen University, Copenhagen, Denmark
Anne L. C. Runehov
Pontificia Universita Antonianum, Roma, Italia
Lluis Oviedo
Rights and permissions
Reprints and permissions
Copyright information
© 2013 Springer Science+Business Media Dordrecht
About this entry
Cite this entry.
Sherrell, L. (2013). Waterfall Model. In: Runehov, A.L.C., Oviedo, L. (eds) Encyclopedia of Sciences and Religions. Springer, Dordrecht. https://doi.org/10.1007/978-1-4020-8265-8_200285
Download citation
DOI : https://doi.org/10.1007/978-1-4020-8265-8_200285
Publisher Name : Springer, Dordrecht
Print ISBN : 978-1-4020-8264-1
Online ISBN : 978-1-4020-8265-8
eBook Packages : Humanities, Social Sciences and Law Reference Module Humanities and Social Sciences Reference Module Humanities
Share this entry
Anyone you share the following link with will be able to read this content:
Sorry, a shareable link is not currently available for this article.
Provided by the Springer Nature SharedIt content-sharing initiative
- Publish with us
Policies and ethics
- Find a journal
- Track your research
IMAGES
COMMENTS
This paper discusses two main software engineering methodologies to system development, the waterfall model and the object-oriented approach.
The Waterfall Model is a linear application development model that uses rigid phases: When one phase ends, the next begins. Steps occur in sequence, and, if unmodified, the model does not allow developers to go back to previous steps (hence “waterfall”: Once water falls down, it cannot go back up). Exam Warning.
This paper discusses best practices for the Systems Development Lifecycle (SDLC) based on the Waterfall Model. Topics covered include an introduction to the Systems Development Lifecycle and the Waterfall Model including advantages and disadvantages.
This paper briefly discusses the Waterfall Model while describing best practices for each stage of the Systems Development Lifecycle. LITERATURE REVIEW. Meir “Manny” Lehman discussed one of...
To address this research gap, we compare the problems in literature with the results of a case study at Ericsson AB in Sweden, investigating issues in the waterfall model.
However, many of the problems mentioned in literature are based on beliefs and experiences, and not on empirical evidence. To address this research gap, we compare the problems in literature with the results of a case study at Ericsson AB in Sweden, investigating issues in the waterfall model.
In this section, we provide an overview of the relevant literature introducing the innovation of software development processes and the idea of a lifecycle. We then present the waterfall model, which is perceived as the first software development lifecycle, as well as our motivation for its study. 2.1. The Software Development Lifecycle
The Waterfall Model is a software development life cycle model that was originally defined by Royce around 1970. This model has the advantage of dividing the life cycle into phases that are easily understood by management. The phases follow: Requirements (the needs of the customer are collected).
The case study makes the following contributions to research on waterfall development: 1) Illus-tration of the waterfall implementation in practice within large-scale industrial software development, 2) Identification of issues related to the waterfall model and their prioritization showing the most critical issues, and 3) Comparison of case stu...
The waterfall methodology uses a sequential or linear approach to software development. The project is broken down into a sequence of tasks, with the highest level grouping referred to as phases. A true waterfall approach requires phases that are completed in sequence and have formal exit criteria, typically a sign-off by the project stakeholders.