mlsanityData to 7 Oct 2026

The impact of using biased performance metrics on software defect prediction research

arXiv 2103.10201 ↗First posted 18 Mar 2021cs.SE cs.LGcited by 4

Not on the map. Why?

Abstract (arXiv)

Context: Software engineering researchers have undertaken many experiments investigating the potential of software defect prediction algorithms. Unfortunately, some widely used performance metrics are known to be problematic, most notably F1, but nevertheless F1 is widely used. Objective: To investigate the potential impact of using F1 on the validity of this large body of research. Method: We undertook a systematic review to locate relevant experiments and then extract all pairwise comparisons of defect prediction performance using F1 and the un-biased Matthews correlation coefficient (MCC). Results: We found a total of 38 primary studies. These contain 12,471 pairs of results. Of these, 21.95% changed direction when the MCC metric is used instead of the biased F1 metric. Unfortunately, we also found evidence suggesting that F1 remains widely used in software defect prediction research. Conclusions: We reiterate the concerns of statisticians that the F1 is a problematic metric outside of an information retrieval context, since we are concerned about both classes (defect-prone and not defect-prone units). This inappropriate usage has led to a substantial number (more than one fifth) of erroneous (in terms of direction) results. Therefore we urge researchers to (i) use an unbiased metric and (ii) publish detailed results including confusion matrices such that alternative analyses become possible.

Key facts. Cited by 4 papers in the map (data through 7 Oct 2026). Builds on 8 of its 90 references that are in the map. First posted on arXiv 18 Mar 2021.

Builds on

8 of 90 references.

References · 8

  1. 2020Evaluation: from precision, recall and F-measure to ROC, informedness, markedness and correlationcited by 420
  2. 2017Guidelines for including grey literature and conducting multivocal literature reviews in software engineeringcited by 38
  3. 2020Assessing Software Defection Prediction Performance: Why Using the Matthews Correlation Coefficient Matterscited by 8
  4. 2017Correction of "A Comparative Study to Benchmark Cross-project Defect Prediction Approaches"cited by 4
  5. 2019Are SonarQube Rules Inducing Bugs?cited by 4
  6. 2019A Systematic Review of Unsupervised Learning Techniques for Software Defect Predictioncited by 4
  7. 2019The Prevalence of Errors in Machine Learning Experimentscited by 3
  8. 2019On the costs and profit of software defect predictioncited by 1

Built on by

Cited by year

Citing papers per year: 2021: 2; 2022: 0; 2023: 1; 2024: 0; 2025: 1.

4 papers.