Quantifying the impact of requirements definition and management process maturity on project outcome in large business application development

Requirements Engineering

Volumn 18, Issue 3, 2013, Pages 223-249

  Ellis, Keith ^a   Berry, Daniel M ^b  

^a LANCASTER UNIVERSITY   (United Kingdom)

^b UNIVERSITY OF WATERLOO   (Canada)

Author keywords

Commercial application (CA) development; Empirical study; On budget; On function; On time; RDM maturity; Requirements discovery and management (RDM); Successful CA development; Survey

Indexed keywords

COMMERCIAL APPLICATIONS; EMPIRICAL STUDIES; ON-BUDGET; ON-FUNCTION; ON-TIME; RDM MATURITY; REQUIREMENTS DISCOVERY; SUCCESSFUL CA DEVELOPMENT;

BUDGET CONTROL; PROJECT MANAGEMENT; SURVEYING;

SURVEYS;

EID: 84881615480     PISSN: 09473602     EISSN: 1432010X     Source Type: Journal    
DOI: 10.1007/s00766-012-0146-3     Document Type: Article

References (45)

1. Abbott B (2001) Requirements set the mark. InfoWorld 23(10): 45-46.
2. Agile Alliance Principles (2001) The agile alliance 2001. http://www. agilealliance. org/.
3. Alexander L, Davis A (1991) Criteria for the selection of a software process model. In: Knafl G (ed) Proceedings of the fifteenth annual computer software and application conference. pp 521-528.
4. Berry DM, Damian D, Finkelstein A, Gause D, Hall R, Wassyng A (2005) To do or not to do: if the requirements engineering payoff is so good, why aren't more companies doing it? In: Proceedings of the IEEE international conference on requirements engineering (RE), p 447, http://www. requirements-engineering. org/REnotDonePanelRE05/.
5. Boehm BW, Abts C, Brown AW, Chulani S, Clark BK, Horowitz E, Madachy R, Reifer DJ, Steece B (2000) Software cost estimation with COCOMO II. Prentice Hall, Upper Saddle River, NJ.
6. Bourque P, Dupuis R, Abran A, Moore JW, Tripp L (1999) The guide to the software engineering body of knowledge. IEEE Softw 16: 35-44.
7. Brooks F (1987) No silver bullet-essence and accidents of software engineering. IEEE Comput 20(4): 10-19.
8. Curtis B, Krasner H, Iscoe N (1988) A field study of the software design process for large systems. Commun ACM 31(11): 1268-1287.
9. Damian D, Chisan J (2006) An empirical study of the complex relationships between requirements engineering processes and other processes that lead to payoffs in productivity, quality, and risk management. IEEE Trans Softw Eng 32(7): 433-453.
10. Damian D, Chisan J, Vaidyanathasamy L, Pal Y (2005) Requirements engineering and downstream software development: findings from a case study. Empir Softw Eng 10(3): 255-283.
11. Damian D, Zowghi D, Vaidyanathasamy L, Pal Y (2004) An industrial case study of immediate benefits of requirements engineering process improvement at the australian center for unisys software. Empir Softw Eng 9(1-2): 45-75.
12. El Emam K, Madhavji NH (1995) A field study of requirements engineering practices in information systems development. In: Proceedings of the second IEEE international symposium on requirements engineering (RE), p 68.
13. Ellis K (2008) Business analysis benchmark. Technical report, IAG Consulting, Oakville, ON, Canada, http://www2. iag. biz/benchmark-2008.
14. Ellis K (2009) Business analysis benchmark-2009. Technical report. IAG Consulting, Oakville, ON, Canada http://www. iag. biz/resources/library/download-business-analysis-benchmark-2009. html.
15. Fenton N, Pfleeger SL, Glass RL (1994) Science and substance: a challenge to software engineers. IEEE Softw 11: 86-95.
16. Galin D, Avrahami M (2006) Are CMM program investments beneficial? Analyzing past studies. IEEE Softw 23(6): 81-87.
17. Gibson DL, Goldenson DR, Kost K (2006) Performance results of CMMI-based process improvement. Technical report. The Software Engineering Institute, Carnegie Mellon University, Pittsburgh, PA, USA. http://www. sei. cmu. edu/reports/06tr004. pdf.
18. Haase V, Messnarz R, Koch G, Kugler HJ, Decrinis P (1994) Bootstrap: fine-tuning process assessment. IEEE Softw 11: 25-35.
19. Hall T, Beecham S, Rainer A (2002) Requirements problems in twelve software companies: an empirical analysis. IEE Proc Softw 149: 153-160.
20. Harry M, Schroeder R (2000) Six Sigma: the breakthrough management strategy revolutionizing the world's top corporations. Currency, New York, NY.
21. Herbsleb JD, Goldenson DR (1996) A systematic survey of CMM experience and results. In: Proceedings of the eighteenth international conference on software engineering (ICSE). pp 323-330.
22. Herzberg F (1959) The motivation to work. Wiley, New York, NY.
23. Hofmann HF, Lehner F (2001) Requirements engineering as a success factor in software projects. IEEE Softw 18(4): 58-66.
24. IAG Consulting (2002). IAG performance benchmark. http://www. iag. biz.
25. International Institute of Business Analysis (2010) Business analysis body of knowledge (BABOK), Version 2. 0. http://www. theiiba. org.
26. International Standards Organization (2010) ISO 9000-Quality management. Viewed 10 August 2010. http://www. iso. org/iso/iso_catalogue/management_standards/quality_management. htm.
27. International Standards Organization (2010) ISO 9001: 2000, Quality management systems-requirements. Viewed 10 August 2010. http://www. iso. org/iso/iso_catalogue/catalogue_tc/catalogue_detail. htm?csnumber=21823.
28. Jones C (1996) Applied software measurement: assuring productivity and quality. McGraw-Hill, New York, NY.
29. Kerton B (2006) Flawed requirements trigger 70% of project failures. Infotech Research. http://www. infotech. com/research/flawed-requirements-trigger-70-of-project-failures.
30. Kitchenham B, Pfleeger SL (2002) Principles of survey research, part 4: questionnaire evaluation. SIGSOFT Softw Eng Note 27: 20-23.
31. Lauesen S, Vinter O (2001) Preventing requirement defects: an experiment in process improvement. Requir Eng 6: 37-50.
32. Leffingwell D (1997) Calculating the return on investment from more effective requirements management. Am Prog 10(4): 13-16.
33. Lubars M, Potts C, Richter C (1993) A review of the state of the practice in requirements modeling. In: Proceedings of the IEEE international symposium on requirements engineering (RE), pp 2-14.
34. Paech B, Koenig T, Borner L, Aurum A (2005) An analysis of empirical requirements engineering survey data. In: Engineering and managing software requirements, Part 3. Springer, Berlin. pp 427-452.
35. Paulk MC, Curtis B, Chrissis MB, Weber CV (1993) Capability maturity model, version 1. 1. IEEE Softw 10(4): 18-27.
36. Requirements-engineering. org. RE Day 2005 Website. Viewed 10 August 2010. http://www. requirements-engineering. org/REday05/.
37. Sadraei E, Aurum A, Beydoun G, Paech B (2007) A field study of the requirements engineering practice in australian software industry. Requir Eng J 12: 145-162.
38. Sawyer P, Sommerville I, Viller S (1999) Capturing the benefits of requirements engineering. IEEE Softw 16(2): 78-85.
39. Software Engineering Institute (2010) CMMI overview. Viewed 10 August 2010. http://www. sei. cmu. edu/cmmi/.
40. Sommerville I, Sawyer P (1997) Requirements engineering: a good practice guide. Wiley, Chichester.
41. The Standish Group (2009) CHAOS summary 2009. http://www1. standishgroup. com/newsroom/chaos_2009. php.
42. United States Government Accountability Office (2008). Report to congressional requesters: information technology: agencies need to establish comprehensive policies to address changes to projects' cost, schedule, and performance goals, http://www. gao. gov/new. items/d08925. pdf.
43. Wang Y, Court I, Ross M, Staples G, King G, Dorling A (1997) Quantitative evaluation of the SPICE, CMM, IS0 9000 and BOOTSTRAP. In: Proceedings of the third international software engineering standards symposium (ISESS), pp 57-68.
44. Wiegers KE (2003) Software requirements. 2nd edn. Microsoft Press, Redmond, WA.
45. Wohlin C, Runeson P, Höst M, Ohlsson MC, Regnell B, Wesslén A (2000) Experimentation in software engineering: an introduction. Kluwer Academic Publishers, Norwell, MA.