On Architectural Decay Prediction and Detection in Real-Time Software Systems

Fellah, Aziz; Bandi, Ajay

doi:10.29007/l86k

Cited by 5 publications

(5 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For example, AEr could be also caused by technological evolution (e.g., [S7]), including operating systems, hardware, and programming languages. 42 Technical debt is a metaphor reflecting technical compromises that can yield short-term benefits but may hurt the long-term goal of a software system. 34 For example, new products are hastily released to the market because of time pressure (e.g., [S66]).…”

Section: Lack Of Communication Between Stakeholders [S12][s25][s34][s47]mentioning

confidence: 99%

Understanding software architecture erosion: A systematic mapping study

Liang

Soliman

et al. 2022

J Software Evolu Process

View full text Add to dashboard Cite

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 of approaches, tools, and measures has been proposed and employed to detect and tackle AEr; and (4) three categories of difficulties and five categories of lessons learned on tackling AEr were identified. The results can provide researchers a comprehensive understanding of AEr and help practitioners handle AEr and improve the sustainability of their architecture. More empirical studies are required to investigate the practices of detecting and addressing AEr in industrial settings.

show abstract

Section: Lack Of Communication Between Stakeholders [S12][s25][s34][s47]mentioning

confidence: 99%

Understanding software architecture erosion: A systematic mapping study

Liang

Soliman

et al. 2022

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…Architectural smells are one of the causes of architectural decay, and technical debt [24], [25]. Finding architectural smells and anti-patters can thus aid the software's long-term viability.…”

Section: A Architecture Smell/anti-pattern Detectionmentioning

confidence: 99%

Using Microservice Telemetry Data for System Dynamic Analysis

Maruf¹,

Bakhtin²,

Černý³

et al. 2022

Preprint

View full text Add to dashboard Cite

Microservices bring various benefits to software systems. They also bring decentralization and lose coupling across self-contained system parts. Since these systems likely evolve in a decentralized manner, they need to be monitored to identify when possibly poorly designed extensions deteriorate the overall system quality. For monolith systems, such tasks have been commonly addressed through static analysis. However, given the decentralization and possible language diversity across microservices, static analysis tools are lacking. On the other hand, there are available tools commonly used by practitioners that offer centralized logging, tracing, and metric collection for microservices. In this paper, we assess the opportunity to combine current dynamic analysis tools with anomaly detection in the form of quality metrics and anti-patterns. We develop a tool prototype that we use to assess a large microservice system benchmark demonstrating the feasibility and potential of such an approach.

show abstract

“…Uncontrollable evolution process (e.g., [S58]) might increase the risk of AEr and give rise to software failure. For example, AEr could be also caused by technological evolution (e.g., [S7]), including operating systems, hardware, and programming languages [42].…”

Section: Immobilitymentioning

confidence: 99%

Understanding Software Architecture Erosion: A Systematic Mapping Study

Li,

Liang,

Soliman

et al. 2021

Preprint

View full text Add to dashboard Cite

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

show abstract

On Architectural Decay Prediction and Detection in Real-Time Software Systems

Cited by 5 publications

References 21 publications

Understanding software architecture erosion: A systematic mapping study

Understanding software architecture erosion: A systematic mapping study

Using Microservice Telemetry Data for System Dynamic Analysis

Understanding Software Architecture Erosion: A Systematic Mapping Study

Contact Info

Product

Resources

About