Papers for

software architects

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Hybrid graph learning improves splitting of monolithic software into microservices

TripleBound: Triplet-Guided Heterogeneous Graph Learning for Microservice Decomposition

Abstract: Cloud computing and DevOps have made microservices a common architecture for scalable, maintainable software systems. However, migrating monoliths to microservices remains challenging due to tight coupling and unclear service boundaries. Existing decomposition approaches typically rely on either structural dependencies or semantic similarity signals, but rarely integrate both within a unified representation learning objective. This paper proposes TripleBound, a hybrid framework for automated monolith-to-microservices decomposition that augments a heterogeneous graph neural network with weakly supervised triplet constraints derived from parser-inferred service groups based on package structure, naming conventions, and code location. TripleBound injects triplet-based constraints directly into the shared structural latent space, enabling both signals to be jointly optimized during representation learning. Structural dependencies are captured using CHGNN, which models the monolith as a heterogeneous graph with program nodes, resource nodes, CALL edges, and CRUD edges. Semantic relationships are incorporated through triplet constraints generated from parser-inferred service groups. Evaluation on AcmeAir, DayTrader, PlantsByWebSphere, and JPetStore shows that TripleBound achieves the highest composite decomposition score under the selected weighting on AcmeAir, DayTrader, and JPetStore compared to CHGNN and MonoEmbed, while CHGNN remains stronger on PlantsByWebSphere. Per-metric analysis reveals trade-offs: gains in structural modularity and inter-partition coupling are accompanied by higher entity distribution imbalance on some datasets. Alternative composite weightings preserve TripleBound's first-place ranking on AcmeAir and DayTrader but not on JPetStore, showing that the aggregate ranking is metric-dependent.

Thu 10 SeptSoftware Engineering
The gist
Breaking a big software program into smaller microservices is hard because the parts are often tightly connected or unclear. The authors developed a method called TripleBound that uses a combination of software structure and naming rules to better identify these parts by representing them as a graph with multiple types of connections. TripleBound uses special constraints during learning to combine these signals in one model. Tests on several example software programs show TripleBound often outperforms other methods, though results vary depending on how success is measured.
Open 2609.11212v1

Context operations improve systems design modelling with large language models

Context operations to architecture modelling output from large language models and evaluation criteria for their use in systems engineering design

Abstract: The development of generative artificial intelligence resources enables opportunities of speeding up systems and engineering design work. This contribution introduces a framework of formal operations for assembling context in LLM-based engineering design. This framework involves the assembly of modular context units, including policy prompts, reference units with persistence, and user questions with prompt vectoring. This approach enables the systematic structuring of interactions with generative models. A formal method for evaluating modelling-as-code LLM outputs is also presented, which enables the evaluation of compliance to intent from LLM answers and thereby asses the support from LLMs for systems architecture modelling.

Wed 9 SeptArtificial IntelligenceSoftware Engineering
The gist
Designing complex systems is often slow and complicated. This paper offers a way to structure how large language models (LLMs) are used in engineering design by organizing different types of information like policies and previous references alongside user questions. The authors also propose a method to check if the model’s outputs really match what the designers want. This helps engineers trust and make better use of AI tools when planning system architectures.
Open 2609.10132v1

Surrogate models speed up multi-objective software architecture optimization

A Surrogate-based Approach for Fast Multi-objective Architectural Refactoring Optimization

Abstract: Software model optimization is a process that generates architecture alternatives aimed at improving quantifiable non-functional properties of software systems, such as performance and reliability. Multi-objective evolutionary algorithms are commonly used to explore the search space and help designers identify trade-offs among competing non-functional properties (e.g., through a Pareto front). However, such algorithms face efficiency challenges in complex software models and large design spaces, since evaluating the fitness (i.e., the quality) of each architecture requires analysis tools that become computationally expensive when repeatedly invoked during the search process. In this paper, we explore the construction of surrogate models based on regression techniques to approximate the outputs of these analysis tools at significantly lower computational cost, while maintaining reasonable output accuracy. Our experimental results suggest that surrogate models provide savings of up to $30\%$ in computational time and maintain the Pareto front quality provided by evolutionary algorithms. Also, we observed some differences in the architectural models produced by our approach. Overall, surrogate models constitute a promising approach for scaling multi-objective architecture optimization to larger spaces and complex architectural models.

Mon 7 SeptSoftware Engineering
The gist
Optimizing software architecture to improve things like speed and reliability often requires testing many design options, which can be very slow. The authors tried using shortcut models that approximate the testing process to save time. These shortcut models can reduce computation time by about 30% while still finding good design trade-offs. This approach helps handle more complex designs more efficiently.
Open 2609.07389v1

Automated analysis reveals common gaps in software architecture records

A Text Mining and Classification Approach for Analyzing Architecture Decision Records

Abstract: Architectural decision records (ADRs) have become a popular lightweight mechanism for documenting architectural knowledge in software projects. However, there is limited empirical evidence on the kinds of architectural concerns captured in ADRs and how well their contents align with established architectural knowledge concepts and documentation practices. In this paper, we propose an automated text-mining and classification approach for analyzing ADRs at scale. We apply this approach to a dataset of ADRs extracted from ~550 open-source repositories, combining topic modeling, LLM-based classification, and template compliance checks. Our analysis examines decision taxonomies and quality attributes, and the degree to which ADRs adhere to the MADR template. Our findings show that ADRs frequently capture existence, technology, and process-related decisions, while alternatives, decisions drivers, and some quality concerns remain under-documented. We also observe recurring mismatches between ADR contents and template sections. These insights into current documentation practices provide architects with valuable information to reflect on how ADRs are and should be used to effectively deal with architectural knowledge. Furthermore, our automated approach is adaptable to other architectural tasks.

Mon 7 SeptSoftware Engineering
The gist
In software projects, teams write down important design decisions in notes called architectural decision records (ADRs). The authors developed a computer method that reads many of these records to see what kinds of decisions get written down and how well the notes follow a common template. They found that some types of decisions, like technology choices, are often recorded, while others, like alternative options and reasons, are missing or poorly documented. This method can help software architects understand and improve how they document design decisions.
Open 2609.07375v1