A process model for Requirements Change Management in collocated software development
- 1 October 2012
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 1-6
Abstract
Requirements Change Management (RCM) could occur at any phase of the software development life cycle. Therefore, RCM is considered to be a difficult task in software development organizations. The purpose of this study is to propose a model for RCM that will be implemented in collocated software development organizations. The model is based on the data collected from different RCM reports, models, research papers and different case studies related to RCM. The model has seven core stages, i.e., change request, validate, reject, batch, implement, verify and update. Propose model will eliminate the limitations of the available RCM models.Keywords
This publication has 10 references indexed in Scilit:
- A methodology to manage the changing requirements of a software project2010
- An investigation of changing requirements with respect to development phases of a software project2010
- Systematic literature reviews in software engineering – A tertiary studyInformation and Software Technology, 2010
- Process-related software requirements management2010
- A Software Requirements Change Source Taxonomy2009
- The Requirements Change Analysis for Different Level Users2008
- Requirement Change Management Process Models: Activities, Artifacts and Roles2006
- Making Decision in Requirement Change Management2006
- Requirements Engineering for Sociotechnical Systems2005
- An examination of the effects of requirements changes on software maintenance releasesJournal of Software Maintenance: Research and Practice, 1999