Requirements engineering process improvement and related models

Requirements Engineering (RE) is a key discipline in software development, and several standards and models are available to help assess and improve RE processes. However, different standards and models can also help achieve different improvement goals. Thus, organizations are challenged to select these standards and models to best suit their specific context and available resources. This chapter presents a review of selected RE-specific and generic process improvement models that are available in the public domain. The review aims to provide preliminary information that might be needed by organizations in selecting these models. The chapter begins with analyses of how RE maturity is addressed in the Capability Maturity Model Integration (CMMI) for Development. Then, it describes the principal characteristics of, and the assessment and improvement framework applied in four RE-specific process assessment and improvement models: the Requirements Engineering Good Practice Guide (REGPG), the Requirements Engineering Process Maturity(REPM), the Requirements Capability Maturity Model (R-CMM), and the Market-Driven Requirements Engineering Process Model (MDREPM). This chapter also examines the utility and lesson learned of these models.

[1]  Austen Rainer,et al.  Using an expert panel to validate a requirements process improvement model , 2005, J. Syst. Softw..

[2]  Ita Richardson,et al.  Research into long-term improvements in small- to medium-sized organisations using SPICE as a framework for standards , 2007 .

[3]  Abdul Azim Abdul Ghani,et al.  Requirements Engineering Problems and Practices in Software Companies: An Industrial Survey , 2009, FGIT-ASEA.

[4]  Ian Sommerville,et al.  An empirical study of industrial requirements engineering process assessment and improvement , 2005, TSEM.

[5]  Mark Staples,et al.  Overcoming the First Hurdle: Why Organizations Do Not Adopt CMMI , 2009, ICSP.

[6]  Douglas C. Schmidt,et al.  Evolution in Model-Driven Software Product-Line Architectures , 2009 .

[7]  Jeremy Rose,et al.  Prescription, description, reflection: the shape of the software process improvement field , 2004, Int. J. Inf. Manag..

[8]  Austen Rainer,et al.  Defining a Requirements Process Improvement Model , 2005, Software Quality Journal.

[9]  Marjo Kauppinen,et al.  Lessons Learned from Applying the Requirements Engineering Good Practice Guide for Process Improvement , 2002, ECSQ.

[10]  Michael Daskalantonakis,et al.  Achieving higher SEI levels , 1994, IEEE Software.

[11]  Tony Gorschek,et al.  A Method for Assessing Requirements Engineering Process Maturity in Software Projects , 2002 .

[12]  M. Niazi,et al.  Role of requirements engineering in software development process: an empirical study , 2003, 7th International Multi Topic Conference, 2003. INMIC 2003..

[13]  Austen Rainer,et al.  Requirements problems in twelve software companies: an empirical analysis , 2002, IEE Proc. Softw..

[14]  Pete Sawyer,et al.  Maturing Requirements Engineering Process Maturity Models , 2004 .

[15]  Andreas Pettersson,et al.  Market-Driven Requirements Engineering Process Model – MDREPM , 2007 .

[16]  D. Ross Jeffery,et al.  An exploratory study of why organizations do not adopt CMMI , 2007, J. Syst. Softw..

[17]  Nannette P. Napier,et al.  Combining Perceptions and Prescriptions in Requirements Engineering Process Assessment: An Industrial Case Study , 2009, IEEE Transactions on Software Engineering.

[18]  Austen Rainer,et al.  Software Process Improvement Problems in Twelve Software Companies: An Empirical Analysis , 2003, Empirical Software Engineering.