{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,11,10]],"date-time":"2026-11-10T10:45:11Z","timestamp":1794307511418,"version":"4.9.0"},"reference-count":25,"publisher":"MDPI AG","issue":"15","license":[{"start":{"date-parts":[[2022,7,26]],"date-time":"2022-07-26T00:00:00Z","timestamp":1658793600000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/creativecommons.org\/licenses\/by\/4.0\/"}],"funder":[{"DOI":"10.13039\/501100004329","name":"Slovenian Research Agency","doi-asserted-by":"publisher","award":["P2-0057"],"award-info":[{"award-number":["P2-0057"]}],"id":[{"id":"10.13039\/501100004329","id-type":"DOI","asserted-by":"publisher"}]}],"content-domain":{"domain":[],"crossmark-restriction":false},"short-container-title":["Applied Sciences"],"abstract":"<jats:p>Technical debt is a well understood and used concept in IT development. The metaphor, rooted in the financial world, captures the amount of work that development teams owe to a product. Every time developers take a shortcut within development, the technical debt accumulates. Technical debt identification can be accomplished via manual reporting on the technical debt items, which is called self-admitted technical debt. Several specialised methods and tools have also emerged that promise to measure the technical debt. Based on experience in the community, the impression emerged that the measured technical debt is of a significantly different amount than the self-admitted debt. In this context, we decided to perform empirical research on the possible gap between the two. We investigated 14 production-grade software products while determining the amount of accumulated technical debt via (a) a self-admitting procedure and (b) measuring the debt. The outcomes show clearly the significant difference in the technical debt reported by the two methods. We urge development and quality-assurance teams not to rely on technical debt measurement alone. The tools demonstrated their strength in identifying low-level code technical debt items that violate a set of predefined rules. However, developers should have additional insight into violations, based on the interconnected source code and its relation to the domain and higher-level design decisions.<\/jats:p>","DOI":"10.3390\/app12157482","type":"journal-article","created":{"date-parts":[[2022,7,26]],"date-time":"2022-07-26T22:03:42Z","timestamp":1658873022000},"page":"7482","update-policy":"https:\/\/doi.org\/10.3390\/mdpi_crossmark_policy","source":"Crossref","is-referenced-by-count":4,"title":["The Gap between the Admitted and the Measured Technical Debt: An Empirical Study"],"prefix":"10.3390","volume":"12","author":[{"ORCID":"https:\/\/orcid.org\/0000-0001-5477-4747","authenticated-orcid":false,"given":"Luka","family":"Pavli\u010d","sequence":"first","affiliation":[{"name":"Faculty of Electrical Engineering and Computer Science, University of Maribor, Koro\u0161ka Cesta 46, 2000 Maribor, Slovenia"}],"role":[{"vocabulary":"crossref","role":"author"}]},{"ORCID":"https:\/\/orcid.org\/0000-0002-4973-4844","authenticated-orcid":false,"given":"Tilen","family":"Hli\u0161","sequence":"additional","affiliation":[{"name":"Faculty of Electrical Engineering and Computer Science, University of Maribor, Koro\u0161ka Cesta 46, 2000 Maribor, Slovenia"}],"role":[{"vocabulary":"crossref","role":"author"}]},{"ORCID":"https:\/\/orcid.org\/0000-0002-1094-0085","authenticated-orcid":false,"given":"Marjan","family":"Heri\u010dko","sequence":"additional","affiliation":[{"name":"Faculty of Electrical Engineering and Computer Science, University of Maribor, Koro\u0161ka Cesta 46, 2000 Maribor, Slovenia"}],"role":[{"vocabulary":"crossref","role":"author"}]},{"ORCID":"https:\/\/orcid.org\/0000-0001-6518-5876","authenticated-orcid":false,"given":"Tina","family":"Berani\u010d","sequence":"additional","affiliation":[{"name":"Faculty of Electrical Engineering and Computer Science, University of Maribor, Koro\u0161ka Cesta 46, 2000 Maribor, Slovenia"}],"role":[{"vocabulary":"crossref","role":"author"}]}],"member":"1968","published-online":{"date-parts":[[2022,7,26]]},"reference":[{"key":"ref_1","doi-asserted-by":"crossref","unstructured":"Cunningham, W. (1992, January 5\u201310). The WyCash Portfolio Management System. Proceedings of the OOPSLA \u201992\u2014Experience Report, Vancouver, BC, Canada.","DOI":"10.1145\/157709.157715"},{"key":"ref_2","doi-asserted-by":"crossref","unstructured":"Potdar, A., and Shihab, E. (October, January 29). An Exploratory Study on Self-Admitted Technical Debt. Proceedings of the 30th International Conference on Software Maintenance and Evolution, ICSME 2014, Victoria, BC, Canada.","DOI":"10.1109\/ICSME.2014.31"},{"key":"ref_3","doi-asserted-by":"crossref","unstructured":"Li, Y., Soliman, M., and Avgeriou, P. (2022). Automatic Identification of Self-Admitted Technical Debt from Different Sources. arXiv.","DOI":"10.1109\/TechDebt59074.2023.00008"},{"key":"ref_4","doi-asserted-by":"crossref","first-page":"131","DOI":"10.1007\/s10664-021-10031-3","article-title":"Self-Admitted Technical Debt Practices: A Comparison Between Industry and Open-Source","volume":"26","author":"Zampetti","year":"2021","journal-title":"Empir. Softw. Eng."},{"key":"ref_5","doi-asserted-by":"crossref","unstructured":"Khomyakov, I., Makhmutov, Z., Mirgalimova, R., and Sillitti, A. (2020, January 5\u20137). An Analysis of Automated Technical Debt Measurement. Proceedings of the Enterprise Information Systems, online.","DOI":"10.1007\/978-3-030-40783-4_12"},{"key":"ref_6","unstructured":"Pfeiffer, R.H., and Lungu, M. (2022). Technical Debt and Maintainability: How do tools measure it?. arXiv."},{"key":"ref_7","unstructured":"Papapetrou, P. (2022, May 20). How to Calculate Technical Debt and Express It Clearly. Available online: http:\/\/thinkapps.com\/blog\/development\/technical-debt-calculation\/."},{"key":"ref_8","doi-asserted-by":"crossref","unstructured":"Fern\u00e1ndez-S\u00e1nchez, C., Garbajosa, J., Vidal, C., and Yag\u00fce, A. (2015, January 16). An Analysis of Techniques and Methods for Technical Debt Management: A Reflection from the Architecture Perspective. Proceedings of the 2015 IEEE\/ACM 2nd International Workshop on Software Architecture and Metrics, Florence, Italy.","DOI":"10.1109\/SAM.2015.11"},{"key":"ref_9","doi-asserted-by":"crossref","first-page":"22","DOI":"10.1016\/j.jss.2016.10.018","article-title":"Identification and analysis of the elements required to manage technical debt by means of a systematic mapping study","volume":"124","author":"Garbajosa","year":"2017","journal-title":"J. Syst. Softw."},{"key":"ref_10","first-page":"1","article-title":"Identifying Self-Admitted Technical Debts with Jitterbug: A Two-Step Approach","volume":"48","author":"Yu","year":"2020","journal-title":"IEEE Trans. Softw. Eng."},{"key":"ref_11","doi-asserted-by":"crossref","unstructured":"Kosti, M.V., Ampatzoglou, A., Chatzigeorgiou, A., Pallas, G., Stamelos, I., and Angelis, L. (September, January 30). Technical Debt Principal Assessment Through Structural Metrics. Proceedings of the 2017 43rd Euromicro Conference on Software Engineering and Advanced Applications (SEAA), Vienna, Austria.","DOI":"10.1109\/SEAA.2017.59"},{"key":"ref_12","doi-asserted-by":"crossref","unstructured":"Kontsevoi, B., Soroka, E., and Terekhov, S. (2019, January 26). TETRA, as a set of Techniques and Tools for Calculating Technical Debt Principal and Interest. Proceedings of the 2019 IEEE\/ACM International Conference on Technical Debt (TechDebt), Montreal, QC, Canada.","DOI":"10.1109\/TechDebt.2019.00021"},{"key":"ref_13","doi-asserted-by":"crossref","unstructured":"Ludwig, J., Cline, D., and Novstrup, A. (2020, January 7\u201314). A Case Study Using CBR-Insight to Visualize Source Code Quality. Proceedings of the 2020 IEEE Aerospace Conference, Big Sky, MT, USA.","DOI":"10.1109\/AERO47225.2020.9172526"},{"key":"ref_14","doi-asserted-by":"crossref","unstructured":"Wiese, M., Riebisch, M., and Schwarze, J. (2021, January 19\u201321). Preventing Technical Debt by Technical Debt Aware Project Management. Proceedings of the 2021 IEEE\/ACM International Conference on Technical Debt (TechDebt), Madrid, Spain.","DOI":"10.1109\/TechDebt52882.2021.00018"},{"key":"ref_15","doi-asserted-by":"crossref","unstructured":"Tsoukalas, D., Siavvas, M., Jankovic, M., Kehagias, D., Chatzigeorgiou, A., and Tzovaras, D. (2018, January 25\u201327). Methods and Tools for TD Estimation and Forecasting: A State-of-the-art Survey. Proceedings of the 2018 International Conference on Intelligent Systems (IS), Funchal, Portugal.","DOI":"10.1109\/IS.2018.8710521"},{"key":"ref_16","doi-asserted-by":"crossref","unstructured":"Lenarduzzi, V., Martini, A., Taibi, D., and Tamburri, D.A. (2019, January 27). Towards Surgically-Precise Technical Debt Estimation: Early Results and Research Roadmap. Proceedings of the 3rd ACM SIGSOFT International Workshop on Machine Learning Techniques for Software Quality Evaluation, Tallinn, Estonia.","DOI":"10.1145\/3340482.3342747"},{"key":"ref_17","unstructured":"Stre\u010dansk\u00fd, P., Chren, S., and Rossi, B. (April, January 30). Comparing Maintainability Index, SIG Method, and SQALE for Technical Debt Identification. Proceedings of the 35th Annual ACM Symposium on Applied Computing, Brno, Czech Republic."},{"key":"ref_18","doi-asserted-by":"crossref","unstructured":"Tan, J., Feitosa, D., and Avgeriou, P. (2020, January 28\u201330). An Empirical Study on Self-Fixed Technical Debt. Proceedings of the 3rd International Conference on Technical Debt, Seoul, Korea.","DOI":"10.1145\/3387906.3388621"},{"key":"ref_19","doi-asserted-by":"crossref","unstructured":"Aversano, L., Iammarino, M., Carapella, M., Del Vecchio, A., and Nardi, L. (2020). On the Relationship between Self-Admitted Technical Debt Removals and Technical Debt Measures. Algorithms, 13.","DOI":"10.3390\/a13070168"},{"key":"ref_20","doi-asserted-by":"crossref","unstructured":"Letouzey, J.L. (2012, January 5). The SQALE method for evaluating Technical Debt. Proceedings of the 2012 Third International Workshop on Managing Technical Debt (MTD), Zurich, Switzerland.","DOI":"10.1109\/MTD.2012.6225997"},{"key":"ref_21","unstructured":"Letouzey, J.-L. (2022, May 20). The SQALE Method for Managing Technical Debt\u2014Definition Document. Available online: http:\/\/www.sqale.org\/wp-content\/uploads\/2016\/08\/SQALE-Method-EN-V1-1.pdf."},{"key":"ref_22","unstructured":"(2022, May 20). SonarSource. SonarQube Docs 9.3. Available online: https:\/\/docs.sonarqube.org\/."},{"key":"ref_23","unstructured":"(2022, May 20). SonarSource. SonarQube. Available online: https:\/\/www.sonarqube.org\/."},{"key":"ref_24","unstructured":"(2022, May 20). Vector. Squore. Available online: https:\/\/www.vector.com\/int\/en\/products\/products-a-z\/software\/squore\/."},{"key":"ref_25","doi-asserted-by":"crossref","first-page":"5","DOI":"10.1186\/s13173-019-0087-5","article-title":"Understanding automated and human-based technical debt identification approaches-a two-phase study","volume":"25","author":"Zazworka","year":"2019","journal-title":"J. Braz. Comput. Soc."}],"container-title":["Applied Sciences"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/www.mdpi.com\/2076-3417\/12\/15\/7482\/pdf","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,10,10]],"date-time":"2025-10-10T23:56:31Z","timestamp":1760140591000},"score":1,"resource":{"primary":{"URL":"https:\/\/www.mdpi.com\/2076-3417\/12\/15\/7482"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2022,7,26]]},"references-count":25,"journal-issue":{"issue":"15","published-online":{"date-parts":[[2022,8]]}},"alternative-id":["app12157482"],"URL":"https:\/\/doi.org\/10.3390\/app12157482","relation":{},"ISSN":["2076-3417"],"issn-type":[{"value":"2076-3417","type":"electronic"}],"subject":[],"published":{"date-parts":[[2022,7,26]]}}}