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
On the automatic modularization of software systems using the Bunch tool
Mitchell, B. S., & Mancoridis, S. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.31 · Cited by 479 · cited 1×
“Software decomposition has been extensively studied in prior research of software engineering [53, 64], in which software clustering has become an active research area. software clustering is defined as the process of decomposing large software systems into smaller, manageable, highly cohesive,…”
BackgroundArchitecture Decisions: Demystifying Architecture
Tyree, J., & Akerman, A. (2005) · IEEE Software · doi:10.1109/ms.2005.27 · Cited by 459 · cited 1×
“The early literature has made great efforts to develop approaches and tools for capturing architecture design decisions explicitly, including formal models (e.g., [39]) and description templates (e.g., [97]).”
An exploration of technical debt
Tom, E., Aurum, A., & Vidgen, R. (2013) · Journal of Systems and Software · doi:10.1016/j.jss.2012.12.052 · Cited by 438 · cited 2×
“An example of pragmatism, creating a minimum viable product in a short amount of time, is noted in prior research [46, 100], which is also recounted by some participants (P3b, P3g, P5a, P6a).”
BackgroundSoftware Architecture: The Next Step
Bosch, J. (2004) · Lecture Notes in Computer Science · doi:10.1007/978-3-540-24769-2_14 · Cited by 324 · cited 1×
“Jan Bosch emphasized that “designing a system can be viewed as a decision process” [12].”
BackgroundSoftware Architecture Optimization Methods: A Systematic Literature Review
Aleti, A., Buhnova, B., Grunske, L., Koziolek, A., & Meedeniya, I. (2013) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2012.64 · Cited by 293 · cited 1×
“…studies have put effort into developing methods and tools for architecture representation and documentation [15, 38], analysis and evaluation [41, 73], recovery and optimization [2, 30, 54], as well as knowledge management and decision making [16, 100] to support software architecture practice.”
MethodThe golden age of software architecture
Shaw, M., & Clements, P. (2006) · IEEE Software · doi:10.1109/ms.2006.58 · Cited by 271 · cited 1×
“The research field of software architecture has achieved tremendous progress since its inception in the 1980s [85].”
BackgroundKnowledge management: problems, promises, realities, and challenges
Fischer, G., & Otswald, J. (2001) · IEEE Intelligent Systems · doi:10.1109/5254.912386 · Cited by 269
Nahar, N., Zhou, S., Lewis, G. A., & Kästner, C. (2022) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/3510003.3510209 · Cited by 261
Measure it? Manage it? Ignore it? software practitioners and technical debt
Ernst, N. A., Bellomo, S., Ozkaya, I., Nord, R. L., & Gorton, I. (2015) · Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering · doi:10.1145/2786805.2786848 · Cited by 260 · cited 1×
“Despite the benefits of architectural refactoring, prior studies [29, 44] also reported that developers perceive the structural changes at architectural scale as costly, complicated, and risky, and failing to implement such changes incurs significant consequences.”
Background(2012) · doi:10.1145/2393596.2393655 · Cited by 239 · cited 1×
“Despite the benefits of architectural refactoring, prior studies [29, 44] also reported that developers perceive the structural changes at architectural scale as costly, complicated, and risky, and failing to implement such changes incurs significant consequences.”
BackgroundAn Empirical Study of RefactoringChallenges and Benefits at Microsoft
Kim, M., Zimmermann, T., & Nagappan, N. (2014) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2014.2318734 · Cited by 231
Challenges of shared decision-making: A multiple case study of agile software development
Moe, N. B., Aurum, A., & Dybå, T. (2012) · Information and Software Technology · doi:10.1016/j.infsof.2011.11.006 · Cited by 205 · cited 1×
“…(e.g., [33]), methods (e.g., [26]), and tools (e.g., [31]), and shift their focus towards addressing the social and psychological aspects of architectural decision making behaviors including naturalistic and rational decision making [66], cognitive biases [67], and group decision making [11, 80].”
MethodHow we refactor, and how we know it
Murphy-Hill, E., Parnin, C., & Black, A. P. (2009) · 2009 IEEE 31st International Conference on Software Engineering · doi:10.1109/icse.2009.5070529 · Cited by 197 · cited 1×
“The difficulty in such activities manifests itself in a variety of ways, e.g., increased cost, complex implementation, and highly scattered code changes.”
BackgroundAn effectiveness measure for software clustering algorithms
Wen, Z., & Tzerpos, V. (2004) · IEEE International Conference on Program Comprehension (ICPC) · doi:10.1109/wpc.2004.1311061 · Cited by 195 · cited 1×
“…and experiences of stakeholders and further using their tacit knowledge (e.g., [13]), creating scenario profiles for a concrete description of quality attributes (e.g., [72]), architecture conformance and compliance checking (e.g., [93]), and using various quality metrics (e.g., MoJoFM [106]).”
BackgroundSoftware Documentation Issues Unveiled
Aghajani, E., Nagy, C., Vega-Marquez, O. L., Linares-Vasquez, M., Moreno, L., Bavota, G., & Lanza, M. (2019) · 2019 IEEE/ACM 41st International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2019.00122 · Cited by 195 · cited 2×
“Placing documentation in standard locations is an effective practice to help practitioners locate it, as suggested in the literature (e.g., [1]).”
BackgroundControlling software architecture erosion: A survey
de Silva, L., & Balasubramaniam, D. (2012) · Journal of Systems and Software · doi:10.1016/j.jss.2011.07.036 · Cited by 184
How does Machine Learning Change Software Development Practices?
Wan, Z., Xia, X., Lo, D., & Murphy, G. C. (2020) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2019.2937083 · Cited by 181
Self-citationFrom Monolith to Microservices: A Dataflow-Driven Approach
Chen, R., Li, S., & Li, Z. (2017) · 2017 24th Asia-Pacific Software Engineering Conference (APSEC) · doi:10.1109/apsec.2017.53 · Cited by 181 · cited 2×
“To identify and tailor services based on business requirements, some organizations use Domain-Driven Design (DDD) as a flexible methodology to create a high level of microservices architecture design with an iterative design and development process (P3a, P3f, P4a, P5a; (cid:17) ).”
MethodA comparative analysis of software architecture recovery techniques
Garcia, J., Ivkovic, I., & Medvidovic, N. (2013) · 2013 28th IEEE/ACM International Conference on Automated Software Engineering (ASE) · doi:10.1109/ase.2013.6693106 · Cited by 175 · cited 1×
“…studies have put effort into developing methods and tools for architecture representation and documentation [15, 38], analysis and evaluation [41, 73], recovery and optimization [2, 30, 54], as well as knowledge management and decision making [16, 100] to support software architecture practice.”
Method10 years of software architecture knowledge management: Practice and future
Capilla, R., Jansen, A., Tang, A., Avgeriou, P., & Babar, M. A. (2016) · Journal of Systems and Software · doi:10.1016/j.jss.2015.08.054 · Cited by 160 · cited 4×
“The discovery of architecture knowledge allows reasoning and uncovering design problems and alternatives [16].”
BackgroundMethodInfluentialDetecting software modularity violations
Wong, S., Cai, Y., Kim, M., & Dalton, M. (2011) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/1985793.1985850 · Cited by 131
A dataflow-driven approach to identifying microservices from monolithic applications
Li, S., Zhang, H., Jia, Z., Li, Z., Zhang, C., Li, J., Gao, Q., Ge, J., & Shan, Z. (2019) · Journal of Systems and Software · doi:10.1016/j.jss.2019.07.008 · Cited by 128 · cited 1×
“As for a microservice architecture, it is challenging to decompose a software system into the optimal number of microservices with appropriate levels of granularity (P3a, P4d, P5a, P11a) [18, 48].”
MethodA tool for managing software architecture knowledge
Babar, M. A., & Ian, G. (2007) · University of Limerick Institutional Repository (University of Limerick) · doi:10.34961/9733 · Cited by 123
On the Relevance of Code Anomalies for Identifying Architecture Degradation Symptoms
Macia, I., Arcoverde, R., Garcia, A., Chavez, C., & von Staa, A. (2012) · 2012 16th European Conference on Software Maintenance and Reengineering · doi:10.1109/csmr.2012.35 · Cited by 121
Cohesion Metrics for Predicting Maintainability of Service-Oriented Software
Perepletchikov, M., Ryan, C., & Frampton, K. (2007) · Seventh International Conference on Quality Software (QSIC 2007) · doi:10.1109/qsic.2007.4385516 · Cited by 115
Cost, benefits and quality of software development documentation: A systematic mapping
Zhi, J., Garousi-Yusifoğlu, V., Sun, B., Garousi, G., Shahnewaz, S., & Ruhe, G. (2015) · Journal of Systems and Software · doi:10.1016/j.jss.2014.09.042 · Cited by 112 · cited 1×
“The incompleteness of design documentation is also discussed in the literature (e.g., [109]).”
BackgroundMacia, I., Garcia, J., Popescu, D., Garcia, A., Medvidovic, N., & von Staa, A. (2012) · Proceedings of the 11th annual international conference on Aspect-oriented Software Development · doi:10.1145/2162049.2162069 · Cited by 111 · cited 1×
“” Previous studies indicate that certain patterns of co-occurrence of code smells tend to be effective indicators of architectural erosion [9, 35, 53, 59].”
BackgroundKnowledge-based approaches in software documentation: A systematic literature review
Ding, W., Liang, P., Tang, A., & van Vliet, H. (2014) · Information and Software Technology · doi:10.1016/j.infsof.2014.01.008 · Cited by 107 · cited 1×
“These findings align with literature past observations that design documents are typically written in natural languages with supporting diagrams [26].”
ResultUse, disuse, and misuse of automated refactorings
Vakilian, M., Chen, N., Negara, S., Rajkumar, B. A., Bailey, B. P., & Johnson, R. E. (2012) · 2012 34th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2012.6227190 · Cited by 106 · cited 1×
“The difficulty in such activities manifests itself in a variety of ways, e.g., increased cost, complex implementation, and highly scattered code changes.”
Background(2009) · doi:10.1109/wicsa.2009.5290823 · Cited by 106 · cited 1×
“The formal models and description templates have consensus on capturing rationale, constraints, and alternatives of architectural design decisions [86].”
Metrics for Measuring the Quality of Modularization of Large-Scale Object-Oriented Software
Sarkar, S., Kak, A. C., & Rama, G. M. (2008) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2008.43 · Cited by 106
HIPAcc: A Domain-Specific Language and Compiler for Image Processing
Membarth, R., Reiche, O., Hannig, F., Teich, J., Korner, M., & Eckert, W. (2016) · IEEE Transactions on Parallel and Distributed Systems · doi:10.1109/tpds.2015.2394802 · Cited by 102 · 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]).”
BackgroundMicroservices and Their Design Trade-Offs: A Self-Adaptive Roadmap
Hassan, S., & Bahsoon, R. (2016) · 2016 IEEE International Conference on Services Computing (SCC) · doi:10.1109/scc.2016.113 · Cited by 98 · cited 1×
“To identify and tailor services based on business requirements, some organizations use Domain-Driven Design (DDD) as a flexible methodology to create a high level of microservices architecture design with an iterative design and development process (P3a, P3f, P4a, P5a; (cid:17) ).”
MethodSmart Contract Security: A Practitioners' Perspective
Wan, Z., Xia, X., Lo, D., Chen, J., Luo, X., & Yang, X. (2021) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1109/icse43902.2021.00127 · Cited by 95
Self-citation(2019) · doi:10.1109/techdebt.2019.00027 · Cited by 94 · cited 4×
“For example, some participants observed god components as an architectural smell (P2a, P3b, P3d-f) [5], as expressed by P3b (architect): “some components have taken on way too many”
BackgroundInfluentialArchitectural Knowledge: Getting to the Core
de Boer, R. C., Farenhorst, R., Lago, P., van Vliet, H., Clerc, V., & Jansen, A. G. J. (2007) · Lecture notes in computer science · doi:10.1007/978-3-540-77619-2_12 · Cited by 90 · cited 1×
“, sharing, compliance, discovery and traceability [24].”
Enriching software architecture documentation
Jansen, A., Avgeriou, P., & van der Ven, J. S. (2009) · Journal of Systems and Software · doi:10.1016/j.jss.2009.04.052 · Cited by 85 · cited 2×
“Previous studies have put effort into developing methods and tools for architecture representation and documentation [15, 38], analysis and evaluation [41, 73], recovery and optimization [2, 30, 54], as well as knowledge management and decision making [16, 100] to support software architecture…”
BackgroundMethodDetecting, Tracing, and Monitoring Architectural Tactics in Code
Mirakhorli, M., & Cleland-Huang, J. (2016) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2015.2479217 · Cited by 85 · cited 1×
“Architecture monitoring aims to quantify the health status of software systems in a continuous way, and evaluate whether the symptoms of architecture problems crept into a system [63].”
BackgroundApplications of clustering techniques to software partitioning, recovery and restructuring
Lung, C.-H., Zaman, M., & Nandi, A. (2004) · Journal of Systems and Software · doi:10.1016/s0164-1212(03)00234-6 · Cited by 81 · cited 1×
“Software decomposition has been extensively studied in prior research of software engineering [55, 66], in which software clustering has become an active research area.”
BackgroundComparing Software Architecture Recovery Techniques Using Accurate Dependencies
Lutellier, T., Chollak, D., Garcia, J., et al. (2015) · Proceedings/Proceedings - International Conference on Software Engineering · doi:10.1109/icse.2015.136 · Cited by 81 · cited 1×
“…studies have put effort into developing methods and tools for architecture representation and documentation [15, 38], analysis and evaluation [41, 73], recovery and optimization [2, 30, 54], as well as knowledge management and decision making [16, 100] to support software architecture practice.”
MethodA Tool for Managing Software Architecture Knowledge
Babar, M. A., & Gorton, I. (2007) · doi:10.1109/shark-adi.2007.1 · Cited by 80
Decoupling level: a new metric for architectural maintenance complexity
Mo, R., Cai, Y., Kazman, R., Xiao, L., & Feng, Q. (2016) · Proceedings of the 38th International Conference on Software Engineering · doi:10.1145/2884781.2884825 · Cited by 80
Decision making in software architecture
van Vliet, H., & Tang, A. (2016) · Journal of Systems and Software · doi:10.1016/j.jss.2016.01.017 · Cited by 79
Past and future of software architectural decisions – A systematic mapping study
Tofan, D., Galster, M., Avgeriou, P., & Schuitema, W. (2014) · Information and Software Technology · doi:10.1016/j.infsof.2014.03.009 · Cited by 77 · cited 1×
“We have seen a number of meta-models that aim at representing design decisions and rationale [50, 94].”
BackgroundApplication of knowledge-based approaches in software architecture: A systematic mapping study
Li, Z., Liang, P., & Avgeriou, P. (2013) · Information and Software Technology · doi:10.1016/j.infsof.2012.11.005 · Cited by 74 · cited 2×
“We have seen a number of meta-models that aim at representing design decisions and rationale [50, 94].”
BackgroundSelić, B. (2009) · IEEE Software · doi:10.1109/ms.2009.167 · Cited by 72
Cui, J. F., & Chae, H. S. (2011) · Information and Software Technology · doi:10.1016/j.infsof.2011.01.006 · Cited by 71 · cited 1×
“…in prior research of software engineering [53, 64], in which software clustering has become an active research area. software clustering is defined as the process of decomposing large software systems into smaller, manageable, highly cohesive, loosely coupled, and feature-oriented subsystems [21].”
BackgroundSoftware architecture review: the state of practice
Babar, M. A., & Ian, G. (2009) · Arrow@dit (Dublin Institute of Technology) · doi:10.34961/9603 · Cited by 71
Mohanani, R., Ralph, P., & Shreeve, B. (2014) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/2568225.2568235 · Cited by 56 · cited 1×
“…(e.g., [33]), methods (e.g., [26]), and tools (e.g., [31]), and shift their focus towards addressing the social and psychological aspects of architectural decision making behaviors including naturalistic and rational decision making [66], cognitive biases [67], and group decision making [11, 80].”
MethodA Literature Review of Automatic Traceability Links Recovery for Software Change Impact Analysis
Aung, T. W. W., Huo, H., & Sui, Y. (2020) · International Conference on Program Comprehension · doi:10.1145/3387904.3389251 · Cited by 53 · cited 1×
“In practice, some organizations encourage practitioners manually build traceability links by including snip-pets of design documentation or its link in commit description (P2a), Javadoc comments (P4b), or code review comments (P6a).”
BackgroundQuantifying the Analyzability of Software Architectures
Bouwers, E., Correia, J. P., Arie Van Deursen, A., & Visser, J. (2011) · Working IEEE/IFIP Conference on Software Architecture (WICSA) · doi:10.1109/wicsa.2011.20 · Cited by 51
ARCADE: an extensible workbench for architecture recovery, change, and decay evaluation
Laser, M. S., Medvidović, N., Le, D. M., & Garcia, J. (2020) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3368089.3417941 · Cited by 50 · cited 1×
“Architectural changes occur during regular development and maintenance activities, which involve a wider spectrum of code components, as well as dependencies among them than local code changes [82].”
BackgroundSoftware Module Clustering: An In-Depth Literature Analysis
Sarhan, Q. I., Ahmed, B. S., Bureš, M., & Zamli, K. Z. (2020) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2020.3042553 · Cited by 50
Challenges to and Solutions for Refactoring Adoption: An Industrial Perspective
Sharma, T., Suryanarayana, G., & Samarthyam, G. (2015) · IEEE Software · doi:10.1109/ms.2015.105 · Cited by 46
Software Architecture Documentation: The Road Ahead
Tang, A., Liang, P., & Vliet, H. V. (2011) · 2011 Ninth Working IEEE/IFIP Conference on Software Architecture · doi:10.1109/wicsa.2011.40 · Cited by 46 · cited 1×
“The unpredictable evolution and changes of requirements sometimes make it infeasible to deliver new features or meet the quality requirements with current architectures, as frequently mentioned in the literature [3, 8, 22, 24, 60, 90, 92].”
BackgroundJaved, M. A., & Zdun, U. (2014) · International Conference on Evaluation and Assessment in Software Engineering (EASE) · doi:10.1145/2601248.2601278 · Cited by 45
Understanding software architecture erosion: A systematic mapping study
Li, R., Liang, P., Soliman, M., & Avgeriou, P. (2022) · Journal of Software: Evolution and Process · doi:10.1002/smr.2423 · Cited by 45 · cited 2×
“The phenomenon of divergence between the intended and implemented architectures is regarded as architecture erosion [49].”
BackgroundExamining decision characteristics & challenges for agile software development
Drury-Grogan, M. L., Conboy, K., & Acton, T. (2017) · Journal of Systems and Software · doi:10.1016/j.jss.2017.06.003 · Cited by 45 · cited 1×
“…conduct empirical studies to investigate architectural decision-making practice including decision-making process (e.g., [33]), methods (e.g., [26]), and tools (e.g., [31]), and shift their focus towards addressing the social and psychological aspects of architectural decision making…”
BackgroundThe Value of Software Documentation Quality
Plosch, R., Dautovic, A., & Saft, M. (2014) · 2014 14th International Conference on Quality Software · doi:10.1109/qsic.2014.22 · Cited by 44 · cited 1×
“Software architecture refers to a collection of design decisions that affect the structure, behavior, and overall quality of a software sys-tem [20, 79], serving as the foundation for subsequent decisions [77].”
BackgroundA systematic mapping study on architectural smells detection
Mumtaz, H., Singh, P., & Blincoe, K. (2021) · Journal of Systems and Software · doi:10.1016/j.jss.2020.110885 · Cited by 44 · cited 1×
“Architectural smells indicate the structural problems in the components and their interactions with other components of software systems that are caused by architecture antipatterns, misuse or violation of architecture styles, and violation of design principles [68].”
BackgroundSoftware Architecture Evolution
Barais, O., Meur, A.-F. L., Duchien, L., & Lawall, J. (2008) · Springer eBooks · doi:10.1007/978-3-540-76440-3_10 · Cited by 43
Predicting Design Impactful Changes in Modern Code Review: A Large-Scale Empirical Study
Uchoa, A., Barbosa, C., Coutinho, D., Oizumi, W., Assuncao, W. K. G., Vergilio, S. R., Pereira, J. A., Oliveira, A., & Garcia, A. (2021) · 2021 IEEE/ACM 18th International Conference on Mining Software Repositories (MSR) · doi:10.1109/msr52588.2021.00059 · Cited by 42 · cited 1×
“It is complex for practitioners to comprehend the scopes and impacts of architectural changes [95, 103].”
BackgroundA Unified Approach to Architecture Conformance Checking
Caracciolo, A., Lungu, M. F., & Nierstrasz, O. (2015) · Working IEEE/IFIP Conference on Software Architecture (WICSA) · doi:10.1109/wicsa.2015.11 · Cited by 41
How Developers Discuss Architecture Smells? An Exploratory Study on Stack Overflow
Tian, F., Liang, P., & Babar, M. A. (2019) · IEEE International Conference on Software Architecture (ICSA) · doi:10.1109/icsa.2019.00018 · Cited by 40
A holistic architecture assessment method for software product lines
Olumofin, F. G., & Mišić, V. B. (2007) · Information and Software Technology · doi:10.1016/j.infsof.2006.05.003 · Cited by 40 · cited 1×
“…and experiences of stakeholders and further using their tacit knowledge (e.g., [13]), creating scenario profiles for a concrete description of quality attributes (e.g., [72]), architecture conformance and compliance checking (e.g., [93]), and using various quality metrics (e.g., MoJoFM [106]).”
BackgroundDesign Rule Spaces: A New Model for Representing and Analyzing Software Architecture
Cai, Y., Xiao, L., Kazman, R., Mo, R., & Feng, Q. (2019) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2018.2797899 · Cited by 39 · cited 1×
“Previous studies have put effort into developing methods and tools for architecture representation and documentation [15, 38], analysis and evaluation [41, 73], recovery and optimization [2, 30, 54], as well as knowledge management and decision making [16, 100] to support software architecture…”
MethodSoftware Module Clustering: An In-Depth Literature Analysis
Sarhan, Q. I., Ahmed, B. S., Bures, M., & Zamli, K. Z. (2020) · IEEE Transactions on Software Engineering · doi:10.48550/arxiv.2012.01057 · Cited by 38
Terra, R., Valente, M. T., Czarnecki, K., & Bigonha, R. S. (2015) · Software: Practice and Experience · doi:10.1002/spe.2228 · Cited by 37 · cited 1×
“, [97]), and using various quality metrics (e.”
Software Architecture: A Comprehensive Framework and Guide for Practitioners
Vogel, O., Arnold, I., Chughtai, A., & Kehrer, T. (2011) · doi:10.1007/978-3-642-19736-9 · Cited by 36
On the Evolutionary Nature of Architectural Violations
Brunet, J., Bittencourt, R. A., Serey, D., & Figueiredo, J. (2012) · 2012 19th Working Conference on Reverse Engineering · doi:10.1109/wcre.2012.35 · Cited by 34 · cited 1×
“As our participants reported, some organizations use unit testing, stress testing, and performance testing frameworks, to continuously monitor the quality of software systems (P2a, P3a, P3c, P3e-f, P4b-d, P5a, P7a, P11a, P12a, P14a, P19b).”
BackgroundEvaluating architectural stability using a metric-based approach
Tonu, S. A., Ashkan, A., & Tahvildari, L. (2006) · doi:10.1109/csmr.2006.26 · Cited by 34 · cited 1×
“From an evolution perspective, architecture analysis and evaluation is a preventive activity to improve qualitative attributes, delay architectural decay, limit the effect of software aging, and identify architectural drift and erosion of software systems [57, 101].”
BackgroundSoftware architecture review by association
Tang, A., & Lau, M. F. (2014) · Journal of Systems and Software · doi:10.1016/j.jss.2013.09.044 · Cited by 33 · cited 1×
“It is complex for practitioners to comprehend the scopes and impacts of architectural changes [95, 103].”
BackgroundHow Do Software Architects Specify and Validate Quality Requirements?
Caracciolo, A., Lungu, M. F., & Nierstrasz, O. (2014) · Lecture Notes in Computer Science · doi:10.1007/978-3-319-09970-5_32 · Cited by 32 · cited 1×
“Instead, some organizations rely heavily on periodical manual inspection, in line with the observations of previous studies (e.g., [17]).”
ResultDasanayake, S., Aaramaa, S., Markkula, J., & Oivo, M. (2019) · Journal of Software: Evolution and Process · doi:10.1002/smr.2160 · Cited by 32 · cited 1×
“The unpredictable evolution and changes of requirements sometimes make it infeasible to deliver new features or meet the quality requirements with current architectures, as frequently mentioned in the literature [3, 8, 22, 24, 60, 90, 92].”
BackgroundKazman, R., Goldenson, D., Monarch, I., Nichols, W., & Valetto, G. (2016) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2015.2465387 · Cited by 31 · cited 1×
“The benefits of software architecture documentation have been widely investigated in previous studies, e.g., serving as an educational tool to introduce new team members to a software project [20] and reduce entry barriers for new contributors in OSS development [42].”
MethodA Study on Group Decision-Making in Software Architecture
Rekhav, V. S., & Muccini, H. (2014) · 2014 IEEE/IFIP Conference on Software Architecture · doi:10.1109/wicsa.2014.15 · Cited by 31 · cited 1×
“…(e.g., [33]), methods (e.g., [26]), and tools (e.g., [31]), and shift their focus towards addressing the social and psychological aspects of architectural decision making behaviors including naturalistic and rational decision making [66], cognitive biases [67], and group decision making [11, 80].”
MethodScaling up software architecture analysis
Kazman, R., Gagliardi, M., & Wood, W. (2012) · Journal of Systems and Software · doi:10.1016/j.jss.2011.03.050 · Cited by 31 · cited 1×
“…studies have put effort into developing methods and tools for architecture representation and documentation [15, 38], analysis and evaluation [41, 73], recovery and optimization [2, 30, 54], as well as knowledge management and decision making [16, 100] to support software architecture…”
MethodExperiences in assessing product family software architecture for evolution
Maccari, A. (2002) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/581339.581414 · Cited by 30
Detecting architecturally-relevant code smells in evolving software systems
Bertran, I. M. (2011) · Proceedings of the 33rd International Conference on Software Engineering · doi:10.1145/1985793.1986003 · Cited by 28 · cited 1×
“Conversely, developers are suggested to be actively involved (P3f), by providing explanations or rationale behind implementation decisions that violate the criteria for metrics as specified in monitoring tools.”
BackgroundHow Does Contributors' Involvement Influence the Build Status of an Open-Source Software Project?
Rebouças, M., dos Santos, R. O., Pinto, G., & Castor, F. (2017) · International Conference on Mining Software Repositories (MSR) · doi:10.1109/msr.2017.32 · Cited by 28 · cited 1×
“Software architecture refers to a collection of design decisions that affect the structure, behavior, and overall quality of a software sys-tem [20, 79], serving as the foundation for subsequent decisions [77].”
BackgroundA survey on software architecture evaluation methods
Patidar, A., & Suman, U. (2015) · International Conference on Computing for Sustainable Global Development · Cited by 26
On assessing the complexity of software architectures
Zhao, J. (1998) · doi:10.1145/288408.288450 · Cited by 24
Exploration of technical debt in start-ups
Klotins, E., Unterkalmsteiner, M., Chatzipetrou, P., Gorschek, T., Prikladnicki, R., Tripathi, N., & Pompermaier, L. B. (2018) · Proceedings of the 40th International Conference on Software Engineering: Software Engineering in Practice · doi:10.1145/3183519.3183539 · Cited by 24 · cited 1×
“The performance metrics generated by automated testing frameworks tend to serve as an indicator of architecture problems, e.g., performance degradation.”
MethodControl Theory for Model-based Performance-driven Software Adaptation
Arcelli, D., Cortellessa, V., Filieri, A., & Leva, A. (2015) · Proceedings of the 11th International ACM SIGSOFT Conference on Quality of Software Architectures · doi:10.1145/2737182.2737187 · Cited by 23 · cited 1×
“the quality requirements with current architectures, as frequently mentioned in the literature [3, 8, 23, 25, 62, 94, 96].”
BackgroundAutomatic Identification of Decisions from the Hibernate Developer Mailing List
Li, X., Liang, P., & Li, Z. (2020) · Proceedings of the Evaluation and Assessment in Software Engineering · doi:10.1145/3383219.3383225 · Cited by 21 · cited 1×
“Recently, researchers pro-pose approaches for the automatic extraction of design decisions from different information sources (e.g., [49]), e.g., email archives, issue management systems, commit messages, and Stack Overflow.”
BackgroundExperiences in assessing product family software architecture for evolution
Maccari, A. (2002) · Proceedings of the 24th international conference on Software engineering - ICSE '02 · doi:10.1145/581413.581414 · Cited by 20 · cited 1×
“From an evolution perspective, architecture analysis and evaluation is a preventive activity to improve qualitative attributes, delay architectural decay, limit the effect of software aging, and identify architectural drift and erosion of software systems [55, 96].”
BackgroundIndustry experiences with large-scale refactoring
Ivers, J., Nord, R. L., Ozkaya, I., Seifried, C., Timperley, C. S., & Kessentini, M. (2022) · Proceedings of the 30th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering · doi:10.1145/3540250.3558954 · Cited by 19 · cited 2×
“Architecture refactoring [37], also known as large-scale refactoring, involves structural and broad changes at an architectural scale to maintain the structural quality of an evolving software system, and facilitate its success to facilitate the integration of new features.”
BackgroundNahar, N., Zhou, S., Lewis, G. A., & Kästner, C. (2021) · arXiv (Cornell University) · doi:10.48550/arxiv.2110.10234 · Cited by 18
A Lightweight Sanity Check for Implemented Architectures
Bouwers, E., & van Deursen, A. (2010) · IEEE Software · doi:10.1109/ms.2010.60 · Cited by 17 · cited 1×
“…analysis and evaluation, including extracting intuitions and experiences of stakeholders and further using their tacit knowledge (e.g., [13]), creating scenario profiles for a concrete description of quality attributes (e.g., [72]), architecture conformance and compliance checking…”
BackgroundA Study on Architectural Decision-Making in Context
Groher, I., & Weinreich, R. (2015) · Working IEEE/IFIP Conference on Software Architecture (WICSA) · doi:10.1109/wicsa.2015.27 · Cited by 17 · cited 1×
“In addition, researchers conduct empirical studies to investigate architectural decision-making practice including decision-making process (e.g., [33]), methods (e.g., [26]), and tools (e.g., [31]), and shift their focus towards addressing the social and psychological aspects of architectural…”
BackgroundBørte, K., Ludvigsen, S., & Mørch, A. I. (2012) · Information and Software Technology · doi:10.1016/j.infsof.2012.03.002 · Cited by 17 · cited 1×
“…(e.g., [33]), methods (e.g., [26]), and tools (e.g., [31]), and shift their focus towards addressing the social and psychological aspects of architectural decision making behaviors including naturalistic and rational decision making [66], cognitive biases [67], and group decision making [11, 80].”
MethodDIVERSIFY: Ecology-inspired software evolution for diversity emergence
Baudry, B., Monperrus, M., Mony, C., Chauvel, F., Fleurey, F., & Clarke, S. (2014) · 2014 Software Evolution Week - IEEE Conference on Software Maintenance, Reengineering, and Reverse Engineering (CSMR-WCRE) · doi:10.1109/csmr-wcre.2014.6747203 · Cited by 14 · cited 1×
“The unpredictable evolution and changes of requirements sometimes make it infeasible to deliver new features or meet the quality requirements with current architectures, as frequently mentioned in the literature [3, 8, 22, 24, 60, 90, 92].”
BackgroundModelling Architectural Decisions under Changing Requirements
Szlenk, M., Zalewski, A., & Kijas, S. (2012) · Working IEEE/IFIP Conference on Software Architecture (WICSA) · doi:10.1109/wicsa-ecsa.212.31 · Cited by 14 · cited 1×
“The unpredictable evolution and changes of requirements sometimes make it infeasible to deliver new features or meet the quality requirements with current architectures, as frequently mentioned in the literature [3, 8, 22, 24, 60, 90, 92].”
BackgroundKnowledge scouts: Reducing communication barriers in a distributed software development project
Dutoit, A. H., Johnstone, J., & Bruegge, B. (2005) · Asia-Pacific Software Engineering Conference (APSEC) · doi:10.1109/apsec.2001.991510 · Cited by 14 · cited 1×
“A shared understanding of architecture knowledge among stake-holders of software systems alleviates miscommunication and information overload, especially for the software systems that are produced by practitioners from different geographic areas [27].”
BackgroundMiksovic, C., & Zimmermann, O. (2011) · Working IEEE/IFIP Conference on Software Architecture (WICSA) · doi:10.1109/wicsa.2011.43 · Cited by 14 · cited 1×
“it is challenging to effectively share and reuse architecture knowledge [64].”
BackgroundIs Self-Admitted Technical Debt a Good Indicator of Architectural Divergences?
Sierra, G., Tahmid, A., Shihab, E., & Tsantalis, N. (2019) · IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER) · doi:10.1109/saner.2019.8667999 · Cited by 13
How Deep is the Mud: Fathoming Architecture Technical Debt Using Designite
Sharma, T. (2019) · doi:10.1109/techdebt.2019.00018 · Cited by 13
Object-Oriented Software Systems Restructuring through Clustering
Şerban, G., & Czibula, I. G. (2008) · Lecture notes in computer science · doi:10.1007/978-3-540-69731-2_67 · Cited by 12
Architecture-sensitive heuristics for prioritizing critical code anomalies
Guimarães, E., Garcia, A., & Cai, Y. (2015) · Proceedings of the 14th International Conference on Modularity · doi:10.1145/2724525.2724567 · Cited by 12 · cited 1×
“Conversely, developers are suggested to be actively involved (P3f), by providing explanations or rationale behind implementation decisions that violate the criteria for metrics as specified in monitoring tools.”
BackgroundA Case Study of Measuring Degeneration of Software Architectures from a Defect Perspective
Li, Z., & Long, J. (2011) · 2011 18th Asia-Pacific Software Engineering Conference · doi:10.1109/apsec.2011.51 · Cited by 12 · cited 1×
“” Previous studies indicate that certain patterns of co-occurrence of code smells tend to be effective indicators of architectural erosion [9, 35, 53, 59].”
BackgroundAutomatic enforcement of constraints in real-time collaborative architectural decision making
Gaubatz, P., Lytra, I., & Zdun, U. (2015) · Journal of Systems and Software · doi:10.1016/j.jss.2015.01.056 · Cited by 11 · cited 1×
“…to investigate architectural decision-making practice including decision-making process (e.g., [33]), methods (e.g., [26]), and tools (e.g., [31]), and shift their focus towards addressing the social and psychological aspects of architectural decision making behaviors including naturalistic…”
BackgroundCommunication in Multidisciplinary Systems Architecting
Bonnema, G. M. (2014) · Procedia CIRP · doi:10.1016/j.procir.2014.03.188 · Cited by 11 · cited 1×
“It seems beneficial to adopt more formal architecture documentation for capturing the tradeoffs in architecture design, and constructing trace links between requirements and design decisions ( ), which has been suggested in the literature [6, 10, 30].”
BackgroundStop the software architecture erosion
Merkle, B. (2010) · Companion to the ACM SIGPLAN Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA Companion) · doi:10.1145/1869542.1869621 · Cited by 11
Stop the software architecture erosion: building better software systems
Merkle, B. (2010) · Proceedings of the ACM international conference companion on Object oriented programming systems languages and applications companion · doi:10.1145/1869542.1869563 · Cited by 10 · cited 1×
“Software maintenance aims to modify the software system and ensure that the system continues to satisfy requirements while preserving its integrity.”
BackgroundAre code smell detection tools suitable for detecting architecture degradation?
Lenhard, J., Hassan, M. M., Blom, M., & Herold, S. (2017) · Proceedings of the 11th European Conference on Software Architecture: Companion Proceedings · doi:10.1145/3129790.3129808 · Cited by 10 · cited 1×
“Conversely, developers are suggested to be actively involved (P3f), by providing explanations or rationale behind implementation decisions that violate the criteria for metrics as specified in monitoring tools.”
BackgroundMuszynski, M., Lugtigheid, S., Castor, F., & Brinkkemper, S. (2022) · 2022 IEEE 19th International Conference on Software Architecture (ICSA) · doi:10.1109/icsa53651.2022.00013 · Cited by 10
Mastering Erosion of Software Architecture in Automotive Software Product Lines
Strasser, A., Cool, B., Gernert, C., Knieke, C., Körner, M., Niebuhr, D., Peters, H., Rausch, A., Brox, O., Jauns-Seyfried, S., et al. (2014) · Lecture Notes in Computer Science · doi:10.1007/978-3-319-04298-5_43 · Cited by 9
Williams, B. J., & Carver, J. C. (2014) · Empirical Software Engineering · doi:10.1007/s10664-012-9223-y · Cited by 8 · cited 1×
“The complexity elevates the cost and effort of implementing architectural changes across the software development lifecycle [107].”
BackgroundTrends in continuous evaluation of software architectures
Soares, R. C., Capilla, R., dos Santos, V., & Nakagawa, E. Y. (2023) · Computing · doi:10.1007/s00607-023-01161-1 · Cited by 8
Architectural Consistency Checking in Plugin-Based Software Systems
Greifenberg, T., Müller, K., & Rumpe, B. (2015) · Proceedings of the 2015 European Conference on Software Architecture Workshops · doi:10.1145/2797433.2797493 · Cited by 7 · cited 1×
“Conversely, developers are suggested to be actively involved (P3f), by providing explanations or rationale behind implementation decisions that violate the criteria for metrics as specified in monitoring tools.”
BackgroundOn the Relationship between Program Evolution and Fault-Proneness: An Empirical Study
Jaafar, F., Hassaine, S., Gueheneuc, Y., Hamel, S., & Adams, B. (2013) · 2013 17th European Conference on Software Maintenance and Reengineering · doi:10.1109/csmr.2013.12 · Cited by 5 · cited 1×
“Software maintenance aims to modify the software system and ensure that the system continues to satisfy requirements while preserving its integrity.”
BackgroundSoftware architecture review by association
TangAntony, & LauMan, F. (2014) · Journal of Systems and Software · doi:10.5555/2747015.2747187 · Cited by 5
(2010) · reroDoc Digital Library · Cited by 2
What motivates software practitioners to contribute to inner source?
Wan, Z., Xia, X., Zhang, Y., Lo, D., Zhou, D., Chen, Q., & Hassan, A. E. (2022) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/3540250.3549148 · Cited by 2
Self-citationThomas, J. R., Nicolaescu, A., & Lichter, H. (2017) · RWTH Publications (RWTH Aachen) · Cited by 1
Software Architecture Optimization Methods: A Systematic Literature Review
Aleti, A., Bühnová, B., Grunske, L., et al. (2012) · Zurich Open Repository and Archive (University of Zurich) · doi:10.5167/uzh-72268 · Cited by 1
Software Architecture Review: The State of Practice
Babar, M. A., & Gorton, I. (2009) · Computer · doi:10.1109/mc.2009.233 · cited 1×
“” The widespread use of experience-based reasoning aligns with findings in the literature (e.g., [7]).”
Background
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 21
“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 3
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
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.

