Defining a Requirements Process Improvement Model

Both software organisations and the academic community are aware that the requirements phase of software development is in need of further support. We address this problem by creating a specialised Requirements Capability Maturity Model (R-CMM1). The model focuses on the requirements engineering process as defined within the established Software Engineering Institute’s (SEI’s) software process improvement framework. Our empirical work with software practitioners is a primary motivation for creating this requirements engineering process improvement model. Although all organisations in our study were involved in software process improvement (SPI), they all showed a lack of control over many requirement engineering activities.This paper describes how the requirements engineering (RE) process is decomposed and prioritised in accordance with maturity goals set by the SEI’s Software Capability Maturity Model (SW CMM). Our R-CMM builds on the SEI’s framework by identifying and defining recommended RE sub-processes that meet maturity goals. This new focus will help practitioners to define their RE process with a view to setting realistic goals for improvement.

[1]  David Cottengim Prerequisites for Success : Why Process Improvement Programs Fail , 2002 .

[2]  Franz Lehner,et al.  Requirements Engineering as a Success Factor in Software Projects , 2001, IEEE Softw..

[3]  Richard H. Thayer,et al.  Software Engineering Project Management , 2000 .

[4]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[5]  Arne Sølvberg,et al.  Understanding quality in conceptual modeling , 1994, IEEE Software.

[6]  Gerald M. Weinberg,et al.  Psychology of computer programming , 1971 .

[7]  Suzanne Robertson,et al.  Mastering the Requirements Process , 1999 .

[8]  Thomas Gilb Level 6: Why We Can't Get There from Here , 1996, IEEE Softw..

[9]  Charles Richter,et al.  A review of the state of the practice in requirements modeling , 1993, [1993] Proceedings of the IEEE International Symposium on Requirements Engineering.

[10]  Shari Lawrence Pfleeger,et al.  Maturity, models, and goals: How to build a metrics plan , 1995, J. Syst. Softw..

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

[12]  Ian Sommerville,et al.  Software Engineering (7th Edition) , 2004 .

[13]  Stan Rifkin Why Software Process Innovations Are Not Adopted , 2001, IEEE Softw..

[14]  Kerinia Cusick,et al.  A Description of the Systems Engineering Capability Maturity Model Appraisal Method, Version 1.0 , 1995 .

[15]  Marko Jäntti,et al.  Improving the Software Problem Management Process: A Case Study , 2006, EuroSPI.

[16]  David Zubrow,et al.  Moving On Up: Data and Experience Doing CMM-Based Process Improvement , 1995 .

[17]  Watts S. Humphrey,et al.  Introduction to the Personal Software Process , 1996 .

[18]  Bill Curtis,et al.  A field study of the software design process for large systems , 1988, CACM.

[19]  Pankaj Jalote,et al.  An integrated approach to software engineering, Second Edition , 1997 .

[20]  Pete Sawyer,et al.  Requirements Engineering: A Good Practice Guide , 1997 .

[21]  Robin W. Whitty,et al.  Software quality assurance and measurement : a worldwide perspective , 1995 .

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

[23]  Taratip Suwannasart,et al.  Developing a Testing Maturity Model, Part II , 1996 .

[24]  Michael A. Jackson,et al.  Software requirements and specifications - a lexicon of practice, principles and prejudices , 1995 .

[25]  Nandish V. Patel,et al.  The Spiral of Change Model for Coping with Changing and Ongoing Requirements , 1999, Requirements Engineering.

[26]  Ian Sommerville,et al.  Requirements process improvement through the phased introduction of good practice , 1997, Softw. Process. Improv. Pract..

[27]  Reidar Conradi,et al.  Improving Software Process Improvement , 2002, IEEE Softw..

[28]  Søren Lauesen,et al.  Preventing Requirement Defects: An Experiment in Process Improvement , 2001, Requirements Engineering.

[29]  Dewayne E. Perry,et al.  People, organizations, and process improvement , 1994, IEEE Software.

[30]  Pericles Loucopoulos,et al.  System Requirements Engineering , 1995, System Requirements Engineering.

[31]  Neil A. M. Maiden,et al.  Where Do Requirements Come From? , 2001, IEEE Softw..

[32]  Carlo Ghezzi,et al.  Software processes: a retrospective and a path to the future , 1998, Softw. Process. Improv. Pract..

[33]  Peter Axel Nielsen,et al.  Competing values in software process improvement: an assumption analysis of CMM from an organizational culture perspective , 2003, IEEE Trans. Engineering Management.

[34]  Tracy Hall,et al.  De-motivators for software process improvement: an analysis of practitioners' views , 2003, J. Syst. Softw..

[35]  William E. Hefley,et al.  People Capability Maturity Model. SM. , 1995 .

[36]  Watts S. Humphrey,et al.  Managing the software process , 1989, The SEI series in software engineering.

[37]  Karl Wiegers Molding the CMM to your organization , 1998 .

[38]  Taratip Suwannasart,et al.  Developing a Testing Maturity Model : Part I , 1996 .

[39]  W. Deming Quality, productivity, and competitive position , 1982 .

[40]  Barbara Paech,et al.  Systematic requirements recycling through abstraction and traceability , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[41]  Watts S. Humphrey,et al.  Introduction to the Team Software Process , 1999 .

[42]  Tony Moynihan Coping with 'requirements-uncertainty': the theories-of-action of experienced IS/software project managers , 2000, J. Syst. Softw..

[43]  Pankaj Jalote,et al.  An Integrated Approach to Software Engineering , 1997, Undergraduate Texts in Computer Science.

[44]  Austen Rainer,et al.  Key success factors for implementing software process improvement: a maturity-based analysis , 2002, J. Syst. Softw..

[45]  Khaled El Emam,et al.  User participation in the requirements engineering process: An empirical study , 1996, Requirements Engineering.

[46]  Corporate Ieee,et al.  Software engineering standards , 1987 .

[47]  Colin Potts,et al.  Requirements models in context , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[48]  Witold Pedrycz,et al.  Software Engineering: An Engineering Approach , 1999 .

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

[50]  Bill Curtis,et al.  The global pursuit of process maturity , 2000 .

[51]  Gerald M. Weinberg,et al.  Exploring Requirements: Quality Before Design , 1989 .

[52]  P. Grant Rule Using measures to understand requirements , 2001 .

[53]  Mark C. Paulk,et al.  The Capability Maturity Model , 1991 .

[54]  Egon Berghout,et al.  The Goal/Question/Metric method: a practical guide for quality improvement of software development , 1999 .

[55]  Ian Sommerville,et al.  Requirements process improvement through the phased introduction of good practice , 1997 .

[56]  Alan M. Davis,et al.  Tracing: A Simple Necessity Neglected , 1995, IEEE Softw..

[57]  J. G. Brodman,et al.  What small businesses and small organizations say about the CMM , 1994, Proceedings of 16th International Conference on Software Engineering.

[58]  Mohamed Fayad,et al.  Software development process: a necessary evil , 1997, CACM.

[59]  J. Creswell Qualitative inquiry and research design: choosing among five traditions. , 1998 .

[60]  Victor R. Basili,et al.  The TAME Project: Towards Improvement-Oriented Software Environments , 1988, IEEE Trans. Software Eng..

[61]  Edward Yourdon,et al.  Techniques of Program Structure and Design , 1976 .

[62]  Suzanne Garcia A Description of the Systems Engineering Capability Maturity Model Appraisal Method, Version 1.0. , 1995 .

[63]  Karl E. Wiegers Read My Lips: No New Models! , 1998, IEEE Softw..

[64]  Kurt R. Linberg Software developer perceptions about software project failure: a case study , 1999, J. Syst. Softw..

[65]  Austen Rainer,et al.  Using an expert panel to validate a requirements software process improvement model , 2005 .

[66]  Khaled El Emam,et al.  A field study of requirements engineering practices in information systems development , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[67]  Alan M. Davis A taxonomy for the early stages of the software development life cycle , 1988, J. Syst. Softw..

[68]  Mark C. Paulk,et al.  The November 1999 High Maturity Workshop , 2000 .

[69]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .

[70]  H. van Vliet,et al.  The IT Service Capability Maturity Model. , 1999 .

[71]  James Bach What Software Reality Is Really About , 1999, Computer.

[72]  Watts S. Humphrey,et al.  Three Process Perspectives: Organizations, Teams, and People , 2002, Ann. Softw. Eng..

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

[74]  Alan M. Christie,et al.  Simulation in support of CMM-based process improvement , 1999, J. Syst. Softw..

[75]  John C. Anderson,et al.  Maturity and its impact on new product development project performance , 2001 .

[76]  Nazim H. Madhavji,et al.  The process cycle [software engineering] , 1991, Softw. Eng. J..

[77]  John Mylopoulos,et al.  Modelling Organizational Issues for Enterprise Integration , 1997, ICEIMT.

[78]  Shari Lawrence Pfleeger,et al.  Measurement based process improvement , 1994, IEEE Software.

[79]  Ian Sommerville Software engineering, 5th Edition , 1996 .

[80]  Dag I. K. Sjøberg,et al.  Towards a framework for empirical assessment of changeability decay , 2000, J. Syst. Softw..

[81]  Mark Neal,et al.  Why and how of requirements tracing , 1994, IEEE Software.

[82]  Richard H. Thayer,et al.  System and Software Requirements Engineering , 1994 .

[83]  Alan M. Davis,et al.  Identifying and measuring quality in a software requirements specification , 1993, [1993] Proceedings First International Software Metrics Symposium.

[84]  JoAnn T. Hackos,et al.  From Theory to Practice: Using the Information Process-Maturity Model as a Tool for Strategic Planning. , 1997 .

[85]  Daniel Gross,et al.  From Non-Functional Requirements to Design through Patterns , 2001, Requirements Engineering.

[86]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

[87]  RainerAusten,et al.  Defining a Requirements Process Improvement Model , 2005 .

[88]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach (McGraw-Hill Series in Computer Science) , 2004 .

[89]  Mark C. Paulk,et al.  The Capability Maturity Model: Guidelines for Improving the Software Process , 1994 .

[90]  Albert David,et al.  Models implementation: A state of the art , 2001, Eur. J. Oper. Res..

[91]  Barry McCollum,et al.  Management of process improvement by prescription , 2001, J. Syst. Softw..

[92]  Tracy Hall,et al.  Motivators of Software Process Improvement: an analysis of practitioners' views , 2002, Journal of Systems and Software.

[93]  Donald J Reifer The CMMI: it's formidable , 2000, J. Syst. Softw..

[94]  Judith G. Brodman,et al.  What small business and small organizations say about the CMM: experience report , 1994, ICSE '94.

[95]  Bob McFeeley,et al.  IDEAL: A User's Guide for Software Process Improvement. , 1996 .

[96]  Austen Rainer,et al.  Building a requirements process improvement model , 2003 .