1. Effective Detection of Self- admitted Technical Debt Everton S. Maldonado Emad Shihab e_silvam@cse.concordia.ca eshihab@cse.concordia.ca Department of Computer Science and Software Engineering Concordia University 1

2. Research Goal 2 Thus far, comments have been used to identify self-admitted technical debt Our goal is to find other ways to identify self-admitted technical debt

3. Current limitations 3 We only have one source for self-admitted technical debt, which is using comments.

4. 4 Research Overview

5. Case study on Eclipse 5

6. Investigating Eclipse Bugs 6 For our next charts: -Creation is when the bug was opened in the bug tracker -Commit is when a code change was submitted to address the specific bug -Resolution is when the bug was marked as fixed

7. Number of days Number of bugs Corrective Changes 7 Average: 118.3111 Median : 35 Creation x Commit Number of bugs Number of days Commit x Resolution Number of bugs Number of days Creation x Resolution Average: 138.5111 Median : 15 Average: 257.3778 Median : 66

8. Advantages 8 -Developer input/confessions about the system are taken into consideration -Can bring more insights about how technical debt is introduced into the source code - A light-weight approach

9. Ongoing and Future Work 9 Manual examination of commits to identify patterns found in the commits messages that relate to self-admitted technical debt Classify types of technical debt and relate them to specific types of fixes or refactoring

10. 10

11. Effective Detection of Self- admitted Technical Debt Everton S. Maldonado e_silvam@cse.concordia.ca e_silvam@cse.concordia.ca Concordia University 11 Emad Shihab eshihab@cse.concordia.ca Concordia University

12. Thus far … 12 Recent work has shown that technical debt is prevalent and unavoidable Thus far, comments have been used to identify self-admitted technical debt

13. Our work 13 Find ways to effectively identify self-admitted technical debt is necessary Using: - Commit messages - Bug reports - Online discussions (e.g., StackOverflow)

14. Our work 14 We perform a case study on Eclipse …..to find out more… …come see my poster