Abstract

Programmers tend to leave deficient, non-permanent bypass and demented codes that require rework in software development and such phenomenon is referred to as Self-admitted Technical Debt (SATD). Previous studies have shown that SATD is common in released software artefacts and is mostly found in source code comments. SATD negatively affects software project development and incurs high maintenance overheads. In this study, the authors seek to identify plausible approaches utilized by researchers to identify and detect SATD prone tasks in software artefacts prior to release to the market or clients. Accordingly, a literature review is carried out to perform this investigative study. Two popular approaches were found for identifying and detecting SATD prone tasks from a pool of SATD related research papers, namely manual and text mining approach.

References

• S. Mensah, J. Keung, J. Svajlenko, K. E. Bennin, and Q. Mi, “On the value of a prioritization scheme for resolving Self-admitted technical debt,” J. Syst. Softw., vol. 135, pp. 37–54, 2018, doi: 10.1016/j.jss.2017.09.026.
• A. Potdar and E. Shihab, “An exploratory study on self-admitted technical debt,” Proc. - 30th Int. Conf. Softw. Maint. Evol. ICSME 2014, pp. 91–100, 2014, doi: 10.1109/ICSME.2014.31.
• G. Bavota and B. Russo, “A large-scale empirical study on self-admitted technical debt,” Proc. - 13th Work. Conf. Min. Softw. Repos. MSR 2016, pp. 315–326, 2016, doi: 10.1145/2901739.2901742.
• W. Cunningham, “The WyCash Portfolio Management System,” 1992.
• S. Wehaibi, E. Shihab, and L. Guerrouj, “Examining the impact of self-admitted technical debt on software quality,” 2016 IEEE 23rd Int. Conf. Softw. Anal. Evol. Reengineering, SANER 2016, vol. 1, pp. 179–188, 2016, doi: 10.1109/SANER.2016.72.
• Q. Huang, E. Shihab, X. Xia, D. Lo, and S. Li, “Identifying self-admitted technical debt in open source projects using text mining,” Empir. Softw. Eng., vol. 23, no. 1, pp. 418–451, 2018, doi: 10.1007/s10664-017-9522-4.
• C. Fern and J. Garbajosa, “A Framework to Aid in Decision Making for Technical Debt Management,” pp. 69–76, 2015.
• E. D. S. Maldonado and E. Shihab, “Detecting and quantifying different types of self-admitted technical Debt,” 2015 IEEE 7th Int. Work. Manag. Tech. Debt, MTD 2015 - Proc., pp. 9–15, 2015, doi: 10.1109/MTD.2015.7332619.
• S. Maldonado, E. Shihab, and N. Tsantalis, “Using nutural language to Automatically Detect Self-Admitted Technical Debt,” vol. 43, no. 11, pp. 1044–1062, 2017.
• J. M. Corbin and A. Strauss, “Grounded theory research: Procedures, canons, and evaluative criteria,” Qual. Sociol., vol. 13, no. 1, pp. 3–21, 1990, doi: 10.1007/BF00988593.
• M. C. O. Silva, M. T. Valente, and R. Terra, “Does technical debt lead to the rejection of pull requests?,” SBSI 2016 - 12th Brazilian Symp. Inf. Syst. Inf. Syst. Cloud Comput. Era, Proc., no. ii, pp. 248–254, 2016, doi: 10.5753/sbsi.2016.5969.
• F. Zampetti, A. Serebrenik, and M. Di Penta, “Was self-admitted technical debt removal a real removal?: An in-depth perspective,” Proc. - Int. Conf. Softw. Eng., pp. 526–536, 2018, doi: 10.1145/3196398.3196423.
• A. Martini and J. Bosch, “Towards Prioritizing Architecture Technical Debt : Information Needs of Architects and Product Owners,” pp. 422–429, 2015, doi: 10.1109/SEAA.2015.78.
• S. Akbarinasaji and A. Bener, “Adjusting the Balance Sheet by Appending Technical Debt,” Proc. - 2016 IEEE 8th Int. Work. Manag. Tech. Debt, MTD 2016, pp. 36–39, 2016, doi: 10.1109/MTD.2016.14.
• G. Sierra, A. Tahmid, E. Shihab, and N. Tsantalis, “Is Self-Admitted Technical Debt a Good Indicator of Architectural Divergences?,” SANER 2019 - Proc. 2019 IEEE 26th Int. Conf. Softw. Anal. Evol. Reengineering, pp. 534–543, 2019, doi: 10.1109/SANER.2019.8667999.
• M. Yan, X. Xia, E. Shihab, D. Lo, J. Yin, and X. Yang, “Automating Change-level Self-admitted Technical Debt Determination,” vol. 5589, no. c, pp. 1–18, 2018, doi: 10.1109/TSE.2018.2831232.
• B. Kitchenham, O. Pearl Brereton, D. Budgen, M. Turner, J. Bailey, and S. Linkman, “Systematic literature reviews in software engineering - A systematic literature review,” Inf. Softw. Technol., vol. 51, no. 1, pp. 7–15, 2009, doi: 10.1016/j.infsof.2008.09.009.
• B. Kitchenham and S. Charters, “Guidelines for performing Systematic Literature Reviews in SE,” pp. 1–44, 2007, doi: 10.1145/1134285.1134500.
• F. Sebastiani, “Machine Learning in Automated Text Categorization,” ACM Comput. Surv., vol. 34, no. 1, pp. 1–47, 2002, doi: 10.1145/505282.505283.
• D. Toruno, E. Çak, M. C. Ganiz, S. Akyoku, and M. Z. Gürbüz, “Analysis of Preprocessing Methods on Classification of Turkish Texts,” pp. 112–117, 2011.
• S. B. Kotsiantis, D. Kanellopoulos, and P. E. Pintelas, “Data Preprocessing for Supervised Leaning,” vol. 1, no. 2, pp. 111–117, 2006.
• X. Liu, “Full-Text Citation Analysis : A New Method to Enhance,” J. Am. Soc. Inf. Sci. Technol., vol. 64, no. July, pp. 1852–1863, 2013, doi: 10.1002/asi.
• G. Salton, “1988_Salton, G. and Buckley, C., 1988. Term-weighting approaches in automatic text retrieval._7896.pdf.” 1988.
• H. Sch, “Introduction to Information Retrieval IIR 8 : Evaluation & Result Summaries Recap Unranked evaluation Ranked evaluation,” Evaluation, 2008.
• M. Baena-garc, “TF-SIDF : Term Frequency , Sketched Inverse Document Frequency,” pp. 1044–1049, 2011.