A new paper on arXiv, titled When Does the Dependency Graph Help Code-to-Architecture Mapping?, tackles the problem of architectural technical debt. The abstract opens by defining this debt as the situation where a system's implementation drifts from its intended modular decomposition, while the mapping between source files and architectural modules is missing, incomplete, or costly to maintain.

The paper's central question is stated in its title: under what circumstances does the dependency graph actually assist in recovering or maintaining that mapping? The abstract does not yet reveal the findings, but the motivation is clear—if dependency graphs can reliably support this mapping, they could reduce the cost and effort of keeping architecture and code aligned.

For now, the published abstract only sets up the problem and the research question. Readers interested in the specific conditions or results will need to wait for the full paper or look beyond the abstract for details.