Introducing Requirements Change Management Process into ISO/IEC 12207 SPICE 2018 Introducing Requirements Change Management Process into ISO/IEC 12207 Sajid Anwer Lian Wen (Larry) Terry Rout Zhe Wang School of ICT, Griffith University, Australia SPICE 2018

Outline Introduction Literature Review & Background Proposed Requirement Change Management Process Comparison with existing Configuration Management Process Conclusion & Future Work References SPICE 2018

Introduction 1/2 Requirements are attributes or capabilities that system must meet to satisfy the customer or stakeholder needs, organizational standards New requirements emerged or existing requirements change due to changes in Customer needs Market trends Business goals Change is inevitable, a continuous source of risk, and impacts the agreed baseline of requirements. Requirement change increases the project cost three times and project duration two times [1]. SPICE 2018

Introduction 2/2 It is often the case that more than 50% of a system’s requirements will be modified before it is put into service [2]. Change management is concerned with keeping track of these changes and ensuring that they are implemented in the most cost-effective way. Requirement change management process ensures that changes are made systematically similar information is collected for each proposed change overall analysis is made about the costs, benefits and timing the requirements document is updated. SPICE 2018

Literature Review & Background 1/2 A number of Requirement Change Management (RCM) models has been proposed, however no model covers all the critical factors related to RCM. ISO/IEC 12207: 2017 [3] and ISO/IEC 15288: 2015 [4] outline the configuration management process and discuss requirement change management as outcomes in the configuration management process. Configuration management’s goal is to set and maintain consistency among project products and product versioning. Requirement change management addresses the requested changes to individual products, e.g. project requirements, design, and scope etc. [5] Configuration management can be considered as a supporting process in software requirements change. SPICE 2018

Literature Review & Background 1/2 Configuration management and change management processes are defined in Information Technology Infrastructure Library (ITIL). However, ITIL mainly focuses on delivering information technology services to the companies instead of developing projects. The guidelines or processes written in natural languages are always context dependent and ambiguous. Composition tree, a semi-formal notation is used to; Model the proposed RCM process Compare proposed RCM process with existing configuration management process. SPICE 2018

Proposed Requirement Change Management Process 1/3 Purpose The purpose of RCMP is to manage and control requirement changes of system elements or items and make them available to concerned parties. Outcomes As a result of the successful implementation of the software requirement change management process: Items to be changed are identified and recorded. Change Impacts are analyzed. The cost and schedule of changing items are estimated. Changes to the items under requirement change are approved. Changes to the items under requirement change are implemented. Changes to the items under requirement change are verified and validated. Changed items deliverables are updated and communicated to concerned parties. SPICE 2018

Proposed Requirement Change Management Process 2/3 SPICE 2018

Proposed Requirement Change Management Process 3/3 SPICE 2018

Comparison between Proposed RCMP and Configuration Management Process (1/4) Composition tree is used to compare the proposed RCMP with existing configuration management process. In Comparison Composition Tree (CCT); The root is a combination of root names of both trees Nodes that are part of both the old and the new trees will be represented with single line boundary Dotted boundary lines are used to represent the nodes that are only part of the old tree Bold boundary lines are used to represent the information that only exists in the new tree SPICE 2018

Comparison between Proposed RCMP and Configuration Management Process (2/4) SPICE 2018

Comparison between Proposed RCMP and Configuration Management Process (3/4) There is one component called Configuration defined in the CMP ISO 12207: 2017, but no such component exists in the RCMP. There are no attributes defined for item or work products in the CMP ISO/IEC 12207:2017, whereas a number of attributes for item or work products are identified in the RCMP. There is a component called Concerned Parties (CP) listed in the RCMP but not in the CMP ISO/IEC 12207:2017. Deliveries and Releases (DLR) are defined as a component in the CMP ISO/IEC 12207:2017, whereas no such component existing in the RCMP. One state of component item or work product called identified is a part of both trees, while managed state exists only in the CMP ISO/IEC 12207:2017, and recorded sate only exists in RCMP. No attributes defined for component change which is a sub component of item in CMP ISO/IEC 12207:2017, while we have one attribute for this component in the RCMP. SPICE 2018

Comparison between Proposed RCMP and Configuration Management Process (4/4) For the sub component “change”, only one state called controlled is presented in the CMP ISO/IEC 12207:2017, contrary to the RCMP we have other four states, one sub component with an associated state called updated. Lastly, one relationship of the sub component Deliverables is also defined in RCMP, but no such component defined in the CMP ISO/IEC 12207:2017. SPICE 2018

Conclusion & Future Work Requirement change management process has been proposed. Seven stage requirement change management model has been designed to elaborate the proposed process. Composition tree is used to model the proposed RCMP. Comparison Composition Tree (CCT) is used to compare the proposed RCMP with existing configuration change management process. The CCT reveals that the RCMP addresses several RCM problems in more detail than the existing CMP. In future, a questionnaire will be conducted with industry professionals to empirically validate the proposed model. The applicability of the proposed model in global software development paradigm is worthy of future investigation. SPICE 2018

References [1] Standish-Group: Chaos - the state of the software industry (2017). [2] G. Kotonya and I. Sommerville, Requirements Engineering - Processes and Techniques, John Wiley & Sons, New York, 1998. [3] "ISO/IEC 12207: 2017, - Information Technology - System engineering- Software life cycle process." [4] "ISO/IEC 15288: 2015, - Information Technology - System engineering- System [5] P. M. Institute, "Practice Standard for Project Configuration Management," 2007: Project Management Institute. SPICE 2018