Analysis of Crosscutting in Model Transformations

This paper describes an approach for the analysis of crosscutting in model transformations in the Model Driven Architecture (MDA). Software architectures should be amenable to changes in user requirements and technological platforms. Impact analysis of changes can be based on traceability of architectural design elements. Design elements have dependencies with other software artifacts but also evolve in time. Crosscutting dependencies may have a strong influence on modifiability of software architectures. We define crosscutting based on a traceability pattern. We present an impact analysis of crosscutting dependencies in transformations rules at model level as well as at meta-model level.

[1]  Juan Hernández,et al.  Analysis of crosscutting across software development phases based on traceability , 2006, EA '06.

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

[3]  Betty H. C. Cheng,et al.  Retrieval by Construction: a Traceability Technique to Support Verification and Validation of Uml Formalizations , 2005, Int. J. Softw. Eng. Knowl. Eng..

[4]  Mike Danilovic,et al.  The use of dependence structure matrix and domain mapping matrix in managing uncertainty in multiple project situations , 2005 .

[5]  Axel Uhl,et al.  Model-Driven Architecture , 2002, OOIS Workshops.

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

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

[8]  Shawn A. Bohner,et al.  Impact analysis-Towards a framework for comparison , 1993, 1993 Conference on Software Maintenance.

[9]  James E. Tomayko,et al.  The structural complexity of software an experimental test , 2005, IEEE Transactions on Software Engineering.

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

[11]  Klaas van den Berg,et al.  Change Impact Analysis of Crosscutting in Software Architectural Design , 2006 .

[12]  Andrea Zisman,et al.  Rule-based generation of requirements traceability relations , 2004, J. Syst. Softw..

[13]  T. Gardner,et al.  A review of OMG MOF 2 . 0 Query / Views / Transformations Submissions and Recommendations towards the final Standard , 2003 .

[14]  José María Conejero,et al.  Disentangling Crosscutting in AOSD: A Conceptual Framework , 2005 .

[15]  H. Q. Nguyen.  Analysis of Crosscutting Concerns in QVT-based Model Transformations , 2006 .

[16]  Paul Clements,et al.  Software Architecture in Practice: Addison-Wesley , 1998 .

[17]  Ruzanna Chitchyan,et al.  AOSD Ontology 1.0: Public Ontology of Aspect-Orientation , 2005 .

[18]  Kim B. Clark,et al.  The power of modularity , 2000 .

[19]  Tzilla Elrad,et al.  Aspect-Oriented Software Development , 2004 .

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

[21]  Frédéric Jouault,et al.  Evaluation of rule-based modularization in model transformation languages illustrated with ATL , 2006, SAC '06.

[22]  Christopher G. Lasater,et al.  Design Patterns , 2008, Wiley Encyclopedia of Computer Science and Engineering.

[23]  Peter Fettke.  Unified modeling language 2.0 , 2007 .

[24]  Joaquin Miller,et al.  MDA Guide Version 1.0.1 , 2003 .

[25]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[26]  Ivan Kurtev,et al.  MISTRAL: A Language for Model Transformations in the MOF Meta-modeling Architecture , 2004, MDAFA.

[27]  K. G. van den Berg,et al.  Identification of Crosscutting in Software Design , 2006 .