Change Impact Analysis for Requirement Evolution using Use Case Maps

Abstract. One of the main recommended practices to enhance software development process is dealing with requirement change. It represents risks to the success and completion of a project. In this paper a comprehensive review on the impact of Software Requirement Change has been conducted. The literature was written in a historical way and divided into four periods. The results of this review show that most addressed fields in this topic studied the requirement change impact on the time (schedule) and the cost of the software project. Furthermore open research directions in this field are proposed.

show abstract

“…Also, the majority of the research works were intended to discover the impact of RC as in [18], [19], [20] and [21] . In 2004, Nurmuliani et.…”

Section: -2009: Discovering the Impactmentioning

confidence: 99%

“…al. in [20]aimed at to identifying the possible impact of RCs on the software system. They use two types of analysis: slicing and dependency analysis.…”

Section: -2009: Discovering the Impactmentioning

confidence: 99%

The Impact of Software Requirement Change – A Review

Alsanad

Chikh

2015

New Contributions in Information Systems and Technologies

View full text Add to dashboard Cite

show abstract

“…Complementary to our approach, O'Neal addresses the identification of the consequences of a change, such as how much change should be done. Hassine et al [41] provide change impact analysis approach for requirements described as detailed scenarios. Dependencies between scenarios are used to identify the impacted scenarios.…”

Section: Change Impact Analysis In Requirementsmentioning

confidence: 99%

Change impact analysis for requirements: A metamodeling approach

Göknil

Kurtev²,

Berg

et al. 2014

Information and Software Technology

View full text Add to dashboard Cite

a b s t r a c tContext: Following the evolution of the business needs, the requirements of software systems change continuously and new requirements emerge frequently. Requirements documents are often textual artifacts with structure not explicitly given. When a change in a requirements document is introduced, the requirements engineer may have to manually analyze all the requirements for a single change. This may result in neglecting the actual impact of a change. Consequently, the cost of implementing a change may become several times higher than expected. Objective: In this paper, we aim at improving change impact analysis in requirements by using formal semantics of requirements relations and requirements change types. Method: In our previous work we present a requirements metamodel with commonly used requirements relation types and their semantics formalized in first-order logic. In this paper the classification of requirements changes based on structure of a textual requirement is provided with formal semantics. The formalization of requirements relations and changes is used for propagating proposed changes and consistency checking of proposed changes in requirements models. The tool support for change impact analysis in requirements models is an extension of our Tool for Requirements Inferencing and Consistency Checking (TRIC). Results: The described approach for change impact analysis helps in the elimination of some false positive impacts in change propagation, and enables consistency checking of changes. Conclusion: We illustrate our approach in an example which shows that the formal semantics of requirements relations and change classification enables change alternatives to be proposed semi-automatically, the reduction of some false positive impacts and contradicting changes in requirements to be determined.

show abstract

“…Based on use case map (UCM) technique, Hassine et al 40 use requirement dependencies with forwarded slicing algorithm to analyze ripple effect of the changes at the requirement level. The requirement dependencies include scenario dependencies and component-based dependencies.…”

Section: Change Impact Analysismentioning

confidence: 99%

Change impact analysis with a goal-driven traceability-based approach

Lee

Deng

Lee

2010

Int. J. Intell. Syst.

View full text Add to dashboard Cite

Recently, the growing popularity of requirements engineering attracts an increasing attention on requirements traceability and change impact analysis, which also imposes a great demand for a systematic approach in developing software systems to handling traceability relations and requirements changes in an automatic manner. In this work, a goal-driven requirements traceability approach is proposed to develop and manage requirements changes along three dimensions: (1) to develop software and manage requirements based on the goal-driven use case (GDUC) approach, (2) to establish and maintain the traceability relation with a design structure matrix (DSM) to derive the traceability tree, and (3) to analyze requirements change impacts through the partitioning of DSM into blocks to serve as a basis for calculating use case points. The proposed approach is illustrated by a benchmark problem domain of a meeting scheduler system. C 2010 Wiley Periodicals, Inc.

show abstract

Change Impact Analysis for Requirement Evolution using Use Case Maps

Cited by 38 publications

References 14 publications

The Impact of Software Requirement Change – A Review

The Impact of Software Requirement Change – A Review

Change impact analysis for requirements: A metamodeling approach

Change impact analysis with a goal-driven traceability-based approach

Contact Info

Product

Resources

About