Requirements engineering and downstream software development: Findings from a case study

Empirical Software Engineering

Volumn 10, Issue 3, 2005, Pages 255-283

  Damian, Daniela ^a   Chisan, James ^a   Vaidyanathasamy, Lakshminarayanan ^b   Pal, Yogendra ^b  

^a UNIVERSITY OF VICTORIA   (Canada)

^b Unisys   (United States)

Author keywords

Empirical studies of software process; Industrial experience in process improvement; Requirements management and practice; Software productivity

Indexed keywords

COMPUTER AIDED DESIGN; COMPUTER SOFTWARE; ENCODING (SYMBOLS); INDUSTRIAL MANAGEMENT; MATHEMATICAL MODELS; PARAMETER ESTIMATION; PROGRAM DOCUMENTATION;

EMPIRICAL STUDIES OF SOFTWARE PROCESS; INDUSTRIAL EXPERIENCE IN PROCESS IMPROVEMENT; REQUIREMENTS MANAGEMENT AND PRACTICES; SOFTWARE PRODUCTIVITY;

COMPUTER AIDED ENGINEERING;

EID: 21644466430     PISSN: 13823256     EISSN: None     Source Type: Journal    
DOI: 10.1007/s10664-005-1288-4     Document Type: Article

References (23)

1. Boehm, B. 1988. A spiral model of software development and enhancement. IEEE Computer 21(2): May, 61-72.
2. Broadman, J., and Johnson, D. 1996. Return on investment from software process improvement as measured by U.S. industry. Crosstalk 9(4): 23-29.
3. Brooks, F. 1987. No silver bullet: Essence and accidents of software engineering. Computer 20(4): April, 10-19.
4. CMM, Capability Maturity Model for Software, 1991: CMU/SEI-91-TR-24, Software Engineering Institute, Carnegie Mellon University.
5. 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.
6. 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.
7. 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.
8. 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.
9. Hall, T., Beecham S., and Rainer, A. 2002. Requirements problems in twelve software companies: An empirical analysis. IEE Proceedings-Software 149(5): 153-160.
10. Halligan, R. 2000. TAA's SE Training Courseware. Halligan Corporation Pty Ltd.
11. Herbsleb, J., and Goldenson, D. 1996. A systematic survey of CMM experience and results. In Proceedings of the International Conference on Software Engineering. ACM Press, pp. 323-330.
12. Humphrey W., Snyder, T., and Willis, R. 1991. Software process improvement at hughes aircraft. IEEE Software 8(4): 11-23.
13. Lauesen, S., and Vinter, O. 2001. Preventing requirement defects: An experiment in process improvement. Requirements Engineering Journal 6: 37-50.
14. Mayo, E. 1933. The Human Problems of an Industrial Civilization. New York, NY: Macmillan Co.
15. Paulk, M. 1994. A comparison of ISO 9001 and the capability maturity model for software. TR: CMU/SEI-94-TR-12.
16. Paulk, M., Curtis, B., Chrissis, M. B., and Weber, C. V. 1993. Capability Maturity Model Version 1.1. IEEE Software 10(4): 18-27.
17. Quality standards: Quality management and quality assurance standards. 1987. Int. Org. for Standardization.
18. Robertson, S., and Robertson, J. 1999. Mastering the Requirements Process. London: Addison-Wesley.
19. SEI, 1995: Software Engineering Institute: The Capability Maturity Model: Guidelines for Improving the Software Process. Addison Wesley.
20. Sommerville. 1996. Software Engineering. England: Addison-Wesley.
21. Sommerville, and Sawyer, P. 1997. Requirements Engineering: A Good Practice Guide. England: John Wiley & Sons.
22. The Standish Group. Chaos. 1997. At http://www.standishgroup.com/chaos. html.
23. 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.