Technical debt is a metaphor describing the situation that long-term benefits (e.g., maintainability and evolvability of software) are traded for short-term goals. When technical debt is admitted explicitly by developers in software artifacts (e.g., code comments or issue tracking systems), it is termed as Self-Admitted Technical Debt or SATD. Technical debt could be admitted in different sources, such as source code comments, issue tracking systems, pull requests, and commit messages. However, there is no approach proposed for identifying SATD from different sources. Thus, in this paper, we propose an approach for automatically identifying SATD from different sources (i.e., source code comments, issue trackers, commit messages, and pull requests).
翻译：技术债务是一种比喻,用来描述长期利益(例如软件的可维持性和可发展性)为短期目标进行交易的情况;当软件文物开发商明确承认技术债务(例如代码评论或问题跟踪系统)时,技术债务被称为自发技术债务或SATD。技术债务可以来自不同来源,例如源代码评论、问题跟踪系统、拉动请求和发送信息等不同来源;然而,没有提出从不同来源确定SATD的方法。因此,我们在本文件中建议采用一种办法,自动确定不同来源的SATD(例如源代码评论、发布跟踪器、发送信息、发送信息、发送请求)的SATD。
相关内容
微信扫码咨询专知VIP会员