A measurement framework for assessing the maturity of requirements engineering process

Software Quality Journal

Volumn 16, Issue 2, 2008, Pages 213-235

  Niazi, Mahmood ^a   Cox, Karl ^b   Verner, June ^b  

^a KEELE UNIVERSITY   (United Kingdom)

^b CSIRO   (Australia)

Author keywords

Process improvement; Process maturity; Requirements engineering

Indexed keywords

SOFTWARE ENGINEERING;

ENTRY POINT; MATURITY MODEL; MEASUREMENT PROCESS; PROCESS IMPROVEMENT; PROCESS MATURITY; REQUIREMENTS ENGINEERING PROCESS; REQUIREMENTS PROCESS; SOFTWARE DEVELOPMENT PROCESS;

REQUIREMENTS ENGINEERING;

EID: 42149166093     PISSN: 09639314     EISSN: 15731367     Source Type: Journal    
DOI: 10.1007/s11219-007-9033-4     Document Type: Article

References (48)

1. Alexander, I., & Stevens, R. (2002). Writing better requirements. Addison-Wesley.
2. Beecham, S., & Hall, T. (2003). Expert panel questionnaire: Validating a requirements process improvement model, http://www.homepages.feis. herts.ac.uk/~pppgroup/requirements_cmm.htm, Site visited May 2003.
3. Beecham, S., Hall, T., & Rainer, A. (2003a). Building a requirements process improvement model. Department of Computer Science, University of Hertfordshire, Technical report No: 378.
4. Beecham, S., Hall, T., & Rainer, A. (2003b). Software process problems in twelve software companies: An empirical analysis. Empirical Software Engineering, 8, 7-42.
5. Boehm, B. W. (1987). Improving software productivity. IEEE Computer, 20(9), 43-57.
6. Briand, L., Wust, J., & Lounis, H. (2001). Replicated case studies for investigating quality factors in object oriented designs. Empirical Software Engineering, 6(1), 11-58.
7. Chatzoglou, P., & Macaulay, L. (1996). Requirements capture and analysis: A survey of current practice. Requirements Engineering Journal, 1, 75-87.
8. Cooper, D., & Schindler, P. (2001). Business research methods (7th ed.). McGraw-Hill.
9. Daskalantonakis, M. K. (1994). Achieving higher SEI levels. IEEE Software, 11(4), 17-24.
10. Davis, F. D. (1989). Perceived usefulness, perceived ease of use, and user acceptance of information technology. MIS Quarterly, 13(3), 319-340.
11. Davis, F. D., Bagozzi, R. P., & Warshaw, P. R. (1989). User acceptance of computer technology: A comparison of two theoretical models. Management Science, 35, 982-1003.
12. Diaz, M., & Sligo, J. (1997). How software process improvement helped Motorola. IEEE Software, 14(5), 75-81.
13. El Emam, K., & Madhavji, H. N. (1995). A field study of requirements engineering practices in information systems development. In Second International Symposium on Requirements Engineering (pp. 68-80).
14. Gorscheck, T., Svahnberg, M., & Kaarina, T. (2003). Introduction and application of a lightweight requirements engineering process evaluation method. In Proceedings of the Requirements Engineering Foundations for Software Quality (REFSQ'03) (pp. 83-92). Klagenfurt/Velden, Austria.
15. Hall, T., Beecham, S., & Rainer, A. (2002). Requirements problems in twelve software companies: An empirical analysis. IEE Proceedings-Software, 149(5), 153-160.
16. Hoffmann, H., & Lehner, F. (2001). Requirements engineering as a success factor in software projects. IEEE Software, 18(4), 58-66.
17. Humphery, W. S. (2002). Three process perspectives: Organizations, teams, and people. Annuls of Software Engineering, 14, 39-72.
18. Jobserve.com. UK Wasting Billions on IT Projects, http://www.jobserve. com/news/NewsStory.asp?e=e&SID=SID2598, 21/4/2004.
19. Kamsties, E., Hormann, K., & Schlich M. (1998). Requirements engineering in small and medium enterprises. Requirements Engineering, 3(2), 84-90.
20. Kauppinen, M., Aaltio, T., & Kujala, S. (2002). Applying the requirements engineering good practice guide for process improvement. In Proceedings of the Seventh European Conference on Software Quality (QC2002) (pp. 45-55).
21. MacDonell, S., & Shepperd, M. (2003). Using prior-phase effort records for re-estimation during software projects. In 9th International Symposium on Software Metrics (pp. 73-86). 3-5 Sept., Sydney, Australia.
22. Marjo, K., & Sari, K. (2001). Assessing requirements engineering processes with the REAIMS model: Lessons learned. In Proceedings of the Eleventh Annual International Symposium of the International Council on Systems Engineering (INCOSE2001).
23. Neill, C. J., & Laplante, P. A. (2003). Requirements engineering: State of the practice. IEEE Software, 18(4), 40-45.
24. Ngwenyama, O., & Nielsen, P. A. (2003). Competing values in software process improvement: An assumption analysis of CMM from an organizational culture perspective. IEEE Transactions on Software Engineering, 50, 100-112.
25. Niazi, M. (2004). A framework for assisting the design of effective software process improvement implementation strategies. Ph.D. thesis, University of Technology Sydney.
26. Niazi, M. (2005a). An empirical study for the improvement of requirements engineering process. In The 17th International Conference on Software Engineering and Knowledge Engineering (pp. 396-399). July 14 to 16, 2005, Taipei, Taiwan, Republic of China.
27. Niazi, M. (2005b). An instrument for measuring the maturity of requirements engineering process. In The 6th International Conference on Product Focused Software Process Improvement (pp. 574-585). LNCS, Oulu, Finland, June 13-16.
28. Niazi, M., Cox, K., & Verner, J. (2005a). An empirical study identifying high perceived value requirements engineering practices. In Fourteenth International Conference on Information Systems Development (ISD'2005). Karlstad University, Sweden August 15-17.
29. Niazi, M., & Shastry, S. (2003). Role of requirements engineering in software development process: An empirical study. In IEEE International Multi-Topic Conference (INMIC03) (pp. 402-407).
30. Niazi, M., Wilson, D., & Zowghi, D. (2005b). A framework for assisting the design of effective software process improvement implementation strategies. Journal of Systems and Software, 78(2), 204-222.
31. Niazi, M., Wilson, D., & Zowghi, D. (2005c). A maturity model for the implementation of software process improvement: An empirical study. Journal of Systems and Software, 74(2), 155-172.
32. Nikula, U., Fajaniemi, J., & Kalviainen, H. (2000). Management view on current requirements engineering practices in small and medium enterprises. In Fifth Australian Workshop on Requirements Engineering (pp. 81-89).
33. Nuseibeh, B., & Easterbrook, S. (2000). Requirements engineering: A roadmap. In 22nd International Conference on Software Engineering (pp. 35-46).
34. Regnell, B., Runeson, P., & Thelin, T. (2000). Are the perspectives really different-further experimentation on scenario-based reading of requirements. Empirical Software Engineering, 5(4), 331-356.
35. Sawyer, P., Sommerville, I., & Viller, S. (1997). Requirements process improvement through the phased introduction of good practice. Software Process-Improvement and Practice, 3, 19-34.
36. ® appraisal method for process improvement (SCAMPISM), Version 1.1: Method Definition Document. SEI, CMU/SEI-2001-HB-001.
37. Siddiqi, J., & Chandra, S. (1996). Requirements engineering: The emerging wisdom. IEEE Software, 13(2), 15-19.
38. Sommerville, I. (1996). Software engineering (5th ed.). Addison-Wesley.
39. Sommerville, I., & Ransom, J. (2005). An empirical study of industrial requirements engineering process assessment and improvement. ACM Transactions on Software Engineering and Methodology, 14(1), 85-117.
40. Sommerville, I., & Sawyer, P. (1997). Requirements engineering-a good practice guide. Wiley.
41. Sommerville, I., Sawyer, P., & Viller, S. (1998). Improving the requirements process. In Fourth International Workshop on Requirements Engineering: Foundation of Software Quality (pp. 71-84).
42. Standish-Group. (1995). Chaos-the state of the software industry. Standish group international technical report, pp. 1-11.
43. Standish-Group. (1999). Chaos: A recipe for success. Standish Group International.
44. Standish-Group. (2003). Chaos-the state of the software industry.
45. Verner, J., Cox, K., Bleistein, S., & Cerpa, N. (2005). Requirements engineering and software project success: An industrial survey in Australia and the US. Australian Journal of Information Systems (to appear Sept 2005).
46. Verner, J., & Evanco, W. M. (2005). In-house software development: What software project management practices lead to success? IEEE Software, 22(1), 86-93.
47. Wiegers, K. E. (2003). Software requirements (2nd ed.). Redmond, WA: Microsoft Press.
48. Yin, R. K. (1993). Applications of case study research. Sage Publications.