Foundations for the study of software architecture
ACM SIGSOFT Software Engineering Notes
Software architecture: perspectives on an emerging discipline
Software architecture: perspectives on an emerging discipline
A Classification and Comparison Framework for Software Architecture Description Languages
IEEE Transactions on Software Engineering
Framework for Goal Driven System Design
COMPSAC '02 Proceedings of the 26th International Computer Software and Applications Conference on Prolonging Software Life: Development and Redevelopment
Architecture Decisions: Demystifying Architecture
IEEE Software
Software Architecture as a Set of Architectural Design Decisions
WICSA '05 Proceedings of the 5th Working IEEE/IFIP Conference on Software Architecture
A survey of architecture design rationale
Journal of Systems and Software
A rationale-based architecture model for design traceability and reasoning
Journal of Systems and Software
UML Profiles for Design Decisions and Non-Functional Requirements
SHARK-ADI '07 Proceedings of the Second Workshop on SHAring and Reusing architectural Knowledge Architecture, Rationale, and Design Intent
SEURAT: integrated rationale management
Proceedings of the 30th international conference on Software engineering
Software Architecture: Foundations, Theory, and Practice
Software Architecture: Foundations, Theory, and Practice
Dominion: An Architecture-Driven Approach to Generating Efficient Constraint Solvers
WICSA '11 Proceedings of the 2011 Ninth Working IEEE/IFIP Conference on Software Architecture
PANDArch: a pluggable automated non-intrusive dynamic architecture conformance checker
ECSA'13 Proceedings of the 7th European conference on Software Architecture
| Hi-index | 0.00 |
Besides structural and behavioural properties, rationale plays a crucial role in defining the architecture of a software system. However, unlike other architectural features, rationale often remains unspecified and inaccessible to tools. Existing approaches for recording rationale are not widely adopted. This paper proposes a simple model for capturing rationales as part of an architecture specification and attaching them to elements in the architecture. The bi-directional links between rationales and elements enable forward and backward traceability. We describe a textual architecture description language named Grasp that implements this model, and illustrate its capabilities using an example.