Export Citations
Save this search
Please login to be able to save your searches and receive alerts for new content matching your search criteria.
- research-articleApril 2024
Towards automating self-admitted technical debt repayment
Information and Software Technology (INST), Volume 167, Issue CMar 2024https://doi.org/10.1016/j.infsof.2023.107376Abstract 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 ...
- research-articleFebruary 2024
Quantifying and characterizing clones of self-admitted technical debt in build systems
Empirical Software Engineering (KLU-EMSE), Volume 29, Issue 2Mar 2024https://doi.org/10.1007/s10664-024-10449-5AbstractSelf-Admitted Technical Debt (SATD) annotates development decisions that intentionally exchange long-term software artifact quality for short-term goals. Recent work explores the existence of SATD clones (duplicate or near duplicate SATD comments) ...
- research-articleNovember 2023
Keyword-labeled self-admitted technical debt and static code analysis have significant relationship but limited overlap
Software Quality Journal (KLU-SQJO), Volume 32, Issue 2Jun 2024, Pages 391–429https://doi.org/10.1007/s11219-023-09655-zAbstractTechnical debt presents sub-optimal choices made in development, which are beneficial in the short term but not in the long run. Consciously admitted debt, which is marked with a keyword, e.g., TODO, is called keyword-labeled self-admitted ...
- research-articleAugust 2023
A two-stage approach for identifying and interpreting self-admitted technical debt
Applied Intelligence (KLU-APIN), Volume 53, Issue 22Nov 2023, Pages 26592–26602https://doi.org/10.1007/s10489-023-04941-6AbstractA major current focus in software quality is how to identify and interpret Self-admitted technical debt(SATD). While many methods have been proposed to identify SATD, these methods are neither interpretable nor generic. There remains a need for an ...
- research-articleApril 2023
Automatic identification of self-admitted technical debt from four different sources
Empirical Software Engineering (KLU-EMSE), Volume 28, Issue 3May 2023https://doi.org/10.1007/s10664-023-10297-9AbstractTechnical debt refers to taking shortcuts to achieve short-term goals while sacrificing the long-term maintainability and evolvability of software systems. A large part of technical debt is explicitly reported by the developers themselves; this is ...
-
- research-articleJanuary 2023
SCGRU: A general approach for identifying multiple classes of self-admitted technical debt with text generation oversampling
Journal of Systems and Software (JSSO), Volume 195, Issue CJan 2023https://doi.org/10.1016/j.jss.2022.111514AbstractIdentifying self-admitted technical debt (SATD) plays an important role in maintaining software stability and improving software quality. Although existing methods can detect SATD and researchers have identified design debt and ...
Graphical abstractDisplay Omitted
Highlights- A new approach called SCGRU is proposed to identify self-admitted technical debt.
- research-articleNovember 2022
Identifying self-admitted technical debt in issue tracking systems using machine learning
Empirical Software Engineering (KLU-EMSE), Volume 27, Issue 6Nov 2022https://doi.org/10.1007/s10664-022-10128-3AbstractTechnical debt is a metaphor indicating sub-optimal solutions implemented for short-term benefits by sacrificing the long-term maintainability and evolvability of software. A special type of technical debt is explicitly admitted by software ...
- research-articleNovember 2022
FIXME: synchronize with database! An empirical study of data access self-admitted technical debt
Empirical Software Engineering (KLU-EMSE), Volume 27, Issue 6Nov 2022https://doi.org/10.1007/s10664-022-10119-4AbstractDevelopers sometimes choose design and implementation shortcuts due to the pressure from tight release schedules. However, shortcuts introduce technical debt that increases as the software evolves. The debt needs to be repaid as fast as possible ...
- research-articleNovember 2022
A framework for conditional statement technical debt identification and description
Automated Software Engineering (KLU-AUSE), Volume 29, Issue 2Nov 2022https://doi.org/10.1007/s10515-022-00364-8AbstractTechnical 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 ...
- research-articleNovember 2022
Self-admitted technical debt in R: detection and causes
Automated Software Engineering (KLU-AUSE), Volume 29, Issue 2Nov 2022https://doi.org/10.1007/s10515-022-00358-6AbstractSelf-Admitted Technical Debt (SATD) is primarily studied in Object-Oriented (OO) languages and traditionally commercial software. However, scientific software coded in dynamically-typed languages such as R differs in paradigm, and the source code ...
- research-articleJune 2022
An empirical study on self-admitted technical debt in modern code review
- Yutaro Kashiwa,
- Ryoma Nishikawa,
- Yasutaka Kamei,
- Masanari Kondo,
- Emad Shihab,
- Ryosuke Sato,
- Naoyasu Ubayashi
Information and Software Technology (INST), Volume 146, Issue CJun 2022https://doi.org/10.1016/j.infsof.2022.106855AbstractTechnical debt is a sub-optimal state of development in projects. In particular, the type of technical debt incurred by developers themselves (e.g., comments that mean the implementation is imperfect and should be replaced with another ...
- research-articleMay 2022
Exploiting gated graph neural network for detecting and explaining self-admitted technical debts
Journal of Systems and Software (JSSO), Volume 187, Issue CMay 2022https://doi.org/10.1016/j.jss.2022.111219AbstractSelf-admitted technical debt (SATD) refers to a specific type of technical debt that is introduced intentionally in the software development and maintenance processes. SATD enables practitioners to take some temporary solutions instead ...
Highlights- Introducing the graph-gated neural network for detecting SATDs.
- Updating the ...
- research-articleMarch 2022
An empirical study on self-admitted technical debt in Dockerfiles
Empirical Software Engineering (KLU-EMSE), Volume 27, Issue 2Mar 2022https://doi.org/10.1007/s10664-021-10081-7AbstractIn software development, ad hoc solutions that are intentionally implemented by developers are called self-admitted technical debt (SATD). Because the existence of SATD spreads poor implementations, it is necessary to remove it as soon as ...
- research-articleJanuary 2022
Deep neural network ensembles for detecting self-admitted technical debt
Journal of Intelligent & Fuzzy Systems: Applications in Engineering and Technology (JIFS), Volume 43, Issue 12022, Pages 93–105https://doi.org/10.3233/JIFS-211273Effectively identifying self-admitted technical debt (SATD) from project source code comments helps developers quickly find and repay these debts, thereby reducing its negative impact. Previous studies used techniques based on patterns, text mining, ...
- rapid-communicationJanuary 2022
SATDBailiff-mining and tracking self-admitted technical debt
- Eman Abdullah AlOmar,
- Ben Christians,
- Mihal Busho,
- Ahmed Hamad AlKhalid,
- Ali Ouni,
- Christian Newman,
- Mohamed Wiem Mkaouer
Science of Computer Programming (SCPR), Volume 213, Issue CJan 2022https://doi.org/10.1016/j.scico.2021.102693Highlights- This paper presents SATDBailiff, a tool for identifying and tracking SATD comments.
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 ...
- research-articleNovember 2021
Self-admitted technical debt practices: a comparison between industry and open-source
Empirical Software Engineering (KLU-EMSE), Volume 26, Issue 6Nov 2021https://doi.org/10.1007/s10664-021-10031-3AbstractSelf-admitted technical debt (SATD) consists of annotations, left by developers as comments in the source code or elsewhere, as a reminder about pieces of software manifesting technical debt (TD), i.e., “not being ready yet”. While previous ...
- research-articleJuly 2021
How Far Have We Progressed in Identifying Self-admitted Technical Debts? A Comprehensive Empirical Study
ACM Transactions on Software Engineering and Methodology (TOSEM), Volume 30, Issue 4Article No.: 45, Pages 1–56https://doi.org/10.1145/3447247Background. Self-admitted technical debt (SATD) is a special kind of technical debt that is intentionally introduced and remarked by code comments. Those technical debts reduce the quality of software and increase the cost of subsequent software ...
- research-articleMarch 2021
An exploratory study on the introduction and removal of different types of technical debt in deep learning frameworks
Empirical Software Engineering (KLU-EMSE), Volume 26, Issue 2Mar 2021https://doi.org/10.1007/s10664-020-09917-5AbstractTo complete tasks faster, developers often have to sacrifice the quality of the software. Such compromised practice results in the increasing burden to developers in future development. The metaphor, technical debt, describes such practice. Prior ...
- research-articleSeptember 2020
Wait for it: identifying “On-Hold” self-admitted technical debt
Empirical Software Engineering (KLU-EMSE), Volume 25, Issue 5Sep 2020, Pages 3770–3798https://doi.org/10.1007/s10664-020-09854-3AbstractSelf-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 ...
- research-articleMay 2020
Identifying self-admitted technical debt through code comment analysis with a contextualized vocabulary
- Mário André de Freitas Farias,
- Manoel Gomes de Mendonça Neto,
- Marcos Kalinowski,
- Rodrigo Oliveira Spínola
Information and Software Technology (INST), Volume 121, Issue CMay 2020https://doi.org/10.1016/j.infsof.2020.106270Abstract ContextPrevious work has shown that one can explore code comments to detect Self-Admitted Technical Debt (SATD) using a contextualized vocabulary. However, current detection strategies still return a large number of false ...