TY - JOUR
T1 - Change impact analysis for requirements
T2 - A metamodeling approach
AU - Goknil, Arda
AU - Kurtev, Ivan
AU - Van Den Berg, Klaas
AU - Spijkerman, Wietze
PY - 2014/8
Y1 - 2014/8
N2 - Context 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.
AB - Context 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.
KW - Change impact analysis
KW - Proposing and propagating changes
KW - Requirements metamodel
UR - http://www.scopus.com/inward/record.url?scp=84900001161&partnerID=8YFLogxK
U2 - 10.1016/j.infsof.2014.03.002
DO - 10.1016/j.infsof.2014.03.002
M3 - Article
AN - SCOPUS:84900001161
SN - 0950-5849
VL - 56
SP - 950
EP - 972
JO - Information and Software Technology
JF - Information and Software Technology
IS - 8
ER -