An industrial case study of architecture conformance
Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement
Introducing Architecture-Centric Reuse into a Small Development Organization
ICSR '08 Proceedings of the 10th international conference on Software Reuse: High Confidence Software Reuse in Large Systems
Towards a Dependency Constraint Language to Manage Software Architectures
ECSA '08 Proceedings of the 2nd European conference on Software Architecture
A dependency constraint language to manage object-oriented software architectures
Software—Practice & Experience
Concepts of modeling architectural module views for compliance checks based on architectural styles
SEA '07 Proceedings of the 11th IASTED International Conference on Software Engineering and Applications
Analyzing security architectures
Proceedings of the IEEE/ACM international conference on Automated software engineering
Assessing architectural drift in commercial software development: a case study
Software—Practice & Experience
Using code analysis tools for architectural conformance checking
Proceedings of the 6th International Workshop on SHAring and Reusing Architectural Knowledge
ReflexML: UML-based architecture-to-code traceability and consistency checking
ECSA'11 Proceedings of the 5th European conference on Software architecture
Controlling software architecture erosion: A survey
Journal of Systems and Software
Generation of task-specific architecture documentation for developers
Proceedings of the 17th international doctoral symposium on Components and Architecture
Maintaining architectural conformance during software development: a practical approach
ECSA'13 Proceedings of the 7th European conference on Software Architecture
Proceedings of the WICSA 2014 Companion Volume
Hi-index | 0.00 |
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.