Sign inGet started
Paper · arXiv

When Does the Dependency Graph Help Code-to-Architecture Mapping?

Architectural technical debt arises when a system's implementation drifts from its inten ded modular decomposition, while the mapping between source files and architectural modu les is missing, incomplete, or costly to maintain manually. We formulate code-to-archite cture mapping as semi-supervised node classification over a directed multi-relational de pendency graph, with files as nodes, typed dependencies as edges, and lexical features d erived from code identifiers and directory layout. Starting from a small labeled sample, an iterative self-training procedure expands the mapping to the remaining files. We com pare a graph convolutional network (GCN), a graph attention network (GAT), ...

AuthorsRakhshanda Jabeen, Morgan Ericsson, Jonas Nordqvist et al.
Primary categorycs.SE
Published14 October 2026
Last updated at source14 October 2026
cs.SEcs.LG
Embed this entry
<iframe src="https://silytics.si/embed/item/3dd99418-8e13-45bf-b9ac-fe99775ff298" width="420" height="190" style="border:0" loading="lazy" title="Silytics entry"></iframe>

Free, no tracking. More about feeds and embeds.

Silytics shows public metadata from arXiv and links to the original. Information may be incomplete or out of date. Last refreshed 15 October 2026. Licenses and terms of the original apply to the work itself. Not financial, legal or professional advice.