Requirement Change Management Process Models: Activities, Artifacts and Roles

Modern software-intensive systems are developed in a world where only constant thing is change. This results in continuously changing requirements. Failure to manage these changing requirements properly may result in failure of system. To manage these requirements, many requirements change management (RCM) process model has been proposed in the literature. Process models facilitate human understating and communication, support process improvement and process management. Coverage of process elements like activities, artifacts and roles has an affect on process model and its usage. This paper reports the current requirements change management process models in the literature on the basis of activities, artifacts and roles. Our survey highlights that there is lack of consensus on RCM process and it has not been described in sufficient detail for use of requirements engineers in the real world.

[1]  Bill Curtis,et al.  Process modeling , 1992, CACM.

[2]  Gerald Kotonya,et al.  An Integrated, Probabilistic Framework for Requirement Change Impact Analysis , 1999, Australas. J. Inf. Syst..

[3]  Lloyd G. Williams.  A behavioral approach to software process modelling , 1988, ISPW '88.

[4]  Luigi Lavazza,et al.  Enhancing requirements and change management through process modelling and measurement , 2000, Proceedings Fourth International Conference on Requirements Engineering. ICRE 2000. (Cat. No.98TB100219).

[5]  M. R. Strens,et al.  Change analysis: a step towards meeting the challenge of changing requirements , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.

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

[8]  Gonzalo Cuevas Agustín,et al.  Assessment of the requirements management process using a two-stage questionnaire , 2004, Fourth International Conference onQuality Software, 2004. QSIC 2004. Proceedings..

[9]  D.-R. Harjani,et al.  A process model for the maintenance of large space systems software , 1992, Proceedings Conference on Software Maintenance 1992.

[10]  Mamoru Maekawa,et al.  Need-based requirements change management , 2001, Proceedings. Eighth Annual IEEE International Conference and Workshop On the Engineering of Computer-Based Systems-ECBS 2001.

[11]  Deborah Richards,et al.  Towards improving requirements engineering processes: prioritizing requirements engineering process problems for elimination , 2005 .

[12]  Gerald Kotonya,et al.  An Integrated Framework for Requirement Change Impact Analysis , 1999 .

[13]  Shawn A. Bohner,et al.  Impact analysis in the software change process: a year 2000 perspective , 1996, 1996 Proceedings of International Conference on Software Maintenance.

[14]  Watts S. Humphrey,et al.  Software process development and enactment: concepts and definitions , 1993, [1993] Proceedings of the Second International Conference on the Software Process-Continuous Software Process Improvement.

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

[16]  Neil C. Olsen.  The software rush hour (software engineering) , 1993, IEEE Software.

[17]  Xavier Ferré,et al.  Software Process Modelling , 2001, ISAS-SCI.

[18]  Angela Greiling Keane,et al.  NO SILVER BULLET , 2003 .

[19]  Minna Mäkäräinen,et al.  Software change management process in the development of embedded software , 2000 .

[20]  Andrew Taylor,et al.  IT projects: sink or swim , 2000 .

[21]  Khaled El Emam,et al.  Causal analysis of the requirements change process for a large system , 1997, 1997 Proceedings International Conference on Software Maintenance.

[22]  Effy Oz,et al.  When professional standards are lax: the CONFIRM failure and its lessons , 1994, CACM.

[23]  Mark Dowson,et al.  Concepts For Process Definition And Support , 1990, 'Support for the Software Process'.,Proceedings of the 6th International Software Process Workshop.

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

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

[26]  Jacques Lonchamp,et al.  A structured conceptual and terminological framework for software process engineering , 1993, [1993] Proceedings of the Second International Conference on the Software Process-Continuous Software Process Improvement.

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

[28]  W. Lam,et al.  Requirements change: a dissection of management issues , 1999, Proceedings 25th EUROMICRO Conference. Informatics: Theory and Practice for the New Millennium.

[29]  Khaled El Emam,et al.  Measuring the success of requirements engineering processes , 1995, Proceedings of 1995 IEEE International Symposium on Requirements Engineering (RE'95).

[30]  William H. Ett,et al.  Lessons learned from a software process modeling system , 1992, CACM.

[31]  Naveed Ikram.  The management of risk in information systems development , 2000 .

[32]  Sara Jones,et al.  Change analysis and management: a process model and its application within a commercial setting , 1998, Proceedings. 1998 IEEE Workshop on Application-Specific Software Engineering and Technology. ASSET-98 (Cat. No.98EX183).