Article Review on Software Change Management

Question

Task: Select a journal article on software change management and prepare a report within 2000 words.

Answer

Introduction
Selected Article Details
[1] L. Ping and L. JianYang, “A Change-Oriented Conceptual Framework Of Software Configuration Management,” 2007 International Conference on Service Systems and Service Management, Jun. 2007.

Purpose & Outline
The purpose of the report is to understand the software change management and the ways in which changes can be better managed in a software project. The conceptual framework is designed using the software configuration management and software change management. The outline includes the intent, content, methodology, and is followed by the findings of the selected research article [1]. The elaboration on the issues and discussion on the results and conclusion is done next.

Intent & Content
While initiating software change management, the cost of software maintenance is high. There is significant cost that is involved with the software codes and packages and it is the primary concern for the software project teams. These costs are high because there are too many changes that are involved in the software packages once the updates are involved. The authors intend to determine the ways in which the change-oriented measures are adopted in the software projects to bring down the overall costs of the project.

Software configuration management, SCM is one of the significant aspects of the overall software development lifecycle. The introduction section elaborates on the background of SCM with the description of change tracking procedures [2]. The conceptual framework is discussed in the next section which may be used as a solution. The software lifecycle is explained using the framework that has been selected. The discussion on the findings is done and it is then followed by a brief conclusion.

Methods & Findings
The authors have followed the qualitative measures to conduct the research work. The research method provides the ability to determine the aspects of software change management and configuration management that shall be followed and the details of the framework applicable in the software projects.

The findings are not discussed separately; rather, all the sections in the article provide the significant details on the conceptual framework and its relation with the SCM. There are several changes that are identified in the software projects. These changes are identified in the maintenance phase when the software codes need to be updated. The changes that are recognized and implemented lead to the modifications essential to be done in the associated areas. The inability to make changes in all the related areas can lead to the gaps. There are several artifacts that are involved in the lifecycle of a software project. The changes need to be tracked at all times so that the issues of mismanagement can be identified and handled. The changes that are confirmed and implemented shall be included in the artifact. This shall then be moved to the workspace and the process shall continue in this way [3]. The use of stages and the artifacts provide the ability to control and keep a track of the changes. Whenever a software change management is implemented in the software project, it is required that the integrity of the lifecycle does not get disturbed. There are several stages that are involved in every process. These changes obtained by performing software change management shall occur at all the stages one after the other. The changes made in one stage shall reflect on the stage that follows and the process shall go on. There are changes that can also be local and may not have any impact outside the stage boundaries. These internal changes can be executed internally as these do not impact the final outcome. The changes that can impact the final outcomes must cover all the stages.

The conceptual framework that is used in the SCM shall be flexible. It shall provide the ability to modify the processes as per the requirement and the integrity must not be disturbed at any stage. The change-oriented conceptual framework that is determined can be easily synced with the phases of the software development lifecycle. The need to maintain the integrity of the processes and the changes is mandatory. This may lead to some additional complexities in a few scenarios. This also leads to ensure that there is complete transparency maintained and no confusions exist.

What are the problems & issues associated with the existing measures of software change management?
The expense of software maintenance is high. There is huge cost that is associated with the software codes and bundles and it is the essential worry for the software project groups. These expenses are high in light of the fact that there are such a large number of changes that are engaged with the software bundles once the updates are included. There are certain problems that are associated with the existing measures of software change management in the software projects. There are a few changes that are distinguished in the software projects. These changes are distinguished in the support stage when the software codes should be refreshed. The changes that are perceived and executed lead to the adjustments basic to be done in the related regions [4]. There are a few antiques that are associated with the lifecycle of a software project. The changes should be tracked consistently with the goal that the issues of bungle can be distinguished and dealt with. The changes that are affirmed and actualized will be remembered for the relic. This will at that point be moved to the workspace and the procedure will proceed along these lines. The utilization of stages and the antiques give the capacity to control and monitor the changes. At whatever point a change is executed in the software project, it is necessitated that the integrity of the lifecycle doesn't get upset. There are a few stages that are engaged with each procedure. These changes will happen at all the stages in a steady progression. The changes made in one stage will ponder the stage that follows and the procedure will go on. There are changes that can likewise be nearby and might not have any impact outside the stage boundaries. These inward changes can be executed internally as these don't impact the final result. The changes that can impact the final results must cover all the stages. The conceptual framework that is utilized in the SCM will be adaptable. It will give the capacity to change the procedures according to the necessity and the integrity must not be upset at any stage. The change-oriented conceptual framework that is resolved can be handily synced with the periods of the software improvement lifecycle. The need to keep up the integrity of the procedures and the changes is required. This may prompt some extra complexities in a couple of situations [5]. This additionally prompts guarantee that there is finished transparency kept up and no disarrays exist.

Results & Discussion
There are a numerous changes that are recognized in the software projects. These changes are recognized in the help stage when the software codes ought to be revived. The changes that are seen and executed lead to the modifications fundamental to be done in the related locales. the insufficient administration of the changes ca lead to the huge gaps. There are a couple of collectibles that are related with the lifecycle of a software project. The changes ought to be tracked reliably with the objective that the issues of screw up can be recognized and managed. The changes that are asserted and completed will be associated with the relic. This will by then be moved to the workspace and the system will continue thusly. The use of stages and the collectibles enable to control and screen the changes. At whatever point a change is executed in the software project, it is required that the integrity of the lifecycle doesn't get agitated. There are a couple of stages that are locked in with every strategy. These changes resulted by software change management process will occur at all the stages in a consistent movement. The changes made in one stage will consider the stage that follows and the method will go on [6]. There are changes that can moreover be close by and probably won't have any impact outside the stage boundaries. These internal changes can be executed internally as these don't impact the final outcome. The changes that can impact the final outcomes must cover all the stages.

The conceptual framework that is used in the SCM will be versatile. It will enable to change the strategies as indicated by the need and the integrity must not be agitated with any stage. The change-oriented conceptual framework that is settled can be conveniently synced with the times of the software improvement lifecycle. The need to keep up the integrity of the methodology and the changes is required. This may incite some additional complexities in a few circumstances. This also prompts ensure that there is done transparency kept up and no confusions exist.

Conclusion
The qualitative research carried out by the authors review the literature on software change management process. The authors highlighted three core areas including: Artefacts, Process and Change tracking. The conceptual framework that has been determined is change-oriented and it can sync well with the lifecycle of the software projects. The use of the conceptual framework used in SCM will provide the ability to effective carry out the software configuration management in the software projects. Authors have also shown that the framework proposed is flexible and can suit a variety of different software development projects.

References
[1] L. Ping and L. JianYang, “A Change-Oriented Conceptual Framework Of Software Configuration Management,” 2007 International Conference on Service Systems and Service Management, Jun. 2007.

[2] S. Jayatilleke and R. Lai, “A systematic review of requirements change management,” Information and Software Technology, vol. 93, pp. 163–185, Jan. 2018.

[3] B. Masekela and R. Nienaber, “A Change Management Framework to Support Software Project Management,” International Journal of Knowledge Society Research, vol. 1, no. 4, pp. 54–68, Oct. 2015.

[4] A. Dhamija and S. Sikka, “Software Change Management: a Quantified Perspective,” International Journal of Engineering & Technology, vol. 7, no. 3.12, p. 963, Jul. 2018.

[5] P. Efe and O. Demirors, “A change management model and its application in software development projects,” Computer Standards & Interfaces, vol. 66, p. 103353, Oct. 2019.

[6] S. Siddique and A. Siddique, “Software Change Management: A Note on Significance, Tools and Support,” International Journal of Computer Applications, vol. 177, no. 34, pp. 59–62, Jan. 2020.