Towards Surgically-Precise Technical Debt Estimation: Early Results and Research Roadmap

Valentina Lenarduzzi, Antonio Martini, Davide Taibi, Damian Andrew Tamburri

Research output: Chapter in Book/Report/Conference proceedingConference contributionScientificpeer-review

12 Citations (Scopus)
17 Downloads (Pure)

Abstract

The concept of technical debt has been explored from many perspectives but its precise estimation is still under heavy empirical and experimental inquiry. We aim to understand whether, by harnessing approximate, data-driven, machine-learning approaches it is possible to improve the current techniques for technical debt estimation, as represented by a top industry quality analysis tool such as SonarQube. For the sake of simplicity, we focus on relatively simple regression modelling techniques and apply them to modelling the additional project cost connected to the sub-optimal conditions existing in the projects under study. Our results shows that current techniques can be improved towards a more precise estimation of technical debt and the case study shows promising results towards the identification of more accurate estimation of technical debt.
Original languageEnglish
Title of host publicationTowards Surgically-Precise Technical Debt Estimation: Early Results and Research Roadmap
PublisherACM
Pages37-42
ISBN (Electronic)978-1-4503-6855-1
DOIs
Publication statusPublished - 27 Aug 2019
Publication typeA4 Article in conference proceedings
EventACM SIGSOFT International Workshop on Machine Learning Techniques for Software Quality Evaluation -
Duration: 1 Jan 2000 → …

Conference

ConferenceACM SIGSOFT International Workshop on Machine Learning Techniques for Software Quality Evaluation
Period1/01/00 → …

Keywords

  • Technical Debt
  • Machine Learning
  • Empirical Study

Publication forum classification

  • Publication forum level 1

Fingerprint

Dive into the research topics of 'Towards Surgically-Precise Technical Debt Estimation: Early Results and Research Roadmap'. Together they form a unique fingerprint.

Cite this