Abstract
Waterfall development is still a widely used way of working in software development companies. Many problems have been reported related to the model. Commonly accepted problems are for example to cope with change and that defects all too often are detected too late in the software development process. 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. The case study aims at validating or contradicting the beliefs of what the problems are in waterfall development through empirical research.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Royce, W.: Managing the development of large software systems: Concepts and techniques. In: Proc. IEEE WESCOM. IEEE Computer Society Press, Los Alamitos (1970)
Sommerville, I.: Software Engineering, 7th edn. Pearson Eductation Ltd., London (2004)
Raccoon, L.B.S.: Fifty years of progress in software engineering. SIGSOFT Softw. Eng. Notes 22(1), 88–104 (1997)
Yin, R.K.: Case Study Research: Design and Methods, 3rd edn. Applied Social Research Methods Series, vol. 5. Prentice Hall, Englewood Cliffs (2002)
McBreen, P.: Software craftsmanship: the new imperative. Addison-Wesley, Boston (2002)
Pfleeger, S.L., Atlee, J.M.: Software engineering: theory and practice, 3rd edn. Prentice Hall, Upper Saddle River (2006)
Jarzombek, J.: The 5th annual jaws s3 proceedings (1999)
Thomas, M.: It projects sink or swim. British Computer Society Review 2001 (2001)
Johnson, J.: Keynote speech: Build only the features you need. In: Proceedings of the 4th International Conference on Extreme Programming and Agile Processes in Software Engineering (XP 2002) (2002)
Jones, C.: Patterns of Software Systems: Failure and Success. International Thomson Computer Press (1995)
Sametinger, J.: Software engineering with reusable components: with 26 tables. Springer, Berlin (1997)
Anderson, D.J.: Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results (The Coad Series). Prentice Hall PTR, Englewood Cliffs (2003)
Cohen, D., Larson, G., Ware, B.: Improving software investments through requirements validation. In: Proceedings of the 26th Annual NASA Goddard Software Engineering Workshop (SEW 2001), Washington, DC, USA, p. 106. IEEE Computer Society, Los Alamitos (2001)
Boehm, B.: Get ready for agile methods, with care. Computer 35(1), 64–69 (2002)
Karlström, D., Runeson, P.: Combining agile methods with stage-gate project management. IEEE Software 22(3), 43–49 (2005)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2009 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
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/10.1007/978-3-642-02152-7_29
Download citation
DOI: https://doi.org/10.1007/978-3-642-02152-7_29
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-02151-0
Online ISBN: 978-3-642-02152-7
eBook Packages: Computer ScienceComputer Science (R0)