Identifying Self-Admitted Technical Debts with Jitterbug: A Two-step Approach
Not on the map. Why?
Abstract (arXiv)
Keeping track of and managing Self-Admitted Technical Debts (SATDs) are important to maintaining a healthy software project. This requires much time and effort from human experts to identify the SATDs manually. The current automated solutions do not have satisfactory precision and recall in identifying SATDs to fully automate the process. To solve the above problems, we propose a two-step framework called Jitterbug for identifying SATDs. Jitterbug first identifies the "easy to find" SATDs automatically with close to 100% precision using a novel pattern recognition technique. Subsequently, machine learning techniques are applied to assist human experts in manually identifying the remaining "hard to find" SATDs with reduced human effort. Our simulation studies on ten software projects show that Jitterbug can identify SATDs more efficiently (with less human effort) than the prior state-of-the-art methods.
Key facts. Cited by 10 papers in the map (data through 14 Oct 2026). First posted on arXiv 25 Feb 2020.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2021: 1; 2022: 3; 2023: 5; 2024: 0; 2025: 0; 2026: 1.
10 papers.
- 2021FRUGAL: Unlocking SSL for Software Analyticscited by 6
- 2022DebtFree: Minimizing Labeling Cost in Self-Admitted Technical Debt Identification using Semi-Supervised Learningcited by 5
- 2023Learning from Very Little Data: On the Value of Landscape Analysis for Predicting Software Project Healthcited by 3
- 2023PENTACET data -- 23 Million Contextual Code Comments and 250,000 SATD commentscited by 2
- 2023Self-Admitted Technical Debt Detection Approaches: A Decade Systematic Reviewcited by 2
- 2022How to Find Actionable Static Analysis Warnings: A Case Study with FindBugscited by 1
- 2022When Less is More: On the Value of "Co-training" for Semi-Supervised Software Defect Predictorscited by 1
- 2023Measuring Improvement of F1-Scores in Detection of Self-Admitted Technical Debtcited by 1
- 2023Less, but Stronger: On the Value of Strong Heuristics in Semi-supervised Learning for Software Analyticscited by 0
- 2026Is Model Instability just Noise to be Tolerated or a Property that can be Managed?cited by 0
- 2026Is Model Instability just Noise to be Tolerated or a Property that can be Managed?11 Jul 2026
- 2023Self-Admitted Technical Debt Detection Approaches: A Decade Systematic Review19 Dec 2023
- 2023PENTACET data -- 23 Million Contextual Code Comments and 250,000 SATD comments24 Mar 2023
- 2023Measuring Improvement of F1-Scores in Detection of Self-Admitted Technical Debt16 Mar 2023
- 2023Less, but Stronger: On the Value of Strong Heuristics in Semi-supervised Learning for Software Analytics3 Feb 2023
- 2023Learning from Very Little Data: On the Value of Landscape Analysis for Predicting Software Project Health16 Jan 2023
- 2022When Less is More: On the Value of "Co-training" for Semi-Supervised Software Defect Predictors10 Nov 2022
- 2022How to Find Actionable Static Analysis Warnings: A Case Study with FindBugs21 May 2022
- 2022DebtFree: Minimizing Labeling Cost in Self-Admitted Technical Debt Identification using Semi-Supervised Learning25 Jan 2022
- 2021FRUGAL: Unlocking SSL for Software Analytics22 Aug 2021