Student or educator? Sign up with your school email and get 6 months of Pro free.
CoChat

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 access
Wan, Zhiyuan, Zhang, Yun, Xia, Xin, Jiang, Yi, Lo, David · 2023 · Proceedings of the 31st ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering

Abstract

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

Crossref · 10.1145/3611643.3616367

Cites

129 of 129 references verified0 citation errors · 0 not checkable

Statistics

Nothing to recompute.

Figures

Image 1
From the PDF
Image 2
From the PDF

Verification

Claims the paper makes

5 Valid · 14 Not valid · 53 Not checked · 189 Own results and interpretations

124 more claims

Create a free account to see all 261 claims and to verify the 6 references still open.

See all claims — free account
  • Probably not a substantial claim. 93
  • It may state two separate claims as one. 58
  • The quote only partly states this claim. 2

Create a free account to see these claims.

Citations

Cites

Show all 127 references

Research works printed but not linked: 3

  1. 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.
  2. P. Kruchten R. Nord and I. Ozkaya. 2019. Managing technical debt: Reducing friction in software development. Addison-Wesley Professional.
  3. 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

See all 30

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
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.