Using code analysis tools for architectural conformance checking

Authors:
Jo Van Eyck;Nelis Boucké;Alexander Helleboogh;Tom Holvoet
Affiliations:
K.U.Leuven, Leuven, Belgium;K.U.Leuven, Leuven, Belgium;K.U.Leuven, Leuven, Belgium;K.U.Leuven, Leuven, Belgium
Venue:
Proceedings of the 6th International Workshop on SHAring and Reusing Architectural Knowledge
Year:
2011

Citing 4
Cited 0

A Comparison of Static Architecture Compliance Checking Approaches

WICSA '07 Proceedings of the Sixth Working IEEE/IFIP Conference on Software Architecture
Using Types to Enforce Architectural Structure

WICSA '08 Proceedings of the Seventh Working IEEE/IFIP Conference on Software Architecture (WICSA 2008)
Unifying software architecture with its implementation

Proceedings of the Fourth European Conference on Software Architecture: Companion Volume
Static Architecture-Conformance Checking: An Illustrative Overview

IEEE Software

Quantified Score

Hi-index	0.00

Visualization

Abstract

Architectural conformance checking verifies whether a system conforms to its intended architecture, which is essential to safeguard the quality attributes of the system. Due to the size of many systems, performing conformance checking by means of manual code inspections is often practically infeasible. Code analysis tools can be used to automatically check architectural conformance. In this paper, we investigate several code analysis tools that offer support for Java and compare them on their usefulness for architectural conformance checking: Architecture Rules, Macker, Lattix DSM, SonarJ, Structure101 and XDepend.