AI & ML
What Carries Architectural Signal? A Code-to-Architecture Mapping Study
arXiv cs.SE0 views
arXiv:2610.41628v1 Announce Type: new Abstract: Code-to-architecture mapping assigns source files to modules of a reference architecture. Representations of implementation artifacts can capture code text, dependencies, and directory organization, but predictive gains alone do not establish the contribution of additional graph processing. Dependencies may already be encoded in these representations, while directories may closely match the reference decomposition. We investigate how artifact representations and graph context affect mapping on ten Java, C, and C++ systems with a limited labeling budget. We compare lexical, structural, and contextual file representations and assess each predictor with and without dependency neighbors. Using a Heterogeneous Graph Transformer (HGT), we compare file-level graphs extended with member nodes summarizing each file's program elements, folder nodes, or both, alongside a variant encoding folder paths directly in file representations. We compare folder-aware predictions with a directory rule using the same labeled files. Representations encoding dependency information outperform lexical representations on most systems. Additional neighbor aggregation can improve mapping, depending on the predictor and aggregation direction. Folder-aware variants yield the largest and most consistent gains across the evaluated HGT configurations. However, the directory rule achieves per-system median accuracy of 89-100%, and adding folder information does not consistently improve predictions for files the rule misclassifies. Member nodes provide no consistent improvement over file-level graphs. These findings support assessing what file representations and directory organization already provide before attributing improvements to graph neural networks.
Source:https://arxiv.org/abs/2610.41628PreviousPrompt Less, Infer More: Static Analysis-Guided LLM Type Annotation for PythonNextA Failure Mode Taxonomy and Severity Model for Ethereum Smart Contracts
Related posts

How Akai and Moog are embracing vibe-coded mods
0The Verge

Big Tech lost big in the 2026 election
0The Verge
How to keep shared short links and QR codes working when a campaign destination changes
0dev.to
Microsoft Entra ID Security: Why Revoking Sessions Isn't Enough
0dev.to
AI Companies Really, Really Want to Buy Your Work Files and Emails
0Wired
Ramp data shows AI spending stalling just as Anthropic nears its IPO
0TechCrunch