Definition(s):
It refers to issues associated with a build process that make this process harder. Some examples of Build Debt items are: files of build containing code source that does not add value to this task and software products and manual build; and “bad” dependencies.
Source(s):
- Li, Zengyang, Paris Avgeriou, and Peng Liang. “A systematic mapping study on technical debt and its management. Syst. Softw., 101 (2015), pp. 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.
- BenIdris, Ammar, Dzielski. “Investigate, identify, and estimate the technical debt: a systematic mapping study.” Int. J. of Softw. Eng. Appl (IJSEA), Vol. 9 (5), (2018), pp.1-14.
- Dalla, L. O. F. B. “Systematic Mapping on a metaphorical issue of Technical Debt framework.” International Journal of Health and Pharmaceutical Research E-ISSN 2545-5737 P-ISSN 2695-2165, Vol 5. (3), (2020).
- Jeronimo Junior, Helvio, and Guilherme Horta Travassos. “Consolidating a Common Perspective on Technical Debt and its Management Through a Tertiary Study.” Information and Software Technology (2022): 106964.