A Comparison of Static Architecture Compliance Checking Approaches
Authors:
- 1 January 2007
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- p. 12
Abstract
The software architecture is one of the most important artifacts created in the lifecycle of a software system. It enables, facilitates, hampers, or interferes directly the achievement of business goals, functional and quality requirements. One instrument to determine how adequate the architecture is for its intended usage is architecture compliance checking. This paper compares three static architecture compliance checking approaches (reflexion models, relation conformance rules, and component access rules) by assessing their applicability in 13 distinct dimensions. The results give guidance on when to use which approach.Keywords
This publication has 12 references indexed in Scilit:
- Equipping the Reflexion Method with Automated Clustering2006
- Static evaluation of software architectures2006
- An evolutionary testbed for software technology evaluationInnovations in Systems and Software Engineering, 2005
- Hierarchical reflexion models2004
- ArchJava: connecting software architecture to implementation2003
- A method for module architecture verification and its application on a large component-based systemInformation and Software Technology, 2003
- Languages for formalizing, visualizing and verifying software architecturesComputer Languages, 2001
- Software reflexion models: bridging the gap between design and implementationIEEE Transactions on Software Engineering, 2001
- A classification and comparison framework for software architecture description languagesIEEE Transactions on Software Engineering, 2000
- Architectural mismatch: why reuse is so hardIEEE Software, 1995