论文标题
在发行跟踪器中识别和补救自我吸引的技术债务
Identification and Remediation of Self-Admitted Technical Debt in Issue Trackers
论文作者
论文摘要
技术债务是指采取快捷方式以实现短期目标，这可能会长期影响软件维护。开发人员在源代码评论中接受了对技术债务的关注越来越多（称为自我吸引的技术债务或SATD）。但是在问题跟踪器中的SATD相对尚未探索。我们进行了一个案例研究，在该案例研究中，我们从两个开源项目（即Hadoop和Camel）手动检查了500期，其中包含152个SATD项目。我们发现：1）在问题，建筑，代码，缺陷，设计，文档，要求和测试债务中确定了八种类型的技术债务； 2）开发人员在三个不同的时间点中确定问题的技术债务，其创作者确定了一小部分； 3）大多数技术债务是还清的，4）主要由确定或创造的技术债务； 5）中间时间和平均偿还技术债务的时间分别为872.3和25.0小时。
Technical debt refers to taking shortcuts to achieve short-term goals, which might negatively influence software maintenance in the long-term. There is increasing attention on technical debt that is admitted by developers in source code comments (termed as self-admitted technical debt or SATD). But SATD in issue trackers is relatively unexplored. We performed a case study, where we manually examined 500 issues from two open source projects (i.e. Hadoop and Camel), which contained 152 SATD items. We found that: 1) eight types of technical debt are identified in issues, namely architecture, build, code, defect, design, documentation, requirement, and test debt; 2) developers identify technical debt in issues in three different points in time, and a small part is identified by its creators; 3) the majority of technical debt is paid off, 4) mostly by those who identified it or created it; 5) the median time and average time to repay technical debt are 872.3 and 25.0 hours respectively.
