Proceeding of the Faculty of technical Sciences, Novi Sad

Information engineering

Vol. 41 No. 04 (2026): Proceedings of the Faculty of Technical Sciences

Identification and Analysis of Technical Debt in Appointment Scheduling Software

  • Mилица Окиљевић
DOI:
https://doi.org/10.24867/
Submitted
March 30, 2026
Published
2026-04-21

Abstract

Technical debt is a metaphor that describes making compromises during software development to speed up short-term progress, which later leads to extra costs for maintenance and improvements. This concept includes not only coding but also project planning, delivery deadlines, and functionality. The aim of this paper is to explain the basics and categorization of technical debt, show its impact on software development, and analyze its occurrence in a real appointment scheduling software system. The results show that the most common types of technical debt are architectural, design, and defect debt, while changing requirements and time pressure are key factors behind their appearance.

References

  1. [1] W. Cunningham, "The WyCash Portfolio Management System," ACM SIGPLAN OOPS Messenger, vol. 4, no. 2, pp. 29–30, 1992.
  2. [2] N. S. Alves, T. S. Mendes, M. G. de Mendonça, R. O. Spínola, F. Shull, and C. Seaman, "Identification and Management of Technical Debt: A Systematic Mapping Study," Information and Software Technology, vol. 70, pp. 100–121, 2016.
  3. [3] C. Seaman, Y. Guo, N. Zazworka, F. Shull, C. Izurieta, and A. Vetrò, "Towards an Ontology of Terms on Technical Debt," in Proceedings of the IEEE International Workshop on Managing Technical Debt (MTD), 2014.
  4. [4] M. Fowler, “Technical Debt Quadrant,” Bliki [Blog], 2009. [Online]. Доступно: http://www.martinfowler.com/bliki/TechnicalDebtQuadrant.html (приступљено 10.10.2025.)
  5. [5] S. McConnell, Managing Technical Debt, Construx Software Builders, Inc., White Paper, 2008. [Online]. Доступно: https://www.construx.com/uploadedfiles/resources/whitepapers/Managing%20Technical%20Debt.pdf (приступљено 10.10.2025.)
  6. [6] V. Lenarduzzi, T. Besker, D. Taibi, A. Martini, and F. Arcelli Fontana, "A Systematic Literature Review on Technical Debt Prioritization: Strategies, Processes, Factors, and Tools," Journal of Systems and Software, vol. 171, p. 110827, 2021.
  7. [7] D. Koulla Moulla, E. Mnkandla, H. Oumarou, and T. Fehlmann, "Technical Debt Measurement: An Exploratory Literature Review," CEUR Workshop Proceedings, vol. 3852, pp. 1–14, 2024.
  8. [8] A. Melo, R. Fagundes, V. Lenarduzzi, and W. Santos, "Identification and Measurement of Technical Debt Requirements in Software Development: A Systematic Literature Review," arXiv preprint arXiv:2105.14232, 2021.
  9. [9] J. Frattini, D. Fucci, D. Mendez, R. Spinola, V. Mandic, N. Tausan, M. O. Ahmad, and J. Gonzalez-Huerta, "An Initial Theory to Understand and Manage Requirements Engineering Debt in Practice," arXiv preprint arXiv:2211.06189, 2022.