Accepted Papers

Call for Research Papers

The European Conference on Software Architecture (ECSA) is the premier European software architecture conference, providing researchers, practitioners, and educators with a platform to present and discuss the most recent, innovative, and significant findings and experiences in the field of software architecture research and practice. 

The 19th European Conference on Software Architecture (ECSA 2025) will be held from September 15 to 19, 2025. ECSA 2025 is planned as an in-person conference taking place in the beautiful city of Limassol (Cyprus).

Scope

The theme for ECSA 2025 is “impactful software architecture”. The software architecture discipline has had a critical role in shaping robust, scalable, and maintainable systems. We are interested in learning about software architecture principles and practices, emergence trends and case studies highlighting strategic architectural choices that can lead to enhanced performance, improved collaboration, and long-term sustainability. The overarching question is how these architectural principles and practices, both well-established and emerging, are making an impact in real-world systems, and how that impact is being felt across various domains, from enterprise systems to more novel areas like, e.g., AI-driven or autonomous applications? 

The Program Committee of 19th European Conference on Software Architecture seeks submissions of original and unpublished high-quality papers describing fundamental and applied research; new methods, approaches, and processes; novel applications; education and training in software architecture; and experience reports on all topics related to software architecture. 

We particularly encourage papers that demonstrate that diversity in gender, culture, religion, country, etc. are key factors for success and innovation in software architecture.
Topics of interest include, but are not limited to:

• Foundational principles of software architecture

• Relationship of requirements engineering and software architecture

• Quality attributes and software architectures

• Architecture practices for secure, explainable, and trustworthy software

• Architecture design and analysis

• Architecture description languages and meta-models

• Architecture verification and validation

• Management of architectural knowledge, decisions, and rationale

• Architecture patterns, styles, and tactics; reference architectures

• Architecture viewpoints and views

• Architecture conformance

• Software architecture virtualization and visualization

• Architecture-centric process models and frameworks

• Software architecture and agile, incremental, iterative, and continuous development

• Component-based models and deployment; middleware

• Software architecture and system architecture

• Software tools and environments for architecture-centric software engineering

• Ethics, cultural, economic, business, social, human, and managerial aspects of software architecture

• Architecture and technical debt

• Architecting for sustainable and environment friendly systems 

• Applying AI and LLMs in software architecture and architecting for AI and LLM intensive systems. 

• Software architecture education

• Cross-disciplinary approaches to software architecture

• Architectures for reconfigurable and self-adaptive systems

• Architectural concerns of autonomic systems

• Software architecture applied to new and emerging areas, such as the cloud/edge, big data, blockchain, cyber-physical systems, IoT, autonomous systems, systems-of-systems, energy-aware software, quantum computing, AI-enabled systems

• Empirical studies, systematic literature reviews, and mapping studies in software architecture

• Diversity, equity, and inclusion in activities related to software architecture

Paper Submissions

ECSA 2025 seeks four types of papers for the research track:

• Research papers (max. 16 pages in LNCS style) which describe novel contributions to software architecture research (submissions should cover work that has a sound scientific/technological basis and has been validated)

• Education and training papers (max. 16 pages in LNCS style) that address methodologies, experiences and best practices for teaching and training software architecture

• Experience reports (max. 16 pages in LNCS style) that cover innovative implementations, novel applications, insightful performance results and experience in applying software architecture research advances to practical situations and systems

• Short papers (max. 8 pages in LNCS style) that present novel and preliminary work-in-progress or challenges in a topic of software architecture research, education, and training. Submissions must have a sound basis, but not necessarily be validated in full.

All submitted papers will undergo a rigorous double-blind peer review process. Papers will be selected based on originality, quality, soundness, and relevance. All contributions must be original, not published, accepted, or submitted for publication elsewhere. Contravention of this concurrent submission policy will be deemed a serious breach of ethics, and appropriate action will be taken in all such cases. Plagiarism checking will be conducted and any paper reporting more than a 20% match with published work will be desk-rejected.

To note is that research papers, education and training papers, and experience reports that are rejected in their categories may be re-evaluated as short papers only if the committee decides on rejection of the full paper on the basis that it presents preliminary work.

The research track of ECSA 2025 supports an Open Science policy. We encourage all contributing authors to disclose (anonymized and curated) data/artifacts to increase reproducibility. Note that sharing research artifacts is not mandatory for submission or acceptance. Upon submission to the research track, authors are required:

• To make their artifacts available to the program committee (via a link to an anonymous repository) and provide instructions on how to access this data in the paper; or

• To include in the paper an explanation as to why this is not possible or desirable; and

• To indicate why they do not intend to make their data or study materials publicly available upon acceptance, if that is the case.

While sharing research artifacts is not mandatory for submission or acceptance, authors are required to include a Data Availability statement after the Conclusions section in a section named "Data Availability". This statement should explain whether or not data and/or artifacts are available or how they could be accessed (or not). Upon acceptance, papers with Open Science artifacts (e.g., data, tools, etc.) will be invited to upload their artifacts into the ECSA Zenodo community (https://zenodo.org/communities/ecsa) to make them accessible and visible to the ECSA community. Sharing artifacts via the ECSA Zenodo community is required for authors to be eligible for the best Open Artifact award.

All contributions must be formatted according to the Springer LNCS style http://www.springer.com/computer/lncs?SGWID=0-164-6-793341-0. Page limits include figures and references.

Contributions need to be submitted in PDF format via EasyChair to the ECSA 2025 Research Track: https://easychair.org/conferences/?conf=ecsa2025. Please select the “Research Track” in EasyChair for your submission and click "Continue".

The proceedings will be published by Springer as part of the LNCS series. Authors of selected papers will be invited to submit an extended version of their research to a special issue of the Journal of Systems and Software.

Important Dates

Main Conference:

• Abstract submission: March 14, 2025

• Paper submission: March 21, 2025  

• Notification: May 9, 2025   

• Camera-ready paper: June 23, 2025 

All dates are 23:59h AoE (Anywhere on Earth).

Program Co-Chairs

Nour Ali, Brunel University London, UK

Jacopo Soldani, University of Pisa, Pisa

1. Introduction

ECSA aims for an inclusive and transparent review process. The following document outlines review criteria for the “Research Papers” track at ECSA 2025 as well as quality criteria for reviews. We aim to balance clarity and level of detail, i.e., we aim to provide a concise guide to support reviewers. The “Research Papers” track at ECSA 2025 accepts different types of papers (see Call for Papers). The type of paper needs to be taken into consideration when evaluating the merit of a submission. We encourage reviewers to be open, positive and professional:

• Review authorship:PC members were invited because of their expertise. Therefore, we expect PC members to author their reviews, asking for sub-reviewers only for additional feedback. This means that reviewers may solicit help from others. However, reviewers should rewrite the review in their own words, and adjust the scores accordingly. The opinions should be represented as the PC member’s opinions, not those of a sub-reviewer.


• Review quality:PC members are requested to submit a thorough and careful review. Reviewers should pay attention to the bidding process to select those papers closer to their area of expertise.


• Be clear about what is missing: Even if, in the view of a reviewer, a paper does not meet the standards required for acceptance, we encourage reviewers to highlight what, in their opinion, would be necessary to make it acceptable for ECSA (while acknowledging that ECSA submissions are subject to the limitations of conference papers regarding lengths, etc.).


• Numerical scoring:Reviewers should try not to be indecisive (i.e., by scoring most papers in the middle of the numerical range). Please take a stand. Whatever a reviewer’s position is, we ask to justify it in the comments.


• Ethical issues: PC members should inform PC co-chairs if they detect any evidence related to plagiarism, concurrent submission, etc.


• Update reviews:Reviews can be updated at any time, i.e., we encourage reviewers to follow the submitted reviews of submissions assigned to them and make adjustments even before the official discussion period.


• Discussion leaders:For papers that require more detailed discussions to reach a final decision of accepting or rejecting them, we might assign discussion leaders. Discussion leaders will be assigned before or during the discussion period. To reduce the workload for PC members, not all papers will have a discussion leader and we will not assign discussion leaders up front.

2.  Review criteria

Relevance: The extent to which the paper responds to the scope as outlined in the Call for Papers and to which the paper’s contributions are important with respect to software architecture research, practice and education/training. ECSA is interested in growing its community, so we encourage new areas of architecture-related research, even if they are not explicitly mentioned in the Call for Papers. If a reviewer believes that a paper is not relevant for ECSA, we ask for an explanation of why not.

• For RESEARCH PAPERS, the key concern is how the paper discusses implications for software architecture research and/or practice and explains the meaning of the findings (in particular if the focus of the paper is on empirical work).
• For EXPERIENCE REPORT papers, the key concern is the relevance of lessons learned from the paper to software architecture research or practice.
• For EDUCATION AND TRAINING papers, the key concern is how other educators (in higher education or industry) can benefit from the work presented in the paper or learn from insights about how to teach and train (or not teach) software architecture-related topics.
• For SHORT PAPERS, the key concern is how convincing the paper argues that the work, if fully completed, impacts software architecture research, practice or education and training.

Soundness: The extent to which the paper’s claims and contributions are supported by rigorous application of appropriate research methods.

• RESEARCH PAPERS should provide a rigorous description of the research method as well acknowledge limitations and validity threats.
• For EXPERIENCE REPORT and EDUCATION AND TRAINING papers, this typically entails appropriate discussion of the context in which the technology or techniques were applied, such that readers can understand the applicability of the lessons learned (rather than, e.g., controlled experimentation or proofs).
• SHORT PAPERS should have sound proposals for the research and the motivation for the proposed work.

Originality: The extent to which the contribution is sufficiently original and is clearly explained with respect to the state-of-the-art. Note that originality is not about providing surprising or unexpected results or the complexity of a proposed solution, but how the work advances the body-of-knowledge. If a paper lacks important references, we ask reviewers to provide suggestions, but avoid self-citations. When a reviewer’s own work is extremely relevant, they should always contact the PC co-chairs and provide potential alternatives of other related work.

• For RESEARCH PAPERS, there needs to be a clear discussion of how the proposed work fits into the current body of knowledge. For papers that provide new approaches, simple and elegant solutions which still have the potential to improve the state of practice or provide relevant insights are acceptable and should not be criticized for being “too trivial” (in that case, soundness and relevance should be assessed carefully). Also, papers that confirm previous findings are encouraged (as long as findings are discussed in the context of previous works).
• EXPERIENCE REPORT and EDUCATION AND TRAINING papers need not always propose a novel technique, but should still add to the body of knowledge of software architecture in context (e.g., by offering insights into why or how a technique or method works or could be applied in a certain context).
• SHORT PAPERS need to outline how, if the proposed work is completed, advances the body of knowledge in software architecture research, practice, or education and training (e.g., will the contribution be a new technique, new empirical evidence, experience).

Quality: The extent to which the paper’s writing is clear, with well-organized descriptions and explanations, adequate use of the English language, absence of major ambiguities, clearly readable figures and tables, and adherence to the formatting instructions provided. In addition to the above criteria, we also ask reviewers to comment on reproducibility and open science principles. As stated in the Call for Papers, ECSA 2025 supports an Open Science policy. We encourage authors to disclose (anonymized and curated) data/artifacts to increase reproducibility.

Reproducibility and Open Science: The extent to which the paper provides sufficient detail on methods and experiments, and shares information and artifacts that are practical and reasonable to share, to support replication and reproducibility. Note that suitable sharing depends on the type of paper. For example:

• In RESEARCH PAPERS, qualitative interview transcripts often cannot be released due to de-identification risk or industry data may contain trade secrets.
• EDUCATION AND TRAINING might share teaching or training resources.
• EXPERIENCE PAPERS and SHORT PAPERS may not have any supplementary material.

Note that according to the Call for Papers, research artifacts are not mandatory for submission or acceptance.  

Data availability statement: While sharing research artifacts is not mandatory for submission or acceptance, authors are required to include a Data Availability statement after the Conclusions section in a section named "Data Availability". This statement should explain whether or not data and/or artifacts are available or how they could be accessed (or not). More specifically, this statement could be used for the following:

• To make their artifact available to the program committee (via a link to an anonymous repository) – and provide instructions on how to access this data in the paper; or
• To include in the paper an explanation as to why this is not possible or desirable; and
• To indicate why they do not intend to make their data or study materials publicly available upon acceptance, if that is the case.

3.  Review quality criteria

All the reviews are expected to meet the following criteria to provide authors with proper feedback:

• Reviewers will check that the review criteria (see above) are properly satisfied by the submissions evaluated. All reviews will comment on the review criteria.
• Reviewers will provide constructive suggestions or ideas to improve the quality of the paper (even if a paper is not accepted).
• Reviewers will describe criticisms and comments in an argumentative and reasoned way, using a polite tone. ECSA aims to provide a supportive community.
• Reviewers will suggest related work as required, such as empirical standards, related papers highly relevant for the community, open repositories, etc.
• In general, requests to cite a reviewer’s own work are not allowed. Only on request,  providing a strong motivation for how the citation will improve the paper (and explaining why there are no alternative references), and after consultation with the PC co-chairs, citations to a reviewer’s own work might be allowed.

Software Architecture for a Robust, Multithreaded, Realtime, Control System used on an Adaptive Racecar - Harry Direen, Randal Direen, James Direen, Vernon Brabec, Shanjay Kailayanathan and George York – Short Paper

An Approach for Integrated Development of an MLOps Architecture - Petra Heck, Jacco Snoeren, Merel Veracx and Manon Peeters - Full Paper

SAFER-D: A Self-Adaptive Security Framework for Distributed Computing Architectures - Marco Stadler, Michael Vierhauser, Michael Riegler, Daniel Waghubinger and Johannes Sametinger - Full Paper

Towards Legal Knowledge Transfer Based on Software Architecture - Nicolas Boltz, Janne Wagner, Leonie Sterz, Oliver Raabe and Christopher Gerking - Short Paper

Nanosatellite Flight Software: A Rigorous Software Architecture Perspective - Christoforos Vasilakis, Alexandros Tsagkaropoulos, Angelos Motsios, Christos Tsigkanos and Dionysios Reisis - Full Paper

Automated Software Architecture Design Recovery from Source Code Using LLMs - Tiziano Santilli, Marco De Luca, Domenico Amalfitano, Anna Rita Fasolino and Patrizio Pelliccione - Full Paper

Model-based Proactive Self-Adaptation for Cloud Systems - Raphael Straub, Sarah Stieß, Steffen Becker and Matthias Tichy - Full Paper

Architectural Design Decisions and Best Practices for Fast and Efficient CI/CD Pipelines - Francesco Urdih, Theodoros Theodoropoulos and Uwe Zdun - Short Paper

Exploring Architectural Smells Detection Through LLMs - Claudio Tessa, Matteo Bochicchio and Francesca Arcelli Fontana - Short Paper

From Lab to Market: Architectural Evolution in Open Source Transition - Sven Thielen, Björn Salgert and Thomas Franz - Full Paper

Using Incremental LLM Context for Cost Reduction in LLM-Driven IoT Applications - Aashna Sofat and Balwinder Sodhi - Full Paper

LLMs for Software Architecture Knowledge: A Comparative Analysis among Seven LLMs - Mohamed Soliman, Elia Ashraf, Kamel M. K. Abdelsalam, Jan Keim and Ashwin Prasad Shivarpatna Venkatesh - Full Paper

Centrality Change Proneness: an Early Indicator of Microservice Architectural Degradation - Alexander Bakhtin, Matteo Esposito, Valentina Lenarduzzi and Davide Taibi - Full Paper

MLOps in Practice: Requirements and a Reference Architecture from Industry - Indika Kumara, Rowan Arts, Renato Cordeiro Ferreira, Dario Di Nucci, Rick Kazman, Damian Andrew Tamburri and Willem Jan Van Den Heuvel - Full Paper

A Comparative Analysis of Monolith vs Microservices Energy Consumption - Roberta Capuano, Eoan O'Dea and Henry Muccini - Full Paper

Towards Mixed-Criticality Software Architectures for Centralized HPC Platforms in Software-Defined Vehicles: A Systematic Literature Review - Lucas Mauser, Eva Zimmermann, Pavel Nedvědický, Tobias Eisenreich, Moritz Wäschle and Stefan Wagner - Full Paper

Runtime Monitor Synthesis for Automotive Software Architectures - Fazli Faruk Okumus, João-Vitor Zacchi, Maike Salfeld, Markus Schweizer, Núria Mata and Stefan Kugele - Full Paper

How do Practitioners Perceive the Relevance of Software Architecture Research? - Everton Cavalcante, Elisa Yumi Nakagawa, Rick Kazman and Thais Batista - Short Paper

SURE! A Catalog of Uncertainties and RELAXed Requirements for Self-Adaptive Systems - Claudia Raibulet, Ilias Gerostathopoulos and Osman Abdelmukaram - Short Paper

Architecting Federated Learning Systems: A Requirement-Driven Approach - Luciano Baresi, Livia Lestingi and Iyad Wehbe - Full Paper

HarmonE: A Self-Adaptive Approach to Architecting Sustainable MLOps - Hiya Bhatt, Shaunak Biswas, Srinivasan Rakhunathan and Karthik Vaidhyanathan - Full Paper

Data-driven Understanding of Design Decisions in Pattern-based Microservices Architectures - J. Andres Diaz-Pace, Catia Trubiani and David Garlan - Full Paper

LLM-based Quality Assessment of Software Architecture Diagrams: A Preliminary Study with Four Open-Source Projects - Glauber Oliveira and Nabor Mendonca - Short Paper