On the Relationship between Self-Admitted Technical Debt Removals and Technical Debt Measures [PDF]
The technical debt (TD) in a software project refers to the adoption of an inadequate solution from its design to the source code. When developers admit the presence of technical debt in the source code, through comments or commit messages, it is called ...
Lerina Aversano +4 more
doaj +5 more sources
SATDBailiff-mining and tracking self-admitted technical debt [PDF]
Self-Admitted Technical Debt (SATD) is a metaphorical concept to describe the self-documented addition of technical debt to a software project in the form of source code comments. SATD can linger in projects and degrade source-code quality, but it can also be more visible than unintentionally added or undocumented technical debt.
Eman Abdullah Alomar +2 more
exaly +3 more sources
In-depth exploration of software defects and self-admitted technical debt through cutting-edge deep learning techniques. [PDF]
Most previous research focuses on finding Self-Admitted Technical Debt (SATD) or detecting bugs alone, rather to addressing the concurrent identification of both issues.
Sajid Ullah +5 more
doaj +3 more sources
Investigation on Self-Admitted Technical Debt in Open-Source Blockchain Projects
Technical debt refers to decisions made during the design and development of software that postpone the resolution of technical problems or the enhancement of the software’s features to a later date.
Andrea Pinna +3 more
doaj +3 more sources
Wait for it: identifying “On-Hold” self-admitted technical debt
AbstractSelf-admitted technical debt refers to situations where a software developer knows that their current implementation is not optimal and indicates this using a source code comment. In this work, we hypothesize that it is possible to develop automated techniques to understand a subset of these comments in more detail, and to propose tool support ...
Rungroj Maipradit +2 more
exaly +4 more sources
The Gap between the Admitted and the Measured Technical Debt: An Empirical Study
Technical debt is a well understood and used concept in IT development. The metaphor, rooted in the financial world, captures the amount of work that development teams owe to a product.
Luka Pavlič +3 more
doaj +3 more sources
Predicting software developer sentiment on self-admitted technical debt [PDF]
Technical debt is a metaphor for sacrificing long-term code quality in order to achieve short-term project goals. The technical debt that developers intentionally introduce into project is called self-admitted technical debt (SATD), which usually exists ...
Haichuan Zhang +6 more
doaj +3 more sources
Towards automating self-admitted technical debt repayment
Context: Self-Admitted Technical Debt (SATD) refers to the technical debt in software that is explicitly flagged, typically by the source code comment. The SATD literature has mainly focused on comprehending, describing, detecting, and recommending SATD. Most recently, there have been efforts to study the state of the code before and after removing the
Abdulaziz Alhefdhi +2 more
exaly +3 more sources
Automating Change-Level Self-Admitted Technical Debt Determination
Technical debt (TD) is a metaphor to describe the situation where developers introduce suboptimal solutions during software development to achieve short-term goals that may affect the long-term software quality. Prior studies proposed different techniques to identify TD, such as identifying TD through code smells or by analyzing source code comments ...
Meng Yan, Xin Xia, Emad Shihab
exaly +4 more sources
Software Self-admitted Technical Debt Identification with Bidirectional Gate Recurrent Unit and Attention Mechanism [PDF]
Software self-admitted technical debt(SATD) is written into the source code comments of the project by developers who leave a note admitting incurring intentionally for short-term benefits,and a large amount of SATD will be dangerous to software ...
XIONG Luo-geng, ZHENG Shang, ZOU Hai-tao, YU Hua-long, GAO Shang
doaj +1 more source

