Share This Article:

A New Maturity Model for Requirements Engineering Process: An Overview

Full-Text HTML XML Download Download as PDF (Size:132KB) PP. 340-350
DOI: 10.4236/jsea.2012.55040    5,217 Downloads   9,579 Views   Citations


It is widely acknowledged that Requirements Engineering (RE) has an important implication for the overall success of software or system development projects. As more and more organizations consider RE as the principal problem areas in the projects, improving RE process therefore appears critical for future business success. Moreover, nowadays there are evidences that support improving RE process maturity can contributes to improved business performance. There exist generic Software Process Improvement (SPI) standards, specialised RE process improvement models as well as guidance and advices on RE. However, they suffer from various issues that limit their adoption by organizations that are interested to assess and improve their RE process capability. Therefore, the research presented in this paper proposes a new RE process improvement model. The model is built by adapting and expanding the structure of the continuous representation of the formal maturity framework Capability Maturity Model Integration for Development (CMMI-DEV) developed by the Software Engineering Institute (SEI) through three rounds of development and validation stages, which involved RE and CMMI expert panel in the software industry. This paper aims to provide an overview on what, why and how we build the maturity model for RE. The intention is to provide a foundation for future development in the area of RE process improvement.

Cite this paper

B. Solemon, S. Sahibuddin and A. Ghani, "A New Maturity Model for Requirements Engineering Process: An Overview," Journal of Software Engineering and Applications, Vol. 5 No. 5, 2012, pp. 340-350. doi: 10.4236/jsea.2012.55040.


[1] I. Sommerville and P. Sawyer, “Requirements Engineering: A Good Practice Guide,” John Wiley & Sons, Chichester, 1997.
[2] R. R. Young, “Effective Requirements Practices,” Addison-Wesley Longman Publishing Co., Inc., Boston, 2001.
[3] H. F. Hofmann and F. Lehner, “Requirements Engineering as a Success Factor in Software Projects,” Software, IEEE, Vol. 18, No. 4, 2001, pp. 58-66. doi:10.1109/MS.2001.936219
[4] S. Martin, A. Aurum, R. Jeffery and B. Paech, “Requirements Engineering Process Models in Pactice,” Proceedings of the Seventh Australian Workshop in Requirements Engineering (AWRE’2002), Deakin University, Melbourne, 2-3 December 2002, pp. 141-155.
[5] J. Chisan, “Theory in Practice: A Case Study of Requirements Engineering Process Improvement,” Master Thesis, the University of Victoria, Victoria, 2005.
[6] D. Damian, D. Zowghi, L. Vaidyanathasamy and Y. Pal, “An industrial Case Study of Immediate Benefits of Requirements Engineering Process Improvement at the Australian Center for Unisys Software,” Empirical Software Engineering, Vol. 9, No. 1, 2004, pp. 45-75. doi:10.1007/s10664-005-1288-4
[7] H. Wohlwend and S. Rosenbaum, “Software Improvements in an International Company,” Proceedings of the 15th International Conference on Software Engineering (ICSE 93), Baltimore, Maryland, 17-21 May 1993, pp. 212-220.
[8] S. Lauesen and O. Vinter, “Preventing Requirement Defects: An Experiment in Process Improvement,” Requirements Engineering, Vol. 6, No. 1, 2001, pp. 37-50. doi:10.1007/PL00010355
[9] J. D. Herbsleb and D. R. Goldenson, “A Systematic Survey of CMM Experience and Results,” Proceedings of the 18th International Conference on Software Engineering—ICSE, Berlin, 25-29 March 1996, pp. 323-330.
[10] J. G. Brodman and D. L. Johnson, “Return on Investment (ROI) from Software Process Improvement as Measured by US Industry,” Software Process: Improvement and Practice, Vol. 1, No. 1, 1995, pp. 35-47.
[11] IEEE, “IEEE Guide for Developing System Requirements Specifications. IEEE Std 1233, 1998 Edition,” Institute of Electrical and Electronics Engineers, Inc., New York, 1998.
[12] IEEE, “IEEE Recommended Practice for Software Requirements Specifications. IEEE Std 830-1998,” Institute of Electrical and Electronics Engineers, Inc., New York, 1998.
[13] P. Sawyer, “Maturing Requirements Engineering Process Maturity Models,” In: J. L. Mate and A. Silva, Eds., Requirements Engineering for Sociotechnical Systems, Idea Group Inc., Hershey, 2004, pp. 84-99.
[14] S. Beecham, T. Hall and A. Rainer, “Defining a Requirements Process Improvement Model,” Software Quality Journal, Vol. 13, No. 3, 2005, pp. 247-279. doi:10.1007/s11219-005-1752-9
[15] S. Beecham, T. Hall and A. Rainer, “Software Process Improvement Problems in Twelve Software Companies: An Empirical Analysis,” Empirical Software Engineering, Vol. 8, No. 1, 2003, pp. 7-42. doi:10.1023/A:1021764731148
[16] T. Hall, S. Beecham and A. Rainer, “Requirements Problems in Twelve Software Companies: An Empirical Analysis,” IEE Proceedings of Software, Vol. 149, No. 5, 2002, pp. 153-160. doi:10.1049/ip-sen:20020694
[17] M. Niazi and S. Shastry, “Role of Requirements Engineering in Software Development Process: An Empirical Study,” Proceedings of the Multi Topic Conference (INMIC 2003), Islamabad, 8-9 December 2003, pp. 402-407.
[18] B. Solemon, S. Sahibuddin and A. A. A. Ghani, “Requirements Engineering Problems and Practices in Software Companies: An Industrial Survey,” Advances in Software Engineering, Vol. 59, 2009, pp. 70-77. doi:10.1007/978-3-642-10619-4_9
[19] M. Ibanez and H. Rempp, “European Survey Analysis,” European Software Institute, Technical Report, 1996.
[20] N. P. Napier, J. Kim and L. Mathiassen, “Software Process Re Engineering: A Model and Its Application to an Industrial Case Study,” Software Process: Improvement and Practice, Vol. 13, No. 5, 2008, pp. 451-471. doi:10.1002/spip.390
[21] M. B. Chrissis, M. Konrad and S. Shrum, “CMMI: Guidelines for Process Integration and Product Improvement,” 2nd Edition, Upper Saddle River, Addison-Wesley, Boston, 2007.
[22] J. R. Persse, “Process Improvement Essentials: CMMI, Six SIGMA, and ISO 9001,” O’Reilly Media, Inc., Sebastopol, 2006.
[23] S. Beecham, T. Hall and A. Rainer, “Building a Requirements Process Improvement Model,” University of Hertfordshire, Technical Report, Hatfield, No. 378, 2003.
[24] T. Gorschek and K. Tejle, “A Method for Assessing Requirements Engineering Process Maturity in Software Projects,” Master Thesis, Department of Software Engineering and Computer Science, Blekinge Institute of Technology, Ronneby, 2002.
[25] F. Pettersson, M. Ivarsson, T. Gorschek and P. Ohman, “A Practitioner’s Guide to Light Weight Software Process Assessment and Improvement Planning,” Journal of Systems and Software, Vol. 81, No. 6, 2007, pp. 972-995. doi:10.1016/j.jss.2007.08.032
[26] N. Dalkey and O. Helmer, “An Experimental Application of the Delphi Method to the Use of Experts,” Management Science, Vol. 9, No. 3, 1963, pp. 458-467. doi:10.1287/mnsc.9.3.458
[27] B. F. Beech, “Changes: The Delphi Technique Adapted for Classroom Evaluation of Clinical Placements,” Nurse Education Today, Vol. 11, No. 3, 1991, pp. 207-212. doi:10.1016/0260-6917(91)90061-E
[28] F. T. Hartman and A. Baldwin, “Using Technology to Improve Delphi Method,” Journal of Computing in Civil Engineering, Vol. 9, No. 4, 1995, pp. 244-249. doi:10.1061/(ASCE)0887-3801(1995)9:4(244)
[29] P. M. Mullen, “Delphi: Myths and Reality,” Journal of Health Organization and Management, Vol. 17, No. 1, 2003, pp. 37-52. doi:10.1108/14777260310469319
[30] G. J. Skulmoski, F. T. Hartman and J. Krahn, “The Delphi Method for Graduate Research,” Journal of Information Technology Education, Vol. 6, 2007, pp. 1-21.
[31] J. A. Cantrill, B. Sibbald and S. Buetow, “The Delphi and Nominal Group Techniques in Health Services Research,” International Journal of Pharmacy Practice, Vol. 4, No. 2, 1996, pp. 67-74. doi:10.1111/j.2042-7174.1996.tb00844.x
[32] S. S. Y. Lam, K. L. Petri and A. E. Smith, “Prediction and Optimization of a Ceramic Casting Process Using a Hierarchical Hybrid System of Neural Networks and Fuzzy Logic,” IIE Transactions, Vol. 32, No. 1, 2000, pp. 83-91. doi:10.1023/A:1007659531734
[33] B. Solemon, S. Shahibuddin and A. A. A. Ghani, “Redefining the Requirements Engineering Process Improvement Model,” Proceedings of the Asia-Pacific Software Engineering Conference, APSEC 2009, Penang, 1-3 December 2009, pp. 87-92.
[34] W. Hayes, E. E. Miluk, L. Ming and M. Glover, “Handbook for Conducting Standard CMMI Appraisal Method for Process Improvement (SCAMPI) B and C Appraisals, Version 1.1,” Software Engineering Institute (SEI), Pittsburgh, 2005.
[35] F. McCaffery, D. McFall and F. G. Wilkie, “Improving the Express Process Appraisal Method,” In: F. Bomarius and S. KomiSirvio, Eds., Product Focused Software Process Improvement, Springer, 2005, pp. 286-298.
[36] K. E. Wiegers and D. C. Sturzenberger, “A Modular Software Process Mini-Assessment Method,” IEEE Software, Vol. 17, No. 1, 2000, pp. 62-69.
[37] D. Linscomb, “Requirements Engineering Maturity in the CMMI,” 5 June 2008.
[38] S. Beecham, T. Hall, C. Britton, M. Cottee and A. Rainer, “Using an Expert Panel to Validate a Requirements Process Improvement Model,” Journal of Systems and Software, Vol. 76, No. 3, 2005, pp. 251-275. doi:10.1016/j.jss.2004.06.004
[39] A. Gomes and A. Pettersson, “Market-Driven Requirements Engineering Process Model-MDREPM,” Master Thesis, Blekinge Institute of Technology, Ronneby, 2007.
[40] I. Sommerville and J. Ransom, “An Empirical Study of Industrial Requirements Engineering Process Assessment and Improvement,” ACM Transactions on Software Engineering and Methodology (TOSEM), Vol. 14, No. 1, 2005, pp. 85-117. doi:10.1145/1044834.1044837
[41] K. E. Wiegers, “Software Requirements,” 2nd Edition, Microsoft Press, Redmond, 2003.
[42] W. S. Humphrey, “CMMI: History and Direction,” In: M. B. Chrissis, et al., Eds., CMMI: Guidelines for Process Integration and Product Improvement, 2nd Edition, Upper Saddle River, Addison-Wesley, Boston, 2007, pp. 5-8.
[43] J. W. Moore, “The Role of Process Standards in Process Definition,” In: M. B. Chrisses, et al., Eds., CMMI: Guidelines for Process Integration and Product Improvement, Upper Saddle River, Addison-Wesley, Boston, 2007, pp. 93-97.
[44] D. Leffingwell and D. Widrig, “Managing Software Requirements: A Use Case Approach,” 2nd Edition, Addison-Wesley Professional, Boston, 2003.
[45] SEI, “Process Maturity Profile, September 2011,” 7 October 2011.
[46] N. Khurshid, P. L. Bannerman and M. Staples, “Overcoming the First Hurdle: Why Organizations Do not Adopt CMMI,” Proceedings of the ICSP 2009-International Conference on Software Process (co-located with ICSE 2009), Vancouver, 16-17 May 2009, pp. 38-49.
[47] M. Staples, et al., “An Exploratory Study of Why Organizations do not Adopt CMMI,” The Journal of System and Software, Vol. 80, No. 6, 2007, pp. 883-895. doi:10.1016/j.jss.2006.09.008
[48] SEI, “CMMI? for Development, Version 1.3,” Software Engineering Institute, Pittsburgh, Technical Report, 2010.
[49] M. C. Paulk, C. Weber, B. Curtis and M. B. Chrisses, the Capability Maturity Model: Guidelines for Improving the Software Process. Addison-Wesley, Reading, 1995.
[50] M. Philips, “CMMI: From the Past and Into the Future,” In: M. B. Chrissis, et al., Eds., CMMI: Guidelines for Process Integration and Product Improvement, 2nd Edition, Upper Saddle River, Addison-Wesley, Boston, 2007, pp. 11-15.
[51] S. P. Sun, “MSC Malaysia APEC Workshop on Software Standards for SMEs and VSEs—A New Global Standard for Today’s International Economy,” 2010.
[52] K. Weber, et al., “Brazilian Software Process Reference Model and Assessment Method,” Computer and Information Sciences-ISCIS 2005, vol. 3733, 2005, pp. 402-411. doi:10.1007/11569596 43
[53] B. Solemon, “Requirements Engineering Process Assessment and Improvement Approach for Malaysian Software Industry,” PhD Thesis, Department of Computer Science and Information System, Universiti Teknologi Malaysia, Skudai, Johor, 2012.
[54] IIBA, “A Guide to the Business Analysis Body of Knowledge (BABOK Guide) Version 2.0,” International Institute of Business Analysis, Ontario, 2009.
[55] IREB, “Syllabus IREB Certified Professional for Requirements Engineering – Foundation Level- Version 2.0. English,” 2010.
[56] IEEE, “IEEE Guide for Software Engineering Body of Knowledge (SWEBOK) version 2004,” Institute of Electrical and Electronics Engineers, Inc., New York, 2004.
[57] S. Beecham, T. Hall, and A. Rainer, “Defining a Requirements Process Improvement Model,” University of Hertfordshire, Hatfield, Technical Report No. 379, 2003.
[58] SEI, “CMMI Models,” 2009.
[59] L. K. Meisenbacher, “The Challenges of Tool Integration for Requirements Engineering,” Proceedings of the Situational Requirements Engineering Processes (SREP’05) In conjunction with 13th IEEE International Requirements Engineering Conference, Paris, 29-30 August 2005, pp. 188-195.
[60] I. Aaen, A. Siltanen, C. Sorensen and V. P. Tahvanainen, “A Tale of Two Countries: CASE Experiences and Expectations,” In: K. E. Kendall, et al., Eds., The Impact of Computer Supported Technologies on Information Systems Development, IFIP Transactions A-8, North-Holland Publishing Co., Amsterdam, 1992, pp. 61-93.
[61] R. J. Kusters and G. M. Wijers, “On the Practical Use of CASE-tools: Results of a Survey,” Proceedings of the 6th International Workshop on CASE, Singapore, 19-23 July 1993, pp. 2-10.
[62] A. Kannenberg and D. H. Saiedian, “Why Software Requirements Traceability Remains a Challenge,” CrossTalk: The Journal of Defense Software Engineering, 2009, pp. 14-19.
[63] I. Sommerville, “Software Engineering,” 8th Edition, Addison-Wesley, Boston, 2007.
[64] S. Robertson and J. Robertson, “Mastering the Requirements Process,” Addison-Wesley, Harlow, 1999.
[65] PMI, “A Guide to the Project Management Body of Knowledge (PMBOK Guide),” PMI Project Management Institute, Newtown Square, 2004.
[66] K. Schwalbe, “Information Technology Project Management,” 2nd Edition, Course Technology, Thomson Learning, Massachusetts, 2002.
[67] B. Hughes and M. Cotterell, “Software Project Management,” 3rd Edition, McGraw-Hill Companies, London, 2002.
[68] D. L. Olson, “Introduction to Information System Project Management,” McGraw-Hill, Boston, 2001.
[69] R. K. Wysocki, J. R. Beck and D. B. Crane, “Effective Project Management,” 2nd Edition, Wiley Computer Publishing, New York, 2000.
[70] R. Conradi and T. Dyba, “An Empirical Study on the Utility of Formal Routines to Transfer Knowledge and Experience,” ACM SIGSOFT Software Engineering Notes, Vol. 26, No. 5, 2001, pp. 268-276.
[71] J. A. Calvo-Manzano Villalon, et al., “Experiences in the application of software process improvement in SMES,” Software Quality Journal, Vol. 10, No. 3, 2002, pp. 261-273.
[72] P. Saliou and V. Ribaud, “ISO-Standardized Requirements Activities for Very Small Entities,” Proceedings of the 16th International Working Conference on Requirements Engineering: Foundation for Software Quality, Essen, 30 June-2 July 2010, pp. 145-157.
[73] V. Ribaud, P. Saliou and C. Y. Laporte, “Towards Experience Management for Very Small Entities,” International Journal on Advances in Software, Vol. 4, No. 1-2, 2011, pp. 218-230.

comments powered by Disqus

Copyright © 2018 by authors and Scientific Research Publishing Inc.

Creative Commons License

This work and the related PDF file are licensed under a Creative Commons Attribution 4.0 International License.