Survey of Traceability Approaches in Model-Driven Engineering

Models have been used in various engineering fields to help managing complexity and represent information in different abstraction levels, according to specific notations and stakeholder's viewpoints. Model-Driven Engineering (MDE) gives the basic principles for the use of models as primary artefacts throughout the software development phases and presents characteristics that simplify the engineering of software in various domains, such as Enterprise Computing Systems. Hence, for its successful application, MDE processes must consider traceability practices. They help the understanding, capturing, tracking and verification of software artefacts and their relationships and dependencies with other artefacts during the software life-cycle. In this survey, we discuss the state-of-the-art in traceability approaches in MDE and assess them with respect to five general comparison criteria: representation, mapping, scalability, change impact analysis and tool support. As a complementary result, we have identified some open issues that can be better explored by traceability in MDE.

[1]  Depaul,et al.  Dynamically Tracing Non-Functional Requirements through Design Pattern Invariants , 2003 .

[2]  Michael Lawley,et al.  Incremental model transformation for the evolution of model-driven systems , 2006, MoDELS'06.

[3]  Frédéric Jouault.  Loosely Coupled Traceability for ATL , 2005 .

[4]  Juan Garbajosa Sopeña,et al.  The Need for a Unifying Traceability Scheme , 2005 .

[5]  Richard F. Paige,et al.  Merging models with the epsilon merging language (EML) , 2006, MoDELS'06.

[6]  Thomas A. Alspaugh,et al.  Using scenarios to support traceability , 2005, TEFSE '05.

[7]  Alexander Egyed,et al.  A Scenario-Driven Approach to Trace Dependency Analysis , 2003, IEEE Trans. Software Eng..

[8]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[9]  Ivan Kurtev Ivanov,et al.  Adaptability of model transformations , 2005 .

[10]  John Lane,et al.  IEEE Standard Computer Dictionary: Compilation of IEEE Standard Computer Glossaries , 1991 .

[11]  R. Paige,et al.  On-Demand Merging of Traceability Links with Models , 2006 .

[12]  Clémentine Nebut,et al.  Towards a Traceability Framework for Model Transformations in Kermeta , 2006 .

[13]  Maria-Eugenia Iacob,et al.  Requirements Traceability and Transformation Conformance in Model-Driven Development , 2006, 2006 10th IEEE International Enterprise Distributed Object Computing Conference (EDOC'06).

[14]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[15]  Oussama Ben Khadra,et al.  Goal-centric traceability for managing non-functional requirements , 2005, Proceedings. 27th International Conference on Software Engineering, 2005. ICSE 2005..

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

[17]  E. L. Harder,et al.  The Institute of Electrical and Electronics Engineers, Inc. , 2019, 2019 IEEE International Conference on Software Architecture Companion (ICSA-C).

[18]  Krzysztof Czarnecki,et al.  Classification of Model Transformation Approaches , 2003 .

[19]  Ralph Johnson,et al.  design patterns elements of reusable object oriented software , 2019 .

[20]  Julia Rubin,et al.  Model traceability , 2006, IBM Syst. J..

[21]  Ivan Kurtev,et al.  Adaptability of model transformations , 2005 .

[22]  Yolande Berbers,et al.  Supporting modular transformation units with precise transformation traceability metadata , 2005 .

[23]  Frédéric Jouault,et al.  Transforming Models with ATL , 2005, MoDELS.

[24]  Gerald Kotonya,et al.  Software Requirements Engineering , 1999 .