On the Relevance of Code Anomalies for Identifying Architecture Degradation Symptoms

Macia, Isela; Arcoverde, Roberta; Garcia, Alessandro; Chávez, Christina; Staa, Arndt von

doi:10.1109/csmr.2012.35

Cited by 95 publications

(145 citation statements)

References 24 publications

Supporting

Mentioning

118

Contrasting

Unclassified

Order By: Relevance

“…Prior work (Macia, Garcia, Popescu, Garcia, Medvidovic & Staa 2012c) (Macia et al 2012b) (Macia 2013) has shown that each design problem is often realized by various code anomalies scattered in the program. These anomalies interact across the code structure in order to reify a single design problem in the program.…”

Section: Motivating Example and Problemmentioning

confidence: 99%

“…Sjoberg et al (Sjobert et al 2013) showed that single code anomalies were not related to maintenance effort. Macia et al (Macia et al 2012b) analyzed the relevance of code anomalies to identify design problems. This research revealed that none of the studied code anomalies was consistently a strong indicator of design problems.…”

Section: Studies On the Relation Of Code Anomalies And Design Problemsmentioning

confidence: 99%

“…However, recent studies showed that this assumption is too simplistic (Macia et al 2012b) (Oizumi, Garcia, Colanzi, Ferreira & Staa 2014a). In fact, each design problem, in general, is realized by various anomalous elements scattered in the implementation (Macia et al 2012b). In addition, a high proportion of individual code anomalies may not affect the system's design.…”

Section: Introductionmentioning

confidence: 99%

“…State-of-art techniques (Emden & Moonen 2002) (Ratzinger, Fischer & Gall 2005) (Wong, Cai, Kim & Dalton 2011) (Marinescu 2004) do not even reveal any form of relationship between code anomalies. A previous work has tried to partially classify a subset of possible relationships between code anomalies (Macia et al 2012b) (Macia, Arcoverde, Cirilo, Garcia & Staa 2012a). However, the proposed technique is not intended to explicitly support the synthetization of all relevant information for the identification and diagnosis of design problems.…”

Section: Introductionmentioning

confidence: 99%

“…However, the identification and understanding of design problems are not trivial tasks, as they often need to rely on source code analysis. Design documentation is rarely available or up-to-date (Macia, Arcoverde, Garcia, Chavez & Staa 2012b).…”

Section: Introductionmentioning

confidence: 99%

See 4 more Smart Citations

Synthesis of Code Anomalies: Revealing Design Problems in the Source Code

Oizumi¹

View full text Add to dashboard Cite

Section: Motivating Example and Problemmentioning

confidence: 99%

Section: Studies On the Relation Of Code Anomalies And Design Problemsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Synthesis of Code Anomalies: Revealing Design Problems in the Source Code

Oizumi¹

View full text Add to dashboard Cite

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

Exploring architecture blueprints for prioritizing critical code anomalies: Experiences and tool support

et al. 2018

View full text Add to dashboard Cite

Summary The manifestation of code anomalies in software systems often indicates symptoms of architecture degradation. Several approaches have been proposed to detect such anomalies in the source code. However, most of them fail to assist developers in prioritizing anomalies harmful to the software architecture of a system. This article presents an investigation on how developers, when supported by architecture blueprints, are able to prioritize architecturally relevant code anomalies. First, we performed a controlled experiment where participants explored both blueprints and source code to reveal architecturally relevant code anomalies. Although the use of blueprints has the potential to improve code anomaly prioritization, the participants often made several mistakes. We found these mistakes might occur because developers miss relationships between implementation and blueprint elements when they prioritize anomalies in an ad hoc manner. Furthermore, the time spent on the prioritization process was considerably high. Aiming to improve the accuracy and effectiveness of the process, we provided means to automate the prioritization process. In particular, we explored 3 prioritization criteria, which establish different ways of relating the blueprint elements with code anomalies. These criteria were implemented in the JSpIRIT tool. The approach was evaluated in the context of 2 applications with satisfactory precision results.

show abstract

On the Relevance of Code Anomalies for Identifying Architecture Degradation Symptoms

Cited by 95 publications

References 24 publications

Synthesis of Code Anomalies: Revealing Design Problems in the Source Code

Synthesis of Code Anomalies: Revealing Design Problems in the Source Code

Understanding software architecture erosion: A systematic mapping study

Exploring architecture blueprints for prioritizing critical code anomalies: Experiences and tool support

Contact Info

Product

Resources

About