Definition(s):
TD types could be classified two main perspectives, and without overlap between them : TD Types from Software Development Phases (and TD Types from their Way of Occurrence (Jeronimo Junior and Travassos, 2022).
The first perspective considers the software lifecycle moment or software artifacts in which TD occurs. According to this perspective TD items can be classified as Archicteture Debt, Build Debt, Code Debt, Design Debt, Documentation Debt, Requirement Debt, Test Debt, and Versioning Debt (Li et al., 2015; Alves et al., 2016).
The other view considers the TD occurrence context, which TD items can be classified as Intentional TD (Prudent TD or Reckless TD) and Unintentional TD (McConnell, 2007; Fowler, 2009).
Source(s):
- McConnell, S.: Technical Debt – 10x Software Development. In: Construx. Available at: http://www.construx.com/10x_Software_Development/Technical_Debt/.
- Fowler, M.: TechnicalDebtQuadrant. In: MartinFowler.com. First published in 2009. Available at: https://martinfowler.com/bliki/TechnicalDebtQuadrant.html.
- Li, Zengyang, Paris Avgeriou, and Peng Liang. “A systematic mapping study on technical debt and its management.” Journal of Systems and Software 101 (2015): 193-220.
- Alves, Nicolli SR, et al. “Identification and management of technical debt: A systematic mapping study.” Inform. Softw. Technol., 70 (2016), pp. 100-121.
- Junior, Helvio Jeronimo, and Guilherme Horta Travassos. “Consolidating a Common Perspective on Technical Debt and its Management Through a Tertiary Study.” Information and Software Technology (2022): 106964.