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

Abstract

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.

Identification and Refactoring of Design Problems in Software Systems

“…There is a possibility that the metric-based detection rules of JSpIRIT might have identified false-positive smells. We mitigated this threat by applying the same metric thresholds proposed by Lanza and Marinescu (Lanza and Marinescu 2006), which had been also used in previous work (Vidal, Marcos and Díaz Pace 2014b, Guimaraes et al 2018.…”