The Waterfall Model in Large-Scale Development

Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 32)


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.


Requirement Engineering Abstraction Level Fault Slip Life Cycle Management Change Request 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Royce, W.: Managing the development of large software systems: Concepts and techniques. In: Proc. IEEE WESCOM. IEEE Computer Society Press, Los Alamitos (1970)Google Scholar
  2. 2.
    Sommerville, I.: Software Engineering, 7th edn. Pearson Eductation Ltd., London (2004)zbMATHGoogle Scholar
  3. 3.
    Raccoon, L.B.S.: Fifty years of progress in software engineering. SIGSOFT Softw. Eng. Notes 22(1), 88–104 (1997)CrossRefGoogle Scholar
  4. 4.
    Yin, R.K.: Case Study Research: Design and Methods, 3rd edn. Applied Social Research Methods Series, vol. 5. Prentice Hall, Englewood Cliffs (2002)Google Scholar
  5. 5.
    McBreen, P.: Software craftsmanship: the new imperative. Addison-Wesley, Boston (2002)Google Scholar
  6. 6.
    Pfleeger, S.L., Atlee, J.M.: Software engineering: theory and practice, 3rd edn. Prentice Hall, Upper Saddle River (2006)Google Scholar
  7. 7.
    Jarzombek, J.: The 5th annual jaws s3 proceedings (1999)Google Scholar
  8. 8.
    Thomas, M.: It projects sink or swim. British Computer Society Review 2001 (2001)Google Scholar
  9. 9.
    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)Google Scholar
  10. 10.
    Jones, C.: Patterns of Software Systems: Failure and Success. International Thomson Computer Press (1995)Google Scholar
  11. 11.
    Sametinger, J.: Software engineering with reusable components: with 26 tables. Springer, Berlin (1997)CrossRefzbMATHGoogle Scholar
  12. 12.
    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)Google Scholar
  13. 13.
    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)Google Scholar
  14. 14.
    Boehm, B.: Get ready for agile methods, with care. Computer 35(1), 64–69 (2002)CrossRefGoogle Scholar
  15. 15.
    Karlström, D., Runeson, P.: Combining agile methods with stage-gate project management. IEEE Software 22(3), 43–49 (2005)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  1. 1.Blekinge Institute of TechnologyRonnebySweden
  2. 2.Ericsson ABKarlskronaSweden

Personalised recommendations