Recording the reasons for design decisions
ICSE '88 Proceedings of the 10th international conference on Software engineering
Software Architecture as a Set of Architectural Design Decisions
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
A web-based tool for managing architectural design decisions
ACM SIGSOFT Software Engineering Notes
A general model of software architecture design derived from five industrial approaches
Journal of Systems and Software
Modeling and Documenting the Evolution of Architectural Design Decisions
SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
An architectural design decision-centric approach to architectural evolution
ICACT'09 Proceedings of the 11th international conference on Advanced Communication Technology - Volume 1
A classification of value for software architecture decisions
ECSA'10 Proceedings of the 4th European conference on Software architecture
Model evolution and management
MBEERTS'07 Proceedings of the 2007 International Dagstuhl conference on Model-based engineering of embedded real-time systems
Modeling in the large and modeling in the small
MDAFA'03 Proceedings of the 2003 European conference on Model Driven Architecture: foundations and Applications
MoDELS'05 Proceedings of the 2005 international conference on Satellite Events at the MoDELS
A case study on co-evolution of software artifacts using integrated views
Proceedings of the WICSA/ECSA 2012 Companion Volume
Hi-index | 0.00 |
Architectural design decisions (i.e., those decisions made when architecting software systems) are considered an essential piece of knowledge to be carefully documented and maintained. As any other artifact, architectural design decisions may evolve, having an impact on other design decisions, or on related artifacts (like requirements and architectural elements). It is therefore important to document and analyze the impact of an evolving decision on other related decisions or artifacts. In this work we propose an approach based on a notation-independent metamodel that becomes a means for systematically defining traceability links, enabling inter-decision and extra-decision evolution impact analysis. The purpose of such an analysis is to check the presence of inconsistencies that may occur during evolution. An Eclipse plugin has been realized to implement the approach.