{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,7,22]],"date-time":"2026-07-22T22:29:05Z","timestamp":1784759345891,"version":"3.55.0"},"reference-count":59,"publisher":"Springer Science and Business Media LLC","issue":"2","license":[{"start":{"date-parts":[[2023,11,16]],"date-time":"2023-11-16T00:00:00Z","timestamp":1700092800000},"content-version":"tdm","delay-in-days":0,"URL":"https:\/\/creativecommons.org\/licenses\/by\/4.0"},{"start":{"date-parts":[[2023,11,16]],"date-time":"2023-11-16T00:00:00Z","timestamp":1700092800000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/creativecommons.org\/licenses\/by\/4.0"}],"funder":[{"DOI":"10.13039\/501100018948","name":"Infotech Oulu","doi-asserted-by":"publisher","award":["298020"],"award-info":[{"award-number":["298020"]}],"id":[{"id":"10.13039\/501100018948","id-type":"DOI","asserted-by":"publisher"}]},{"DOI":"10.13039\/501100002341","name":"Academy of Finland","doi-asserted-by":"publisher","award":["328058"],"award-info":[{"award-number":["328058"]}],"id":[{"id":"10.13039\/501100002341","id-type":"DOI","asserted-by":"publisher"}]},{"DOI":"10.13039\/501100006196","name":"University of Oulu","doi-asserted-by":"crossref","id":[{"id":"10.13039\/501100006196","id-type":"DOI","asserted-by":"crossref"}]}],"content-domain":{"domain":["link.springer.com"],"crossmark-restriction":false},"short-container-title":["Software Qual J"],"published-print":{"date-parts":[[2024,6]]},"abstract":"<jats:title>Abstract<\/jats:title><jats:p>Technical debt presents sub-optimal choices made in development, which are beneficial in the short term but not in the long run. Consciously admitted debt, which is marked with a keyword, e.g., TODO, is called keyword-labeled self-admitted technical debt (KL-SATD). KL-SATD can lead to adverse effects in software development, e.g., to a rise in complexity within the developed software. We investigated the relationship between KL-SATD from source code comments and reports from the highly popular industrial program analysis tool SonarQube. The goal was to find which SonarQube metrics and issues are related to KL-SATD introduction and removal and how many KL-SATD in the context of an issue addresses that issue. We performed a study with 33 software repositories. We analyzed the changes in SonarQube reports (sqale index, reliability and security remediation metrics, and SonarQube issues) and the relationship to KL-SATD addition and removal with mixed model analysis. We manually annotated a sample to investigate how many KL-SATD comments are in the context of SonarQube issues and how many address them directly. KL-SATD is associated with a reduction in code maintainability measured with SonarQube\u2019s sqale index. KL-SATD removal is associated with an increase in code maintainability (sqale index) and reliability measured with SonarQube\u2019s reliability remediation effort. The introduction and removal of KL-SATD have a predominantly relationship with code smells, and not with vulnerabilities and bugs. Manual annotation revealed that 36% of KL-SATD comments are in the context of a SonarQube issue, but only 15% of the comment address an issue. This means that despite of statistical relationship between KL-SATD comments and SonarQube reports there is a large set of KL-SATD comments that are in areas that Sonarqube reports as clean or free of maintainability issues. KL-SATD introduction and removal are connected mainly to code smells, connecting them to maintainability rather than reliability or security. This is reinforced by the relationship with the sqale index, as well as the dominance of code smells in SonarQube issues. Many KL-SATD issues have characteristics going beyond static analysis tools and require future studies extending the capabilities of the current tools. As KL-SATD comments and SonarQube reports appear to have limited overlap, it suggests that they are complementary and both are needed for getting a comprehensive view coverage of code maintainability. The study also presents rules violations developers should be aware of regarding KL-SATD introduction and removal.\n<\/jats:p>","DOI":"10.1007\/s11219-023-09655-z","type":"journal-article","created":{"date-parts":[[2023,11,16]],"date-time":"2023-11-16T08:02:30Z","timestamp":1700121750000},"page":"391-429","update-policy":"https:\/\/doi.org\/10.1007\/springer_crossmark_policy","source":"Crossref","is-referenced-by-count":12,"title":["Keyword-labeled self-admitted technical debt and static code analysis have significant relationship but limited overlap"],"prefix":"10.1007","volume":"32","author":[{"given":"Leevi","family":"Rantala","sequence":"first","affiliation":[],"role":[{"vocabulary":"crossref","role":"author"}]},{"given":"Mika","family":"M\u00e4ntyl\u00e4","sequence":"additional","affiliation":[],"role":[{"vocabulary":"crossref","role":"author"}]},{"given":"Valentina","family":"Lenarduzzi","sequence":"additional","affiliation":[],"role":[{"vocabulary":"crossref","role":"author"}]}],"member":"297","published-online":{"date-parts":[[2023,11,16]]},"reference":[{"key":"9655_CR1","doi-asserted-by":"crossref","unstructured":"Akaike, H. (1998). Information theory and an extension of the maximum likelihood principle. In Selected papers of Hirotugu Akaike, (pp. 199\u2013213). Springer.","DOI":"10.1007\/978-1-4612-1694-0_15"},{"issue":"1","key":"9655_CR2","doi-asserted-by":"publisher","first-page":"66","DOI":"10.1109\/MS.2016.13","volume":"33","author":"P Avgeriou","year":"2016","unstructured":"Avgeriou, P., Kruchten, P., Nord, R. L., Ozkaya, I., & Seaman, C. (2016a). Reducing friction in software development. IEEE Software, 33(1), 66\u201373.","journal-title":"IEEE Software"},{"issue":"4","key":"9655_CR3","first-page":"110","volume":"6","author":"P Avgeriou","year":"2016","unstructured":"Avgeriou, P., Kruchten, P., Ozkaya, I., & Seaman, C. (2016b). Managing technical debt in software engineering (Dagstuhl Seminar 16162). Dagstuhl Reports, 6(4), 110\u2013138.","journal-title":"Dagstuhl Reports"},{"key":"9655_CR4","doi-asserted-by":"crossref","unstructured":"Avgeriou, P., Taibi, D., Ampatzoglou, A., Arcelli\u00a0Fontana, F., Besker, T., Chatzigeorgiou, ... & Tsintzira, A. (2021). An overview and comparison of technical debt measurement tools. IEEE Software.","DOI":"10.1109\/MS.2020.3024958"},{"key":"9655_CR5","doi-asserted-by":"crossref","unstructured":"Baldassarre, M.\u00a0T., Lenarduzzi, V., Romano, S., & Saarim\u00e4ki, N. (2020). On the diffuseness of technical debt items and accuracy of remediation time when using SonarQube. Information and Software Technology, 128.","DOI":"10.1016\/j.infsof.2020.106377"},{"key":"9655_CR6","unstructured":"Basili, V.\u00a0R., Caldiera, G., & Rombach, H.\u00a0D. (1994). The goal question metric approach. Encyclopedia of Software Engineering."},{"key":"9655_CR7","doi-asserted-by":"publisher","first-page":"1278","DOI":"10.1109\/TSE.1987.232881","volume":"12","author":"VR Basili","year":"1987","unstructured":"Basili, V. R., & Selby, R. W. (1987). Comparing the effectiveness of software testing strategies. IEEE transactions on software engineering, 12, 1278\u20131296.","journal-title":"IEEE transactions on software engineering"},{"key":"9655_CR8","doi-asserted-by":"crossref","unstructured":"Bavota, G. & Russo, B. (2016). A large-scale empirical study on self-admitted technical debt. In 13th International Conference on Mining Software Repositories, (pp. 315\u2013326).","DOI":"10.1145\/2901739.2901742"},{"key":"9655_CR9","doi-asserted-by":"crossref","unstructured":"Besker, T., Martini, A., Lokuge, R.\u00a0E., Blincoe, K., & Bosch, J. (2018). Embracing technical debt, from a startup company perspective. In IEEE International Conference on Software Maintenance and Evolution (ICSME), (pp. 415\u2013425).","DOI":"10.1109\/ICSME.2018.00051"},{"issue":"1","key":"9655_CR10","doi-asserted-by":"publisher","first-page":"135","DOI":"10.1109\/2.962984","volume":"34","author":"B Boehm","year":"2001","unstructured":"Boehm, B., & Basili, V. R. (2001). Defect reduction top 10 list. Computer, 34(1), 135\u2013137.","journal-title":"Computer"},{"issue":"2","key":"9655_CR11","doi-asserted-by":"publisher","first-page":"29","DOI":"10.1145\/157710.157715","volume":"4","author":"W Cunningham","year":"1992","unstructured":"Cunningham, W. (1992). The WyCash portfolio management system. SIGPLAN OOPS Messenger, 4(2), 29\u201330.","journal-title":"SIGPLAN OOPS Messenger"},{"key":"9655_CR12","doi-asserted-by":"crossref","unstructured":"de\u00a0Freitas\u00a0Farias, M.\u00a0A., de\u00a0Mendon\u00e7a\u00a0Neto, M.\u00a0G., da\u00a0Silva, A.\u00a0B., & Sp\u00ednola, R.\u00a0O. (2015). A contextualized vocabulary model for identifying technical debt on code comments. In 7th International Workshop on Managing Technical Debt (MTD), (pp. 25\u201332).","DOI":"10.1109\/MTD.2015.7332621"},{"key":"9655_CR13","doi-asserted-by":"crossref","unstructured":"de\u00a0Lima, B.\u00a0S., Garcia, R.\u00a0E., & Eler, D.\u00a0M. (2022). Toward prioritization of self-admitted technical debt: An approach to support decision to payment. Software Quality Journal, (pp. 1\u201327).","DOI":"10.1007\/s11219-021-09578-7"},{"key":"9655_CR14","doi-asserted-by":"crossref","unstructured":"Digkas, G., Lungu, M., Avgeriou, P., Chatzigeorgiou, A., & Ampatzoglou, A. (2018). How do developers fix issues and pay back technical debt in the apache ecosystem?","DOI":"10.1109\/SANER.2018.8330205"},{"key":"9655_CR15","doi-asserted-by":"crossref","unstructured":"Digkas, G., M.\u00a0Lungu, A.\u00a0C., & Avgeriou, P. (2017). The evolution of technical debt in the apache ecosystem. In European Conference on Software Architecture (ECSA2017), (pp. 51\u201366). Springer.","DOI":"10.1007\/978-3-319-65831-5_4"},{"key":"9655_CR16","doi-asserted-by":"crossref","unstructured":"Falessi, D., Russo, B., & Mullen, K. (2017). What if i had no smells? In International Symposium on Empirical Software Engineering and Measurement (ESEM2017).","DOI":"10.1109\/ESEM.2017.14"},{"issue":"3","key":"9655_CR17","first-page":"41","volume":"3","author":"SU Farooq","year":"2013","unstructured":"Farooq, S. U., & Quadri, S. (2013). Empirical evaluation of software testing techniques-need, issues and mitigation. Software engineering: an international Journal, 3(3), 41\u201351.","journal-title":"Software engineering: an international Journal"},{"key":"9655_CR18","first-page":"1","volume-title":"Identification of self-admitted technical debt using enhanced feature selection based on word embedding","author":"J Flisar","year":"2019","unstructured":"Flisar, J., & Podgorelec, V. (2019). Identification of self-admitted technical debt using enhanced feature selection based on word embedding (pp. 1\u20131). PP: IEEE Access."},{"issue":"1","key":"9655_CR19","doi-asserted-by":"publisher","first-page":"159","DOI":"10.1007\/s10664-014-9351-7","volume":"21","author":"Y Guo","year":"2016","unstructured":"Guo, Y., Sp\u00ednola, R., & Seaman, C. (2016). Exploring the costs of technical debt management - A case study. Empirical Software Engineering, 21(1), 159\u2013182.","journal-title":"Empirical Software Engineering"},{"key":"9655_CR20","doi-asserted-by":"publisher","first-page":"418","DOI":"10.1007\/s10664-017-9522-4","volume":"23","author":"Q Huang","year":"2017","unstructured":"Huang, Q., Shihab, E., Xia, X., Lo, D., & Li, S. (2017). Identifying self-admitted technical debt in open source projects using text mining. Empirical Software Engineering, 23, 418\u2013451.","journal-title":"Empirical Software Engineering"},{"key":"9655_CR21","doi-asserted-by":"crossref","unstructured":"Iammarino, M., Zampetti, F., Aversano, L., & Di\u00a0Penta, M. (2021). An empirical study on the co-occurrence between refactoring actions and self-admitted technical debt removal. Journal of Systems and Software, 110976.","DOI":"10.1016\/j.jss.2021.110976"},{"key":"9655_CR22","doi-asserted-by":"crossref","unstructured":"Johnson, B., Song, Y., Murphy-Hill, E., & Bowdidge, R. (2013). Why don\u2019t software developers use static analysis tools to find bugs? In 2013 35th International Conference on Software Engineering (ICSE), (pp. 672\u2013681).","DOI":"10.1109\/ICSE.2013.6606613"},{"key":"9655_CR23","unstructured":"Kenneth\u00a0P., B. & David\u00a0R., A. (2002). Model selection and multimodel inference : A practical information-theoretic approach., (Vol. 2nd ed). Springer."},{"key":"9655_CR24","doi-asserted-by":"crossref","unstructured":"Lehman, M.\u00a0M. (1996). Laws of software evolution revisited. In European Workshop on Software Process Technology, (pp. 108\u2013124).","DOI":"10.1007\/BFb0017737"},{"key":"9655_CR25","doi-asserted-by":"crossref","unstructured":"Lenarduzzi, V., Besker, T., Taibi, D., Martini, A., & Arcelli Fontana, F. (2021). A systematic literature review on technical debt prioritization: Strategies, processes, factors, and tools. Journal of Systems and Software, 171.","DOI":"10.1016\/j.jss.2020.110827"},{"key":"9655_CR26","doi-asserted-by":"crossref","unstructured":"Lenarduzzi, V., Lomio, F., Huttunen, H., & Taibi, D. (2020). Are sonarqube rules inducing bugs? In 27th International Conference on Software Analysis, Evolution and Reengineering (SANER2020), (pp. 501\u2013511).","DOI":"10.1109\/SANER48275.2020.9054821"},{"key":"9655_CR27","doi-asserted-by":"crossref","unstructured":"Lenarduzzi, V., Martini, A., Taibi, D., & Tamburri, D.\u00a0A. (2019a). Towards surgically-precise technical debt estimation: Early results and research roadmap. In International Workshop on Machine Learning Techniques for Software Quality Evaluation (MaLTeSQuE\u201919), (pp. 37\u201342).","DOI":"10.1145\/3340482.3342747"},{"key":"9655_CR28","doi-asserted-by":"crossref","unstructured":"Lenarduzzi, V., Saarim\u00e4ki, N., & Taibi, D. (2019b). The technical debt dataset. In 15th conference on PREdictive Models and data analycs In Software Engineering, PROMISE \u201919, (pp. 2 \u2013 11).","DOI":"10.1145\/3345629.3345630"},{"key":"9655_CR29","doi-asserted-by":"crossref","unstructured":"Lenarduzzi, V., Saarim\u00e4ki, N., & Taibi, D. (2020). Some sonarqube issues have a significant but small effect on faults and changes. a large-scale empirical study. Journal of Systems and Software, 170.","DOI":"10.1016\/j.jss.2020.110750"},{"key":"9655_CR30","doi-asserted-by":"crossref","unstructured":"Leon, D. & Podgurski, A. (2003). A comparison of coverage-based and distribution-based techniques for filtering and prioritizing test cases. In 14th International Symposium on Software Reliability Engineering, 2003. ISSRE 2003., (pp. 442\u2013453).","DOI":"10.1109\/ISSRE.2003.1251065"},{"key":"9655_CR31","doi-asserted-by":"crossref","unstructured":"Li, Y., Soliman, M., & Avgeriou, P. (2020). Identification and remediation of self-admitted technical debt in issue trackers. In 46th Euromicro Conference on Software Engineering and Advanced Applications (SEAA), (pp. 495\u2013503).","DOI":"10.1109\/SEAA51224.2020.00083"},{"key":"9655_CR32","doi-asserted-by":"publisher","first-page":"193","DOI":"10.1016\/j.jss.2014.12.027","volume":"101","author":"Z Li","year":"2015","unstructured":"Li, Z., Avgeriou, P., & Liang, P. (2015). A systematic mapping study on technical debt and its management. Journal of Systems and Software, 101, 193\u2013220.","journal-title":"Journal of Systems and Software"},{"key":"9655_CR33","doi-asserted-by":"crossref","unstructured":"Liu, Z., Huang, Q., Xia, X., Shihab, E., Lo, D., & Li, S. (2018). Satd detector: A text-mining-based self-admitted technical debt detection tool. In 40th International Conference on Software Engineering: Companion (ICSE-Companion), (pp. 9\u201312).","DOI":"10.1145\/3183440.3183478"},{"key":"9655_CR34","doi-asserted-by":"crossref","unstructured":"Maldonado, E. d.\u00a0S., Abdalkareem, R., Shihab, E., & Serebrenik, A. (2017). An empirical study on the removal of self-admitted technical debt. In International Conference on Software Maintenance and Evolution (ICSME), (pp. 238\u2013248).","DOI":"10.1109\/ICSME.2017.8"},{"key":"9655_CR35","doi-asserted-by":"crossref","unstructured":"Maldonado, E. D.\u00a0S. & Shihab, E. (2015). Detecting and quantifying different types of self-admitted technical debt. In 7th International Workshop on Managing Technical Debt (MTD), (pp. 9\u201315).","DOI":"10.1109\/MTD.2015.7332619"},{"issue":"6","key":"9655_CR36","doi-asserted-by":"publisher","first-page":"986","DOI":"10.1016\/j.infsof.2012.12.004","volume":"55","author":"MV M\u00e4ntyl\u00e4","year":"2013","unstructured":"M\u00e4ntyl\u00e4, M. V., & Itkonen, J. (2013). More testers-the effect of crowd size and time restriction in software testing. Information and Software Technology, 55(6), 986\u20131003.","journal-title":"Information and Software Technology"},{"key":"9655_CR37","doi-asserted-by":"publisher","first-page":"237","DOI":"10.1016\/j.infsof.2015.07.005","volume":"67","author":"A Martini","year":"2015","unstructured":"Martini, A., Bosch, J., & Chaudron, M. (2015). Investigating architectural technical debt accumulation and refactoring over time: A multiple-case study. Information and Software Technology, 67, 237\u2013253.","journal-title":"Information and Software Technology"},{"issue":"4","key":"9655_CR38","doi-asserted-by":"publisher","first-page":"340","DOI":"10.1109\/TSE.2005.49","volume":"31","author":"TJ Ostrand","year":"2005","unstructured":"Ostrand, T. J., Weyuker, E. J., & Bell, R. M. (2005). Predicting the location and number of faults in large software systems. IEEE Transactions on Software Engineering, 31(4), 340\u2013355.","journal-title":"IEEE Transactions on Software Engineering"},{"issue":"3","key":"9655_CR39","doi-asserted-by":"publisher","first-page":"1188","DOI":"10.1007\/s10664-017-9535-z","volume":"23","author":"F Palomba","year":"2018","unstructured":"Palomba, F., Bavota, G., Penta, M. D., Fasano, F., Oliveto, R., & Lucia, A. D. (2018). On the diffuseness and the impact on maintainability of code smells: A large scale empirical investigation. Empirical Software Engineering, 23(3), 1188\u20131221.","journal-title":"Empirical Software Engineering"},{"key":"9655_CR40","volume-title":"Qualitative evaluation and research methods","author":"M Patton","year":"2002","unstructured":"Patton, M. (2002). Qualitative evaluation and research methods. Newbury Park: Sage."},{"key":"9655_CR41","doi-asserted-by":"crossref","unstructured":"Potdar, A. & Shihab, E. (2014). An exploratory study on self-admitted technical debt. In IEEE International Conference on Software Maintenance and Evolution, (pp. 91\u2013100).","DOI":"10.1109\/ICSME.2014.31"},{"key":"9655_CR42","doi-asserted-by":"crossref","unstructured":"Rantala, L., M\u00e4ntyl\u00e4, M., & Lo, D. (2020). Prevalence, contents and automatic detection of kl-satd. In 2020 46th Euromicro Conference on Software Engineering and Advanced Applications (SEAA).","DOI":"10.1109\/SEAA51224.2020.00069"},{"issue":"3","key":"9655_CR43","doi-asserted-by":"publisher","first-page":"1","DOI":"10.1145\/3324916","volume":"28","author":"X Ren","year":"2019","unstructured":"Ren, X., Xing, Z., Xia, X., Lo, D., Wang, X., & Grundy, J. (2019). Neural network-based detection of self-admitted technical debt: From performance to explainability. ACM Transactions on Software Engineering and Methodology (TOSEM), 28(3), 1\u201345.","journal-title":"ACM Transactions on Software Engineering and Methodology (TOSEM)"},{"issue":"2","key":"9655_CR44","doi-asserted-by":"publisher","first-page":"131","DOI":"10.1007\/s10664-008-9102-8","volume":"14","author":"P Runeson","year":"2009","unstructured":"Runeson, P., & H\u00f6st, M. (2009). Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering, 14(2), 131\u2013164.","journal-title":"Empirical Software Engineering"},{"key":"9655_CR45","doi-asserted-by":"publisher","DOI":"10.1109\/SEAA.2019.00055","volume-title":"On the accuracy of sonarqube technical debt remediation time","author":"N Saarimaki","year":"2019","unstructured":"Saarimaki, N., Baldassarre, M. T., Lenarduzzi, V., & Romano, S. (2019). On the accuracy of sonarqube technical debt remediation time. In SEAA Euromicro."},{"key":"9655_CR46","doi-asserted-by":"crossref","unstructured":"Saarim\u00e4ki, N., Lenarduzzi, V., & Taibi, D. (2019). On the diffuseness of code technical debt in java projects of the apache ecosystem. In Second International Conference on Technical Debt (TechDebt \u201919), (pp. 98\u2013107).","DOI":"10.1109\/TechDebt.2019.00028"},{"key":"9655_CR47","doi-asserted-by":"publisher","first-page":"25","DOI":"10.1016\/B978-0-12-385512-1.00002-5","volume":"82","author":"C Seaman","year":"2011","unstructured":"Seaman, C., & Guo, Y. (2011). Measuring and monitoring technical debt. Advances in Computers, 82, 25\u201346.","journal-title":"Advances in Computers"},{"key":"9655_CR48","doi-asserted-by":"publisher","first-page":"70","DOI":"10.1016\/j.jss.2019.02.056","volume":"152","author":"G Sierra","year":"2019","unstructured":"Sierra, G., Shihab, E., & Kamei, Y. (2019). A survey of self-admitted technical debt. Journal of Systems and Software, 152, 70\u201382.","journal-title":"Journal of Systems and Software"},{"key":"9655_CR49","doi-asserted-by":"crossref","unstructured":"Tan, J., Feitosa, D., & Avgeriou, P. (2020). An empirical study on self-fixed technical debt. In Proceedings of the 3rd International Conference on Technical Debt, (pp. 11\u201320).","DOI":"10.1145\/3387906.3388621"},{"key":"9655_CR50","doi-asserted-by":"crossref","unstructured":"Tollin, I., Arcelli Fontana, F., Zanoni, M., & Roveda, R. (2017). Change prediction through coding rules violations. In 21st International Conference on Evaluation and Assessment in Software Engineering (EASE\u201917), (pp. 61\u201364).","DOI":"10.1145\/3084226.3084282"},{"key":"9655_CR51","doi-asserted-by":"publisher","first-page":"44","DOI":"10.1016\/j.jss.2018.03.053","volume":"143","author":"H Valdivia-Garcia","year":"2018","unstructured":"Valdivia-Garcia, H., Shihab, E., & Nagappan, M. (2018). Characterizing and predicting blocking bugs in open source projects. Journal of Systems and Software, 143, 44\u201358.","journal-title":"Journal of Systems and Software"},{"key":"9655_CR52","doi-asserted-by":"crossref","unstructured":"Vassallo, C., Panichella, S., Palomba, F., Proksch, S., Gall, H.\u00a0C., & Zaidman, A. (2019). How developers engage with static analysis tools in different contexts. Empirical Software Engineering.","DOI":"10.1007\/s10664-019-09750-5"},{"key":"9655_CR53","doi-asserted-by":"crossref","unstructured":"Wagner, S., J\u00fcrjens, J., Koller, C., & Trischberger, P. (2005). Comparing bug finding tools with reviews and tests. In IFIP International Conference on Testing of Communicating Systems, (pp. 40\u201355).","DOI":"10.1007\/11430230_4"},{"key":"9655_CR54","doi-asserted-by":"crossref","unstructured":"Wehaibi, S., Shihab, E., & Guerrouj, L. (2016). Examining the impact of self-admitted technical debt on software quality. In 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER), 1, 179\u2013188.","DOI":"10.1109\/SANER.2016.72"},{"key":"9655_CR55","doi-asserted-by":"crossref","unstructured":"Xavier, L., Ferreira, F., Brito, R., & Valente, M.\u00a0T. (2020). Beyond the code: Mining self-admitted technical debt in issue tracker systems. In 17th International Conference on Mining Software Repositories, (pp. 137\u2013146).","DOI":"10.1145\/3379597.3387459"},{"key":"9655_CR56","doi-asserted-by":"crossref","unstructured":"Zampetti, F., Noiseux, C., Antoniol, G., Khomh, F., & Di\u00a0Penta, M. (2017). Recommending when design technical debt should be self-admitted. In 2017 IEEE International Conference on Software Maintenance and Evolution (ICSME), (pp. 216\u2013226).","DOI":"10.1109\/ICSME.2017.44"},{"key":"9655_CR57","doi-asserted-by":"crossref","unstructured":"Zampetti, F., Serebrenik, A., & Di Penta, M. (2018). Was self-admitted technical debt removal a real removal? an in-depth perspective. In 15th International Conference on Mining Software Repositories (MSR), (pp. 526\u2013536).","DOI":"10.1145\/3196398.3196423"},{"key":"9655_CR58","doi-asserted-by":"crossref","unstructured":"Zampetti, F., Serebrenik, A., & Di Penta, M. (2020). Automatically learning patterns for self-admitted technical debt removal. In 27th International Conference on Software Analysis, Evolution and Reengineering (SANER), (pp. 355\u2013366).","DOI":"10.1109\/SANER48275.2020.9054868"},{"key":"9655_CR59","doi-asserted-by":"crossref","unstructured":"Zazworka, N., Sp\u00ednola, R.\u00a0O., Vetro\u2019, A., Shull, F., & Seaman, C. (2013). A case study on effectively identifying technical debt. In International Conference on Evaluation and Assessment in Software Engineering (EASE \u201913), (pp. 42\u201347).","DOI":"10.1145\/2460999.2461005"}],"container-title":["Software Quality Journal"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/link.springer.com\/content\/pdf\/10.1007\/s11219-023-09655-z.pdf","content-type":"application\/pdf","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/link.springer.com\/article\/10.1007\/s11219-023-09655-z\/fulltext.html","content-type":"text\/html","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/link.springer.com\/content\/pdf\/10.1007\/s11219-023-09655-z.pdf","content-type":"application\/pdf","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2024,6,20]],"date-time":"2024-06-20T09:13:23Z","timestamp":1718874803000},"score":1,"resource":{"primary":{"URL":"https:\/\/link.springer.com\/10.1007\/s11219-023-09655-z"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2023,11,16]]},"references-count":59,"journal-issue":{"issue":"2","published-print":{"date-parts":[[2024,6]]}},"alternative-id":["9655"],"URL":"https:\/\/doi.org\/10.1007\/s11219-023-09655-z","relation":{},"ISSN":["0963-9314","1573-1367"],"issn-type":[{"value":"0963-9314","type":"print"},{"value":"1573-1367","type":"electronic"}],"subject":[],"published":{"date-parts":[[2023,11,16]]},"assertion":[{"value":"18 October 2023","order":1,"name":"accepted","label":"Accepted","group":{"name":"ArticleHistory","label":"Article History"}},{"value":"16 November 2023","order":2,"name":"first_online","label":"First Online","group":{"name":"ArticleHistory","label":"Article History"}},{"order":1,"name":"Ethics","group":{"name":"EthicsHeading","label":"Declarations"}},{"value":"The authors declare no competing interests.","order":2,"name":"Ethics","group":{"name":"EthicsHeading","label":"Competing interests"}}]}}