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 detectedtoo late in the software development process. However, many of the problems mentioned in literature are based on beliefs andexperiences, and not on empirical evidence. To address this research gap, we compare the problems in literature with the resultsof a case study at Ericsson AB in Sweden, investigating issues in the waterfall model. The case study aims at validating orcontradicting the beliefs of what the problems are in waterfall development through empirical research.
%0 Journal Article
%1 kai2009waterfall
%A Petersen, Kai
%A Wohlin, Claes
%A Baca, Dejan
%D 2009
%J Product-Focused Software Process Improvement
%K agile development methodology process software waterfall
%P 386-400
%T The Waterfall Model in Large-Scale Development
%U http://dx.doi.org/10.1007/978-3-642-02152-7_29
%X 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 detectedtoo late in the software development process. However, many of the problems mentioned in literature are based on beliefs andexperiences, and not on empirical evidence. To address this research gap, we compare the problems in literature with the resultsof a case study at Ericsson AB in Sweden, investigating issues in the waterfall model. The case study aims at validating orcontradicting the beliefs of what the problems are in waterfall development through empirical research.
@article{kai2009waterfall,
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 detectedtoo late in the software development process. However, many of the problems mentioned in literature are based on beliefs andexperiences, and not on empirical evidence. To address this research gap, we compare the problems in literature with the resultsof a case study at Ericsson AB in Sweden, investigating issues in the waterfall model. The case study aims at validating orcontradicting the beliefs of what the problems are in waterfall development through empirical research.},
added-at = {2009-10-10T17:34:39.000+0200},
author = {Petersen, Kai and Wohlin, Claes and Baca, Dejan},
biburl = {https://www.bibsonomy.org/bibtex/27ed887eab7843362e6f046a158a94f4e/yish},
description = {SpringerLink - Book Chapter},
interhash = {90c07e92a76125fc2c4a5c3224503610},
intrahash = {7ed887eab7843362e6f046a158a94f4e},
journal = {Product-Focused Software Process Improvement},
keywords = {agile development methodology process software waterfall},
pages = {386-400},
timestamp = {2009-10-10T17:34:40.000+0200},
title = {The Waterfall Model in Large-Scale Development},
url = {http://dx.doi.org/10.1007/978-3-642-02152-7_29},
year = 2009
}