Key points are not available for this paper at this time.
Technical Debt (TD) 1 term in software systems was introduced over two decades ago and remains a critical concern in software development. It has the potential to evolve into a liability that necessitates refactoring or rewriting code over time. Regardless of its significance, there exists a notable gap in literature concerning a comprehensive list of technical debt indicators. The purpose of this study is to re-evaluate existing TD categorization and extend TD indicators and offer a complete and validated TD Type and TD Indicator list. In this study, we adopted a qualitative research approach and used mapping and expert opinion techniques as the research approach. The number of TD indicators extracted from existing formal literature was 60 which was extended to 92 by reviewing gray literature. This list was then subjected to the expert review, and with their feedback, grew by an additional 21%. Consequently, we present 10 distinct TD types, accompanied by 120 TD indicators that would aid in TD identification, resolution and minimizing the risks and costs associated with technical debt in software development.
Çağlayan et al. (Mon,) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: