Gabriele Rotoloni

Gabriele Rotoloni

Auto-generated profile, based on publicly available information

Gabriele Rotoloni

Università degli Studi dell’Insubria, Italy

Research Focus & Metrics

Academic Career Length

4Years (2023-Present)

(Calculated once Scilit publication data is synced: current year − year of first publication + 1)

Representative Publications

View All Publications


2 December 2023
Verified
Book Chapter
Closed access
PDF file
LLLuigi Lavazza
Luigi Lavazza
SMSandro Morasca
Sandro Morasca
GRGabriele Rotoloni
Gabriele Rotoloni

27 April 2025 in arXiv
Verified
Preprint
Open access
PDF file
LLLuigi Lavazza
Luigi Lavazza
GRGabriele Rotoloni
Gabriele Rotoloni
SMSandro Morasca
Sandro Morasca
Background. Effort-aware metrics (EAMs) are widely used to evaluate the effectiveness of software defect prediction models, while accounting for the effort needed to analyze the software modules that are estimated defective. The usual underlying assumption is that this effort is proportional to the modules' size measured in LOC. However, the research on module analysis (including code understanding, inspection, testing, etc.) suggests that module analysis effort may be better correlated to code attributes other than size. Aim. We investigate whether assuming that module analysis effort is proportional to other code metrics than LOC leads to different evaluations. Method. We show mathematically that the choice of the code measure used as the module effort driver crucially influences the resulting evaluations. To illustrate the practical consequences of this, we carried out a demonstrative empirical study, in which the same model was evaluated via EAMs, assuming that effort is proportional to either McCabe's complexity or LOC. Results. The empirical study showed that EAMs depend on the underlying effort model, and can give quite different indications when effort is modeled differently. It is also apparent that the extent of these differences varies widely. Conclusions. Researchers and practitioners should be aware that the reliability of the indications provided by EAMs depend on the nature of the underlying effort model. The EAMs used until now appear to be actually size-aware, rather than effort-aware: when analysis effort does not depend on size, these EAMs can be misleading.

20 June 2026 in ACM Transactions on Software Engineering and Methodology
Verified
Journal Article
Open access
LLLuigi Lavazza
Luigi Lavazza
SMSandro Morasca
Sandro Morasca
GRGabriele Rotoloni
Gabriele Rotoloni
Background : Effort-aware metrics (EAMs) have the merit of including software analysis effort in the evaluation of software defect prediction (SDP) models. Yet, almost all EAMs concentrate only on the effectiveness of SDP models, i.e., how well they identify actually defective modules. Instead, EAMs ignore the efficiency of SDP models, i.e., their ability to not classify non-defective modules as defective. Efficiency is important because modules incorrectly classified as defective will undergo useless analysis, thus causing effort waste, and also undermining the confidence of developers in the usefulness of SDP models. Aim : We aim to represent the performance of SDP models along several dimensions, while taking into consideration the effort needed for module analysis. Specifically, we look for indicators that account for both effectiveness and efficiency. Method : We extend Receiver Operating Characteristic (ROC) curves to explicitly represent analysis effort. To this end, we add iso-effort lines to the ROC space and iso-effort points to ROC curves. Iso-effort curves and points show where each point of the ROC space (corresponding to a classifier) is positioned with respect to analysis effort. We also define effort-aware metrics based on the area under the ROC curve. Results : We show that the proposed effort-aware ROC curves support systematic and complete evaluation of SDP models’ performance. Specifically, we show that a single effort-aware ROC curve provides the same information as multiple traditional EAMs. In addition, effort-aware ROC curves provide evaluation-oriented information in a coherent and visually intuitive way. We also show the practical application of the proposed techniques to well-known software defectiveness datasets. Conclusions : The proposed technique can effectively support both researchers and developers in comparing and selecting SDP models.