Understanding automated and human-based technical debt identification approaches-a two-phase study

Thumbnail Image

Files

Understanding automated and humanbased technical debt identification.pdf (2.49 MB)

Links to Files

https://link.springer.com/article/10.1186/s13173-019-0087-5

Permanent Link

https://doi.org/10.1186/s13173-019-0087-5
 http://hdl.handle.net/11603/15981

Collections

UMBC Information Systems Department
UMBC Faculty Collection

Author/Creator

Author/Creator ORCID

Date

2019-06-08

Type of Work

journal articles
Text

Department

Program

Citation of Original Publication

Spínola, Rodrigo O. ; Zazworka, Nico; Vetro, Antonio ; Shull, Forrest; Seaman, Carolyn; Understanding automated and human-based technical debt identification approaches-a two-phase study; Journal of the Brazilian Computer Society 25,5 ; https://doi.org/10.1186/s13173-019-0087-5

Rights

This item is likely protected under Title 17 of the U.S. Copyright Law. Unless on a Creative Commons license, for uses protected by Copyright Law, contact the copyright holder or the author.
Attribution 2.0 Generic (CC BY 2.0)

Subjects

Technical debt
Automated technical debt identification
Human-based technical debt identification

Abstract

Context The technical debt (TD) concept inspires the development of useful methods and tools that support TD identification and management. However, there is a lack of evidence on how different TD identification tools could be complementary and, also, how human-based identification compares with them. Objective To understand how to effectively elicit TD from humans, to investigate several types of tools for TD identification, and to understand the developers’ point of view about TD indicators and items reported by tools. Method We asked developers to identify TD items from a real software project. We also collected the output of three tools to automatically identify TD and compared the results in terms of their locations in the source code. Then, we collected developers’ opinions on the identification process through a focus group. Results Aggregation seems to be an appropriate way to combine TD reported by developers. The tools used cannot help in identifying many important TD types, so involving humans is necessary. Developers reported that the tools would help them to identify TD faster or more accurately and that project priorities and current development activities are important to be considered together, along with the values of principal and interest, when deciding to pay off a debt. Conclusion This work contributes to the TD landscape, which depicts an understanding between different TD types and how they are best discovered.