The Community for Technology Leaders
Green Image
Issue No. 03 - May/June (2009 vol. 35)
ISSN: 0098-5589
pp: 407-429
Bente C.D. Anda , University of Oslo, Oslo
Audris Mockus , Avaya Labs Research, Basking Ridge
Dag I.K. Sjøberg , Simula Research Laboratory, Lysaker
ABSTRACT
The scientific study of a phenomenon requires it to be reproducible. Mature engineering industries are recognized by projects and products that are, to some extent, reproducible. Yet, reproducibility in software engineering (SE) has not been investigated thoroughly, despite the fact that lack of reproducibility has both practical and scientific consequences. We report a longitudinal multiple-case study of variations and reproducibility in software development, from bidding to deployment, on the basis of the same requirement specification. In a call for tender to 81 companies, 35 responded. Four of them developed the system independently. The firm price, planned schedule, and planned development process, had, respectively, “low,” “low,” and “medium” reproducibilities. The contractor's costs, actual lead time, and schedule overrun of the projects had, respectively, “medium,” “high,” and “low” reproducibilities. The quality dimensions of the delivered products, reliability, usability, and maintainability had, respectively, “low,” "high,” and “low” reproducibilities. Moreover, variability for predictable reasons is also included in the notion of reproducibility. We found that the observed outcome of the four development projects matched our expectations, which were formulated partially on the basis of SE folklore. Nevertheless, achieving more reproducibility in SE remains a great challenge for SE research, education, and industry.
INDEX TERMS
Software engineering life cycle, software quality, software project success, software process, multiple-case study.
CITATION
Bente C.D. Anda, Audris Mockus, Dag I.K. Sjøberg, "Variability and Reproducibility in Software Engineering: A Study of Four Companies that Developed the Same System", IEEE Transactions on Software Engineering, vol. 35, no. , pp. 407-429, May/June 2009, doi:10.1109/TSE.2008.89
93 ms
(Ver )