Abstract

A key aspect of architecture-centric development is the traceability of design documentation. In particular, architects should be always aware of the relationships between the architectural model "as documented" and its corresponding implementation model. The problem is that these two models usually diverge from each other over time, due to factors such as new requirements, refactorings, etc. Therefore, tool assistance is very important to assess the level of conformance between architectural documentation and implementation. In this paper, we present a tool approach called Arch Sync? that helps architects to conciliate architectural documentation expressed through Use-Case Maps with Java source code, as modifications are being made on the code. Arch Sync? relies on a heuristic that incrementally detects inconsistencies with respect to the architectural prescriptions, based on the analysis of system execution traces. Arch Sync? can also give suggestions for re-synchronization. Results of two case-studies showing the applicability of the approach are reported.

-- Daniel Amyot - 07 Jul 2010

Discussion

• Paper available at http://dx.doi.org/10.1109/WICSA.2009.5290801
• Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.