Requirement Change Management Techniques in Software Systems

Mapping Intimacies ◽

10.20944/preprints201912.0145.v1 ◽

2019 ◽

Author(s):

Mehreen Sirshar ◽

Ghanwa Ejaz ◽

Maria Mumtaz

Keyword(s):

Software Development ◽

Change Management ◽

Software Systems ◽

Project Failure ◽

Critical Phase ◽

Management Techniques ◽

Requirement Change ◽

Level Of Understanding ◽

Total Project

During software development requirement gathering is an important phase. Requirements are the basis of software development. The success or failure of any software depends upon level of understanding developed in requirements. During software development requirements keeps on changing due to different reasons. Hence requirements are such a critical phase that leads to the total project failure. So, to understand the impacts and to identify the conflicts with existing requirements, it is important to manage and analyze the requirements well. Requirement change management is the interest of this paper. Different requirement change management techniques has been discussed in this paper and analyzed them well and finally conclude the results accordingly.

Download Full-text

Toward an Agile Approach to Managing the Effect of Requirements on Software Architecture during Global Software Development

Scientific Programming ◽

10.1155/2016/8198039 ◽

2016 ◽

Vol 2016 ◽

pp. 1-16 ◽

Cited By ~ 1

Author(s):

Abdulaziz Alsahli ◽

Hameed Khan ◽

Sultan Alyahya

Keyword(s):

Grounded Theory ◽

Software Development ◽

Change Management ◽

Impact Analysis ◽

Global Software Development ◽

Case Based Reasoning ◽

Domain Experts ◽

Agile Practices ◽

Critical Activity ◽

Requirement Change

Requirement change management (RCM) is a critical activity during software development because poor RCM results in occurrence of defects, thereby resulting in software failure. To achieve RCM, efficient impact analysis is mandatory. A common repository is a good approach to maintain changed requirements, reusing and reducing effort. Thus, a better approach is needed to tailor knowledge for better change management of requirements and architecture during global software development (GSD).The objective of this research is to introduce an innovative approach for handling requirements and architecture changes simultaneously during global software development. The approach makes use of Case-Based Reasoning (CBR) and agile practices. Agile practices make our approach iterative, whereas CBR stores requirements and makes them reusable. Twin Peaks is our base model, meaning that requirements and architecture are handled simultaneously. For this research, grounded theory has been applied; similarly, interviews from domain experts were conducted. Interview and literature transcripts formed the basis of data collection in grounded theory. Physical saturation of theory has been achieved through a published case study and developed tool. Expert reviews and statistical analysis have been used for evaluation. The proposed approach resulted in effective change management of requirements and architecture simultaneously during global software development.

Download Full-text