Abstract
Requirements management is being recognized as one of the most important albeit difficult phases in software engineering. The literature repeatedly cites the role of well-defined requirements and requirements management process in problem analysis and project management as benefiting software development throughout the life cycle: during design, coding, testing, maintenance and documentation of software. This paper reports on the findings of an investigation into industrial practice of requirements management process improvement and its positive effects on downstream software development. The evidence reveals a strong relationship between a well-defined requirements process and increased developer productivity, improved project planning through better estimations and enhanced ability for stakeholders to negotiate project scope. These results are important since there is little empirical evidence of the actual benefits of sound requirements practice, in spite of the plethora of claims in the literature. An account of these effects not only adds to our understanding of good requirements practice but also provides strong motivation for software organizations to develop programs for improvement of their requirements processes.
This is a preview of subscription content, log in via an institution to check access.
Similar content being viewed by others
References
Boehm, B. 1988. A spiral model of software development and enhancement. IEEE Computer 21(2): May, 61–72.
Broadman, J., and Johnson, D. 1996. Return on Investment from Software Process Improvement as Measured by U.S. Industry. Crosstalk 9(4): 23–29.
Brooks, F. 1987. No silver bullet: Essence and accidents of software engineering. Computer 20(4): April, 10–19.
CMM, Capability Maturity Model for Software, 1991: CMU/SEI-91-TR-24, Software Engineering Institute, Carnegie Mellon University.
Curtis, B., Krasner, H., and Iscoe, N. 1988. A field study of the software design process for large systems. Communications of the ACM 31(11): November, 1268–1287.
Damian, D., Zowghi, D., Vaidyanathasamy, L., and Pal, Y. 2004. An industrial case study of immediate benefits of requirements engineering process improvement at the Australian Center for Unisys Software. International Journal of Empirical Software Engineering 9(1–2): March, 45–75.
El Emam, K., and Birk, A. 2000. Validating the ISO/IEC 15504 measure of software requirements analysis process capability. IEEE transactions on Software Engineering 26(6): June, 544–566.
El Emam, K., Dourin, J., and Melo, W. 1998. In: K. El Emam, J. Dourin and W. Melo, (eds), SPICE: The Theory and Practice of Software Process Improvement and Capability Determination. IEEE CS Press.
Hall, T., Beecham S., and Rainer, A. 2002. Requirements problems in twelve software companies: An empirical analysis. IEE Proceedings-Software 149(5): 153–160.
Halligan, R. 2000. TAA’s SE Training Courseware. Halligan Corporation Pty Ltd.
Herbsleb, J., and Goldenson, D. 1996. A systematic survey of CMM experience and results. In Proceedings of the International Conference on Software Engineering, pp. 323–330.
Humphrey W., Snyder, T., and Willis, R. 1991. Software process improvement at hughes aircraft. IEEE Software 8(4): 11–23
Lauessen, S., and Vinter, O. 2001. Preventing requirement defects: An experiment in process improvement. Requirements Engineering Journal 6: 37–50.
Mayo, E. 1933. The Human Problems of an Industrial Civilization. New York, NY: Macmillan Co.
Paulk, M. 1994. A comparison of ISO 9001 and the capability maturity model for software. TR: CMU/SEI-94-TR-12.
Paulk, M., Curtis, B., Chrissis, M. B., and Weber, C. V. 1993. Capability Maturity Model Version 1.1. IEEE Software 10(4), 18–27.
Quality standards: Quality management and quality assurance standards. 1987. Int. Org. for Standardization.
Robertson, S., and Robertson, J. 1999. Mastering the Requirements Process. London: Addison-Wesley.
SEI, 1995: Software Engineering Institute: The Capability Maturity Model: Guidelines for Improving the Software Process. Addison Wesley.
Sommerville. 1996. Software Engineering. England: Addison-Wesley.
Sommerville, and Sawyer, P. 1997. Requirements Engineering: A Good Practice Guide. England: John Wiley & Sons.
The Standish Group, Chaos. 1997. At http://www.standishgroup.com/chaos.html
Wohlwend, H., and Rosenbaum, S. 1993. Software process improvement in an international company. In Proceedings of the International Conference on Software Engineering, pp. 212–220.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
About this article
Cite this article
Damian, D., Chisan, J., Vaidyanathasamy, L. et al. Requirements Engineering and Downstream Software Development: Findings from a Case Study. Empir Software Eng 10, 255–283 (2005). https://doi.org/10.1007/s10664-005-1288-4
Issue Date:
DOI: https://doi.org/10.1007/s10664-005-1288-4