A survey of architecture design rationale
Journal of Systems and Software
Using Bayesian belief networks for change impact analysis in architecture design
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
Towards practical software traceability
Companion of the 30th international conference on Software engineering
Software designers, are you biased?
Proceedings of the 6th International Workshop on SHAring and Reusing Architectural Knowledge
Rationale, decisions and alternatives traceability for architecture design
Proceedings of the 5th European Conference on Software Architecture: Companion Volume
RCDA: Architecting as a risk- and cost management discipline
Journal of Systems and Software
Towards quantitative metrics for architecture models
Proceedings of the WICSA 2014 Companion Volume
Hi-index | 0.00 |
Architecture modeling is practiced extensively in the software industry but there is little attention paid to the traceability, verifiability and completeness of architecture designs. Deficiencies in any of these three areas in an architecture model can be costly and risky to projects. We propose the Architecture Rationalization Method (ARM), which is based on architecture rationale, to overcome these issues. ARM makes use of both qualitative and quantitative rationales for selecting architecture designs. Quantitative rationale uses a model based on costs, benefits and risks in the selection process. ARM provides a method to determine when an architecture model is complete in that the level of details represented by the architecture design is sufficient. We apply ARM to a real-life industry case retrospectively to demonstrate how ARM can overcome issues surrounding traceability and verifiability.