Waterfall model

The waterfall model is the process of performing the typical software development life cycle (SDLC) phases in sequential order. Each phase is completed before the next is started, and the result of each phase drives subsequent phases.^[1] Compared to alternative SDLC methodologies, it is among the least iterative and flexible,^[1] as progress flows largely in one direction (like a waterfall) through the phases of conception, requirements analysis, design, construction, testing, deployment, and maintenance.^[2] The waterfall model is the earliest SDLC methodology.^[3] When first adopted, there were no recognized alternatives for knowledge-based creative work.^[4]

^ ^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.
^ Tom Gilb (1985). "Evolutionary Delivery versus the "waterfall model"". ACM SIGSOFT Software Engineering Notes. 10 (3): 49–61. doi:10.1145/1012483.1012490.
^ Linda Sherrell (2013). "Waterfall Model". In A. L. C. Runehov; L. Oviedo (eds.). Encyclopedia of Sciences and Religions. Dordrecht, The Netherlands: Springer. pp. 2343–2344. doi:10.1007/978-1-4020-8265-8_200285. ISBN 978-1-4020-8264-1.
^ 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.

[:0-1] 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 (1985). "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". In A. L. C. Runehov; L. Oviedo (eds.). Encyclopedia of Sciences and Religions. Dordrecht, The Netherlands: Springer. pp. 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.

[1]

[2]

[3]

[4]

Waterfall model

From Wikipedia, the free encyclopedia · View on Wikipedia