Change impact analysis for requirements: A metamodeling approach

Abstract

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.

Leveraging Historical Associations between Requirements and Source Code to Identify Impacted Classes

“…His study highlights the many different ways in which change impact analysis can be used and the diverse stages of a project at which it can be applied. For instance, during early-stage activities, change impact analysis can help identify impacts of requirements changes on other requirements [91], [92]. During late-stage activities, change impact analysis can support the quality and correctness of software architectures [93].…”

Semi-Automatized Assessment of Requirement Interrelations

“…By applying graph-theoretical approaches such as active or passive sum, clustering or identification of paths, the structure of the requirement graph can be analysed. According to contemporary state-of-research in software engineering, requirements and their interrelations are analysed to evaluate the propagation of requirement changes (Knethen and Grund, 2003;Goknil et al, 2014;Zhang et al, 2014). Various dependency types are identified (Pohl, 1996;Dahlstedt and Persson, 2005;Zhang et al, 2014).…”

Automated change impact analysis between SysML models of requirements and design

“…van den Berg [27] augments traceability links with dependency type information between software artifacts. Goknil et al [28] extend the approach of van den Berg [27] with formal semantics and apply it for impact analysis over requirements. When the requirements are expressed as models, more specialized dependency types may be defined.…”