The DOI matches its Crossref record; 129 of the 129 references it cites were found in a registry or an index; 8 of the 93 sources its claims cite were checked for support.
Software Architecture in Practice: Challenges and Opportunities
Open accessAbstract
Software architecture has been an active research field for nearly four decades, in which previous studies make significant progress such as creating methods and techniques and building tools to support software architecture practice. Despite past efforts, we have little understanding of how practitioners perform software architecture related activities, and what challenges they face. Through interviews with 32 practitioners from 21 organizations across three continents, we identified challenges that practitioners face in software architecture practice during software development and maintenance. We reported on common software architecture activities at software requirements, design, construction and testing, and maintenance stages, as well as corresponding challenges. Our study uncovers that most of these challenges center around management, documentation, tooling and process, and collects recommendations to address these challenges.
Overview
CoChat Summary
TL;DR
Through interviews with 32 practitioners from 21 organizations across three continents, this study maps software architecture activities and challenges across requirements, design, construction/testing, and maintenance. It finds recurring challenges around management, documentation, tooling, and process, and offers recommendations for improving practice and future research.
Key findings
- Challenges cluster into four themes: management/collaboration, documentation, tooling, and process. Specific issues include unpredictable requirements evolution, obsolete design documentation, inadequate tool support for conformance checking, monitoring, architectural smell detection, and refactoring, plus architecture erosion and technical debt.
- Participants included 32 practitioners from 21 organizations: Architect (17), Development (13), Project Management (11), Testing (2); seniority was 10+ years (14), 5–10 years (17), under 5 years (1). Company types were Big tech (7), Non IT (6), Mid-size tech (5), Startup (3); locations were Asia (14), North America (5), Europe (2).
- Architects raised more challenges than non-architects, with a median of 10 vs. 7; participants with 10+ years of experience also raised more than those with less than 10 years, median 10 vs. 7. Participants from PaaS, communications, and intelligent device domains reported the highest median challenge counts: 17, 12, and 12, respectively.
- The study reports common architecture activities and challenges at each stage: requirements evolution; design documentation, decomposition, and architecture analysis/evaluation; conformance checking, continuous monitoring, and code quality; and architecture erosion and refactoring.
Methods
- Qualitative study using Straussian Grounded Theory, with semistructured interviews of 32 software practitioners from 21 organizations; 4 interviews were in-person and 28 online, each 45–60 minutes.
- Participants were selected via maximum variation purposeful sampling; data collection and analysis continued until saturation. Interviews were recorded, transcribed, open coded in NVivo, and analyzed with constant comparison, yielding 272 unique codes (15–79 per interview).
- Findings were triangulated with a literature review of 65 papers and validated with interview participants; all participants indicated general agreement, six responded with comments, and three minor suggested changes were incorporated.
Limitations
- The paper states typical qualitative-research threats and cautions that generalizations beyond the sampled participant distribution should be made with care.
- It notes that participants were sampled through personal networks, which may threaten representativeness for the software industry; in several organizations only one person was interviewed, possibly giving a one-sided perspective.
- The text makes evident that findings rely on self-reported interview data plus literature triangulation, not quantitative or observational validation; the authors call for future quantitative work on how cultural, product, and company characteristics influence architecture practice.
Model-written summary. Check it against the paper before relying on it.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
5 Valid · 14 Not valid · 53 Not checked · 189 Own results and interpretations
The cited sources support only part of this claim — read each source’s verdict below.
In the paper
“Unpredictable evolution and changes of software requirements complicate architecture design ( group , calendar ).”
- Also stated in: § Table 3: Summary of challenges with recommendations. · p. 22 · plain
“Unpredictable evolution and changes of software requirements com- plicate architecture design ( group , calendar ).”
What the sources say
- Supportedcites [3] [3] D. Arcelli, V. Cortellessa, A. Filieri, and A. Leva. 2015. Control theory for modelbased performance-driven software adaptation. In Proc. of the 11th Int'l ACM SIGSOFT Conf. on Quality of Software Architectures . 11-20. - source
The Introduction (page not available in our copy) identifies unpredictable changes, including changes in user requirements, as a challenge for software engineers. It also discusses architectural models used from the early stages of design, supporting the citing sentence’s broad paraphrase. (LLM, conf=0.86)
- Not checked — no full text of the sourcecites [8] [8] B. Baudry, M. Monperrus, C. Mony, F. Chauvel, F. Fleurey, and S. Clarke. 2014. Diversify: ecology-inspired software evolution for diversity emergence. In 2014 Software Evolution Week-IEEE Conf. on Software Maintenance, Reengineering, and Reverse Engineering (CSMR-WCRE) . 395-398. - source
- Supportedcites [23] [23] S. Dasanayake, S. Aaramaa, J. Markkula, and M. Oivo. 2019. Impact of requirements volatility on software architecture: How do software teams keep up with ever-changing requirements? Journal of software: evolution and process 31, 6 (2019), e2160. - source
The Abstract (p. 1) says requirements volatility greatly affects software architecture and that changes in requirements can lead to significant architecture changes. The Conclusions (p. 18) explicitly describe challenges that requirements volatility poses to architecture design, supporting the paraphrase. (LLM, conf=0.94)
- Not checked — no full text of the sourcecites [25] [25] L. De Silva and D. Balasubramaniam. 2012. Controlling software architecture erosion: A survey. Journal of Systems and Software 85, 1 (2012), 132-151. - source
- Partly supportedcites [62] [62] T. Mens, S. Demeyer, O. Barais, A. F. Le Meur, L. Duchien, and J. Lawall. 2008. Software architecture evolution. Software Evolution (2008), 233-262. - sourceExperimental — accuracy not yet measured
The “VIII Feedback system” section says that the precise evolution of software requirements is difficult to predict, and the discussion of E-type systems describes requirements that can change over time. The passages do not establish the further claim that this complicates architecture design. (LLM, conf=0.84)
- Not checked — no full text of the sourcecites [94] [94] M. Szlenk, A. Zalewski, and S. Kijas. 2012. Modelling architectural decisions under changing requirements. In 2012 Joint Working IEEE/IFIP Conf. on Software Architecture and European Conf. on Software Architecture . 211-214. - source
- Not checked — no full text of the sourcecites [96] [96] A. Tang, P. Liang, and H. Van Vliet. 2011. Software architecture documentation: The road ahead. In 2011 Ninth Working IEEE/IFIP Conf. on Software Architecture . 252-255. - source
plainstates a cause- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Also stated in: § Table 3: Summary of challenges with recommendations. · p. 22 · plain
Every source the paper cites for this claim was checked and supports it.
In the paper
“Despite abundant research on architecture knowledge management [17], little is used in practice to ensure the completeness, upto-dateness, and traceability of architecture documentation.”
What the sources say
- Supportedcites [17] [17] R. Capilla, A. Jansen, A. Tang, P. Avgeriou, and M. A. Babar. 2016. 10 years of software architecture knowledge management: Practice and future. Journal of Systems and Software 116 (2016), 191-205. - source
The Introduction and §3.2 describe substantial AKM research, while §4.1 reports that interviewed practitioners generally did not use systematic architecture-documentation approaches. The Introduction says architectural knowledge is often incomplete and out of date, and §2.4 says relationships needed for traceability are usually not expressly captured. Together, these passages support the citing sentence’s broad characterization. (LLM, conf=0.87)
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Supported
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“Organizations rarely provide tool support for impact analysis of architecture refactoring due to limited traceability information between architecture, design and implementation artifacts.”
plainstates a cause- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“Practitioners tend to manually perform module- and system-level refactoring, with limited support from automated testing frameworks.”
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
A result the paper reports from its own data — it cites no other source for it, so there is none to check. The quote shows it is in the paper.
In the paper
“Participants perceive impact analysis as a challenging activity when it comes to architecture refactoring.”
plain- Asserted: passes — The authors put it forward as true.
- Checkable: passes — It can be checked against evidence.
- Load-bearing: passes — The paper’s conclusions depend on it.
- Based: passes — The paper gives a reason why it holds.
- Rests on an assumption not shown here.
124 more claims
Create a free account to see all 261 claims and to verify the 6 references still open.
- Probably not a substantial claim. 93
- It may state two separate claims as one. 58
- The quote only partly states this claim. 2
Citations
Cites
Basics of Qualitative Research: Grounded Theory Procedures and Techniques
Long, D. R., Strauss, A., & Corbin, J. (1993) · The Modern Language Journal · doi:10.2307/328955 · Cited by 17,576
Enhancing the quality and credibility of qualitative analysis.
(1999) · PubMed Central · Cited by 4,133
Purposeful Sampling in Qualitative Research Synthesis
Suri, H. (2011) · Qualitative Research Journal · doi:10.3316/qrj1102063 · Cited by 2,284 · cited 1×
“Note that some participants take more than one role in their projects.”
BackgroundThe 4+1 View Model of architecture
Kruchten, P. B. (1995) · IEEE Software · doi:10.1109/52.469759 · Cited by 2,158
Foundations for the study of software architecture
Perry, D. E., & Wolf, A. L. (1992) · ACM SIGSOFT Software Engineering Notes · doi:10.1145/141874.141884 · Cited by 2,023
A classification and comparison framework for software architecture description languages
Medvidovic, N., & Taylor, R. N. (2000) · IEEE Transactions on Software Engineering · doi:10.1109/32.825767 · Cited by 1,987 · cited 1×
“…approaches for documenting the relevant views of software architecture to help practitioners successfully use it, maintain it, and build a software system from it, including unified modeling language, architecture description languages (e.g., [58]), and domain-specific languages (e.g., [59]).”
BackgroundDocumenting software architectures: views and beyond
Clements, P., Garlan, D., Little, R., Nord, R., & Stafford, J. (2003) · 25th International Conference on Software Engineering, 2003. Proceedings. · doi:10.1109/icse.2003.1201264 · Cited by 1,430 · cited 4×
“Software architecture practice embraces the concept of architecture view , which represents a partial aspect of the high-level structures of a software system [20].”
BackgroundMethodInfluentialToward reference models for requirements traceability
Ramesh, B., & Jarke, M. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.895989 · Cited by 912 · cited 1×
“Traceability of architecture knowledge improves understandability of software architectures, helps to locate relevant knowledge, enables impact analysis of architectural changes, and facilitates design review, evaluation and assessment [50, 78].”
BackgroundSoftware Architecture as a Set of Architectural Design Decisions
Jansen, A., & Bosch, J. (2006) · 5th Working IEEE/IFIP Conference on Software Architecture (WICSA'05) · doi:10.1109/wicsa.2005.61 · Cited by 615
How We Refactor, and How We Know It
Murphy-Hill, E., Parnin, C., & Black, A. P. (2012) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2011.41 · Cited by 547
Research works printed but not linked: 3
- P. Clements F. Bachmann L. Bass D. Garlan J. Ivers R. Little P. Merson R. Nord and J. Stafford. 2010. Documenting Software Architectures: Views and Beyond. Pearson Education.
- P. Kruchten R. Nord and I. Ozkaya. 2019. Managing technical debt: Reducing friction in software development. Addison-Wesley Professional.
- Z. Wan, Y. Zhang, X. Xia, Y. Jiang, and D. Lo. 2023. Software Architecture in Practice: Challenges and Opportunities. arXiv 2308.09978. · arXiv
Cited by
6GSoft: Software for Edge-to-Cloud Continuum
Akbar, M. A., Esposito, M., Hyrynsalmi, S., Kumar, K. D., Lenarduzzi, V., Li, X., Mehraj, A., Mikkonen, T., Moreschini, S., Mäkitalo, N., et al. (2024) · Euromicro Conference on Software Engineering and Advanced Applications (SEAA) · doi:10.1109/seaa64295.2024.00082 · Cited by 25
“Given the complex nature of current software architectures, orchestrating large-scale systems demands substantial resources [20].”
Experimenting Architectural Patterns in Federated Learning Systems
Compagnucci, I., Pinciroli, R., & Trubiani, C. (2025) · Journal of Systems and Software · doi:10.1016/j.jss.2025.112655 · Cited by 11
On the correlation between architectural smells and static analysis warnings
Esposito, M., Robredo, M., Fontana, F. A., & Lenarduzzi, V. (2025) · Software Quality Journal · doi:10.1007/s11219-025-09730-7 · Cited by 10
“The risk of service degradation and disruption for critical services is exponentially increasing due to the pervasive nature of computing and the widespread adoption of digital services in all areas of daily life [1].”
Application of AI in Software Architecture Development at Volvo Construction Equipment
Johansson, N., & Caporuscio, M. (2025) · Lecture notes in computer science · doi:10.1007/978-3-032-04403-7_12 · Cited by 5
A Model-Driven Platform for Software Applications on Heterogeneous Computing Environments
Bauco, S., Angelis, G. D., Marotta, R., et al. (2025) · IEEE International Conference on Software Architecture Companion (ICSA-C) · doi:10.1109/icsa-c65153.2025.00064 · Cited by 3
“In this sense, software architectures [4, 5] (SAs) give the possibility to reason on a system in terms of a set of design concepts that can be properly interconnected in order to cooperatively offer some functionality.”
Metadata
- Authors
- Wan, Z., Zhang, Y., Xia, X., Jiang, Y., & Lo, D.
- Affiliations
- Zhejiang University (CN)
- Hangzhou City University (CN)
- Huawei Technologies (China) (CN)
- Singapore Management University (SG)
- Venue
- Proceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering
- Publisher
- ACM
- Published
- 2023-11-30
- Pages
- 1457-1469
- OpenAlex
- W4386113668
- Cited by
- 30
- References
- 127
- Citations by year
- 2026: 10 · 2025: 13 · 2024: 7
- FWCI
- 5.32
- Type
- conference paper
- Language
- en
- Open access
- bronze
- doi.org
- Locations
- ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) (publishedVersion)
- arXiv (Cornell University) (submittedVersion)
- Singapore Management University Institutional Knowledge (InK) (Singapore Management University) (submittedVersion, cc-by-nc-nd)
- arXiv (Cornell University)
- Funders
- National Key R&D Program of China (2020YFB1005400)
- National Science Foundation of China (62102358)
- Natural Science Foundation of Zhejiang Province (LQ21F020008)
- Topics
- Physical Sciences › Computer Science › Software › Advanced Software Engineering Methodologies
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Software › Model-Driven Software Engineering Techniques
- Keywords
- software architecture, practitioner challenges, software requirements, software design, software construction, software testing, software maintenance, architectural documentation, architecture management, software development process
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
The claim verdicts this report counts are experimental: their accuracy is not yet measured.
A language model drew the claims from the paper on 2026-10-10, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).
A second model labelled each claim on 2026-10-10 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).
Cited sources are checked with a language model’s help (gpt-6-sol).
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Software Architecture in Practice: Challenges and Opportunities. https://app.cochat.ai/papers/10.1145/3611643.3616367
- The paper
- Wan, Z., Zhang, Y., Xia, X., Jiang, Y., & Lo, D. (2023). Software Architecture in Practice: Challenges and Opportunities. Proceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering. https://doi.org/10.1145/3611643.3616367
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.

