Change Impact Analysis based on Formalization of Trace Relations for Requirements

Evolving customer needs is one of the driving factors in software development. There is a need to analyze the impact of requirement changes in order to determine possible conflicts and design alternatives influenced by these changes. The analysis of the impact of requirement changes on related requirements can be based on requirements traceability. In this paper, we propose a requirements metamodel with well defined types of requirements relations. This metamodel represents the common concepts extracted from some prevalent requirements engineering approaches. The requirements relations in the metamodel are used to trace related requirements for change impact analysis. We formalize the relations. Based on this formalization, we define change impact rules for requirements. As a case study, we apply these rules to changes in the requirements specification for Course Management System.

[1]  Francisco J. García-Peñalvo,et al.  Metamodeling for Requirements Reuse , 2002, WER.

[2]  José Ambrosio Toval Álvarez,et al.  REMM-Studio: an Integrated Model-Driven Environment for Requirements Specification, Validation and Formatting , 2007, J. Object Technol..

[3]  Nora Koch,et al.  Towards a Common Metamodell for the Development of Web Appliactions , 2003, ICWE.

[4]  Yves Sorel,et al.  Model-Based Methodology for Requirements Traceability in Embedded Systems , 2007 .

[5]  Sam Supakkul,et al.  A UML profile for goal-oriented and use case-driven representation of NFRs and FRs , 2005, Third ACIS Int'l Conference on Software Engineering Research, Management and Applications (SERA'05).

[6]  Axel van Lamsweerde,et al.  Goal-oriented requirements enginering: a roundtrip from research to practice [enginering read engineering] , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[7]  Anneke Kleppe,et al.  The Object Constraint Language: Getting Your Models Ready for MDA , 2003 .

[8]  P. V. Gorp,et al.  Traceability and Fine-Grained Constraints in Interactive Inconsistency Management , 2006 .

[9]  Henrik Eriksson,et al.  The evolution of Protégé: an environment for knowledge-based systems development , 2003, Int. J. Hum. Comput. Stud..

[10]  Anthony Finkelstein,et al.  A UML profile to support requirements engineering with KAOS , 2002 .

[11]  Samuel Ajila,et al.  Software maintenance: An approach to impact analysis of objects change , 1995, Softw. Pract. Exp..

[12]  Jonathan I. Maletic,et al.  An XML based approach to support the evolution of model-to-model traceability links , 2005, TEFSE '05.

[13]  Matthias Jarke,et al.  Toward Reference Models for , 2001 .

[14]  Ian Horrocks,et al.  OWL Web Ontology Language Reference-W3C Recommen-dation , 2004 .

[15]  Mikael Lindvall,et al.  Traceability aspects of impact analysis in object-oriented systems , 1998 .

[16]  Baowen Xu,et al.  Change impact analysis to support architectural evolution , 2002, J. Softw. Maintenance Res. Pract..

[17]  Ståle Walderhaug,et al.  Towards a Generic Solution for Traceability in MDD , 2006 .

[18]  S.A. Bohner,et al.  Software change impacts-an evolving perspective , 2002, International Conference on Software Maintenance, 2002. Proceedings..

[19]  Ivan Kurtev,et al.  A Metamodeling Approach for Reasoning about Requirements , 2008, ECMDA-FA.

[20]  Gregg Rothermel,et al.  Whole program path-based dynamic impact analysis , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[21]  Alain Abran,et al.  Guide to software engineering body of knowledge : trail version , 2001 .

[22]  Carl K. Chang,et al.  Event-Based Traceability for Managing Evolutionary Change , 2003, IEEE Trans. Software Eng..

[23]  H. Lan,et al.  SWRL : A semantic Web rule language combining OWL and ruleML , 2004 .

[24]  Frank Dignum,et al.  The Role of Deontic Logic in the Specification of Information Systems , 1998, Logics for Databases and Information Systems.

[25]  Luqi A Graph Model for Software Evolution , 1990, IEEE Trans. Software Eng..

[26]  John J. McCarthy,et al.  The Rule Engine for the Java Platform , 2008 .