Change Impact Analysis of Crosscutting in Software Architectural Design

Software architectures should be amenable to changes in user requirements and implementation technology. The analysis of the impact of these 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 present an impact analysis of crosscutting dependencies in architectural design. The analysis is supported by a matrix representation of dependencies.

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

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

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

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

[5]  Hidehiko Masuhara,et al.  Modeling Crosscutting in Aspect-Oriented Mechanisms , 2003, ECOOP.

[6]  Will Venters,et al.  Software engineering: theory and practice , 2006 .

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

[8]  K. G. van den Berg,et al.  A Conceptual Formalization of Crosscutting in AOSD , 2005 .

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

[10]  Thomas Ledoux,et al.  Aspect-Oriented Software Development , 2003 .

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

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

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

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

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

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

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

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

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

[20]  Mikael Lindvall,et al.  Traceability aspects of impact analysis in object-oriented systems , 1998, J. Softw. Maintenance Res. Pract..

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

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

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

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

[25]  Sushil Krishna Bajracharya,et al.  An analysis of modularity in aspect oriented design , 2005, AOSD '05.

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

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