Detecting and Quantifying Different Types of Self-Admitted Technical Debt
October 2015 • Presentation
This presentation examines source-code comments to detect and categorize types of technical debt and proposes four simple filtering heuristics to detect them.
Software Engineering Institute
This presentation was part of the Seventh International Workshop on Managing Technical Debt, held in conjunction with the 31th International Conference on Software Maintenance and Evolution (ICSME 2015).
Technical debt is a term that has been used to express non-optimal solutions during the development of software projects. These non-optimal solutions are often shortcuts that allow the project to move faster in the short term, at the cost of increased maintenance in the future. To help alleviate the impact of technical debt, a number of studies focused on the detection of technical debt. More recently, our work showed that one possible source to detect technical debt is using source code comments, also referred to as self-admitted technical debt. However, what types of technical debt can be detected using source code comments remains as an open question. Therefore, we examine code comments to determine the different types of technical debt. First, we propose four simple filtering heuristics to eliminate comments that are not likely to contain technical debt. Second, we read through more than 33K comments, and we find that self-admitted technical debt can be classified into five main types: design debt, defect debt, documentation debt, requirement debt, and test debt. The most common type of self-admitted technical debt is design debt, making up between 42% to 84% of the classified comments. Last, we make the classified data set of more than 33K comments publicly available for the community as a way to encourage future research and the evolution of the technical debt landscape.