A Framework for Conditional Statement Technical Debt Identification and Description
Abdulaziz Alhefdhi (1), Hoa Khanh Dam (1), Yusuf Sulistyo Nugroho (2),, Hideaki Hata (3), Takashi Ishio (4), Aditya Ghose (1) ((1) University of, Wollongong, (2) Universitas Muhammadiyah Surakarta, (3) Shinshu University,, (4) Nara Institute of Science, Technology)

TL;DR
This paper introduces a framework called SATDID that detects and describes hidden technical debt in conditional statements, especially when such debt isn't explicitly acknowledged in code comments, improving maintainability.
Contribution
The study presents a novel framework for identifying and automatically generating descriptive comments for hidden technical debt in code, focusing on conditional statements.
Findings
Achieved over 21% improvement in Precision
Achieved over 59% improvement in Recall
Generated comments with acceptable levels of understandability
Abstract
Technical Debt occurs when development teams favour short-term operability over long-term stability. Since this places software maintainability at risk, technical debt requires early attention to avoid paying for accumulated interest. Most of the existing work focuses on detecting technical debt using code comments, known as Self-Admitted Technical Debt (SATD). However, there are many cases where technical debt instances are not explicitly acknowledged but deeply hidden in the code. In this paper, we propose a framework that caters for the absence of SATD comments in code. Our Self-Admitted Technical Debt Identification and Description (SATDID) framework determines if technical debt should be self-admitted for an input code fragment. If that is the case, SATDID will automatically generate the appropriate descriptive SATD comment that can be attached with the code. While our approach is…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
