Assessing issues of change impact analysis process for a software projects (original) (raw)

Identifying challenges of change impact analysis for software projects

2012

Project changes are difficult since the impacts of the changes are not readily known in advance. Changing customer needs and technology are driving factors influencing project evolution. Consequently, there is a need to assess the impact of these changes on existing software systems. For safety-critical system, the changes can even introduce hazards to bug down the system, particularly for larger systems, it quickly become difficult to comprehend what impact of requirement change might have on the overall system or parts of the system. Impact analysis is identifying the potential impact of disruption caused by a change to one or more components in the requirement on other components. The significant behind impact analysis is to identify requirement elements that may be affected by the change. However, this paper deals with impact analysis approach during project changes and identifies issues of impact analysis and where change impact analysis applied during software development projects

A Change Impact Analysis Tool for Software Development Phase

Accepting too many software change requests could contribute to expense and delay in project delivery. On the other hand rejecting the changes may increase customer dissatisfaction. Software project management might use a reliable estimation on potential impacted artifacts to decide whether to accept or reject the changes. In software development phase, an assumption that all classes in the class artifact are completely developed is impractical compared to software maintenance phase. This is due to some classes in the class artifact are still under development or partially developed. This paper extends our previous works on developing an impact analysis approach for the software development phase in automating the approach which we call it CIAT (Change Impact Analysis Tool). The significant achievements of the tool are demonstrated through an extensive experimental validation using several case studies. The experimental analysis shows improvement in the accuracy over current impact analysis results.

The importance of decision strategy and role in a software change impact analysis performance

World Applied Sciences Journal

Software change impact analysis is defined as a process of identifying the potential impact of disruption caused by a change to one or more components in the data center on other components. Change impact analysis is defined as identifying the potential consequences of a change or estimating what needs to be modified to accomplish a change. The term "impact analysis" is used with many meanings, its used for characterizing and comparing diverse change impact analysis approaches, it corresponds to how an approach is used to accomplish change impact analysis and how an approach does change impact analysis internally and the effectiveness of the impact analysis approach. As the project management community recognizes the growing need to identify the consequences of changes. Some recent surveys reported that the project failure rate has increased over the last two decades. Because, the software projects capacities increase with the lack of appropriate approach of software change requirement management. However, this paper deals with investigating further change impact analysis issues at IT companies in Malaysia, by looking their Organizational decision level and how they applied it and profile them. Subsequently, it proposes the approapreate team for software change impact analysis performance.

A Conceptual Model of Impact Analysis for Requirements Change

Requirements change in software is inevitable due to the dynamic needs of business process and environment. This change needs to be managed accordingly by determining the influencing elements as well as assessing their impacts to the current environment through impact analysis. This critical task is accomplished by a dedicated team, namely Change Control Board (CCB). In essence, an impact analysis helps CCB to visualize the potential impacts of change towards organization before implementing them. This is vital because an improper analysis may not only affect project but also organization sustainability. Previous studies have identified some contributing elements for requirements change. However, they are isolated and disintegrated between technical and non-technical perspectives that cause impact analyses to be difficult. This paper therefore collated the necessary elements for requirements change impact analysis that encompasses both perspectives. The elements were identified through reviews and were analysed by using content analysis. The elements form a conceptual model for requirements change impact analysis. The model illustrates the relationships between elements, which is important to assess the impacts of requirements change. The model can be used by CCB as a guide to decide the way forward a particular requirements change request.

Preface to "Software Change Impact Analysis

Ieee Computer Society, 1996

What is Software Change Impact Analysis? Software change impact analysis, or impact analysis for short, estimates what will be affected in software and related documentation if a proposed software change is made. Impact-analysis information can be used for planning changes, making changes, accommodating certain types of software changes, and tracing through the effects of changes. Impact analysis provides visibility into the potential effects of changes before the changes are implemented. This can make it easier to perform changes more accurately. Why This Book? This book is a collection of tutorial papers, trade articles, and software-research literature that capture current impact-analysis techniques and technical results. Much has been written on impact analysis, but it is scattered across magazines and books and is time-consuming to collect, review, and evaluate. This book grew from our perception that, with the great interest in software change, people need a handy, one-volume source of useful information. We have collected scattered technical information on the science and art of determining what software parts affect one another. We have sifted through many papers, articles, and technical reports. We have distilled the themes, trends, and techniques of impact analysis so that our book can frame the field, focus attention, and temper expectations.

Software Change Management: a Quantified Perspective

International Journal of Engineering & Technology

A systematic Change Impact Analysis (CIA) is being used for better change management of software. Also, CIA process is evolved continuously to make it more effective. Software metrics play an important role to evaluate CIA process. Two types of metrics are used to evaluate CIA. First types of metrics are the standard metrics used to evaluate the performance of CIA techniques for example Precision, Recall, F-measure etc. These are most commonly used by researchers. Second types of metrics are those which are used to quantify the change impact which is based on the code/design features. This paper is aimed at identification of these second types of metrics available in literature.

The Influence of Change Management on the Effectiveness of the Software Development Process

1998

This paper presents the partial results of a field work, the intention of which was to measure change management in the effectiveness of the software development process in real-life projects. The methodology proposed by Perez and Rojas [Perez and Rojas, 1997] has been used in this task. A reference framework and the identification of change management measurement indicators, including their corresponding reactives, are the partial results of this field work. Introduction It is clear that all transformation processes are of vital importance for organizations to survive in today s competitive environment. A tangible element in this transformation process is the management of change. Change management is one of the factors affecting the effectiveness of the software development process. This dimension, the effectiveness of the process, is one of the most difficult to measure when considering its human and social characteristics. Therefore, it is useful to carry out field work that wou...

New change impact factor estimation in software development

Change in software is always an essential part of software development and maintenance. Estimating a proposed change’s effect on the later phases of the development helps project managers and developers with decision-making and predicting future progress. During development, on some occasions, speedy solutions are necessary to meet project schedules. Such quick changes may lead to major quality flaws in the long term, even though they solve local problems in the short term. Controlled management of change is achieved by being able to estimate the impact of changes. In this paper, we propose a new change impact factor estimation and present the design of an experiment to measure these effects, describe its application, and show the measured results of the change impact. Key Words: Change impact factor, software development, product risk model

Change Impact Analysis in Agile Development

2014

Any change that will influence the system’s safety requirements after we have finished the safety analysis and safety planning for development of safety-critical software will require a change impact analysis. One of the reasons for using Scrum is its declarations to “embrace change”. Using agile development we may add new requirements, change existing requirements and make current requirements more detailed both in the product backlog and in the sprint backlogs. Problems, methods and necessary reports related to the consequences of such changes have been discussed and analysed in the SUSS (Agile Development of Safety Critical Software) project. We have come up with an extended Scrum model which includes the change impact analysis for all potential changes to the Scrum backlog. In addition, we have designed a change impact analysis process plus a template for a change impact analysis report. Before we entered the software development part of the project, which is Scrum’s domain, we ...