Understanding Software Architecture Erosion: A Systematic Mapping Study
Ruiyin Li, Peng Liang, Mohamed Soliman, Paris Avgeriou

TL;DR
This systematic mapping study comprehensively analyzes architecture erosion (AEr), its causes, consequences, detection methods, and countermeasures, highlighting the importance of addressing both technical and non-technical factors to improve software sustainability.
Contribution
It provides a comprehensive overview of AEr research, categorizes detection and mitigation approaches, and emphasizes the need for more empirical industrial studies.
Findings
AEr affects software quality and evolution
Both technical and non-technical causes are important
Various tools and approaches exist for detection and mitigation
Abstract
Architecture erosion (AEr) can adversely affect software development and has received significant attention in the last decade. However, there is an absence of a comprehensive understanding of the state of research about the reasons and consequences of AEr, and the countermeasures to address AEr. This work aims at systematically investigating, identifying, and analyzing the reasons, consequences, and ways of detecting and handling AEr. With 73 studies included, the main results are as follows: (1) AEr manifests not only through architectural violations and structural issues but also causing problems in software quality and during software evolution; (2) non-technical reasons that cause AEr should receive the same attention as technical reasons, and practitioners should raise awareness of the grave consequences of AEr, thereby taking actions to tackle AEr-related issues; (3) a spectrum…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
