The Waterfall Model
| Line 6: | Line 6: | ||
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. | 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. | ||
| − | This article introduces | + | '''This article introduces ''' |
| + | |||
- The waterfall model | - The waterfall model | ||
| + | |||
- When to use it | - When to use it | ||
| + | |||
- Where to use it | - Where to use it | ||
| − | - | + | |
| − | - | + | - What each phase consists of |
| − | - | + | |
| + | - Best practice | ||
| + | |||
| + | - Pros and cons. | ||
Revision as of 00:00, 12 February 2022
Abstract
The waterfall model is a Systems 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.
This article introduces
- The waterfall model
- When to use it
- Where to use it
- What each phase consists of
- Best practice
- Pros and cons.
References
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/
