The Waterfall Model

From apppm
Revision as of 13:37, 16 February 2022 by S220123 (Talk | contribs)

Jump to: navigation, search

Contents

Abstract

The waterfall model is a Software Development Life Cycle model (SDLC) and was the first process model to be introduced. The waterfall model is easy to understand and use, it is a stage gate model which means that the model consists of stages and gates. Each phase consists of one stage and one gate. Each phase has some pre-determined activities and requirements. The current phase must be completed before the next phase can begin and to end a phase it must pass a gate. A stage is the activities, and the gate is the requirement and the review that determine whether a project can continue. The waterfall model consists of six different stages, 1) Requirements Gathering and Analysis, 2) Systems Development, 3) Systems Implementation and Coding, 4) Testing, 5) Deployment, 6) Systems Operations and Maintenance.

The waterfall model is widely used for software development, but it is also a widely criticized model. The model is often criticized for the late detection of defects in the process and how to handle change requests among other things. It is most optimal to use the waterfall model for simple projects with clear reqirements and projects that do not change through the development process.

About

The first description of the Waterfall model was written by Winston W. Royce in 1970. Back then he did not call it the Waterfall model. [1] Later it got the name because all the phases are done one by one and flows downwards like a waterfall. It is the finest and oldest known Software Development Life Cycle models (SDLC). There are defined and designed various Software Development Life Cycle models such as Spiral model, Big Bang Model, Iterative model etc. These models are also called Software Development Process Models and are all "process consisting of a sequence of planned phases to develop or to amend the software products." [2]


Figure 3: Application of the Waterfall model

This article introduces

- The waterfall model

- When to use it

- Where to use it

- What each phase consists of

- Best practice

- Pros and cons.

Ref

Petersen K., Wohlin C., Baca D. (2009) The Waterfall Model in Large-Scale Development. In: Bomarius F., Oivo M., Jaring P., Abrahamsson P. (eds) Product-Focused Software Process Improvement. PROFES 2009. Lecture Notes in Business Information Processing, vol 32. Springer, Berlin, Heidelberg. https://doi-org.proxy.findit.cvt.dk/10.1007/978-3-642-02152-7_29

Kramer, Mitch, Best Practices in Systems Development Lifecycle: An Analyses Based on the Waterfall Model (2018). Review of Business & Finance Studies, v. 9 (1) p. 77-84, Available at SSRN: https://ssrn.com/abstract=3131958

http://tryqa.com/what-is-waterfall-model-advantages-disadvantages-and-when-to-use-it/


References

  1. Petersen K., Wohlin C., Baca D. (2009) The Waterfall Model in Large-Scale Development. In: Bomarius F., Oivo M., Jaring P., Abrahamsson P. (eds) Product-Focused Software Process Improvement. PROFES 2009. Lecture Notes in Business Information Processing, vol 32. Springer, Berlin, Heidelberg. https://doi-org.proxy.findit.cvt.dk/10.1007/978-3-642-02152-7_29
  2. Dubey A.; Jain A.; Mantri A., "Comparative Study: Waterfall v/s Agile Model", International Journal of Engineering Sciences & Research Technology (IJESRT), 2015
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox