Results 151 to 160 of about 9,472,967 (176)
Some of the next articles are maybe not open access.
Who (Self) Admits Technical Debt?
2020 IEEE International Conference on Software Maintenance and Evolution (ICSME), 2020Self-Admitted Technical Debt (SATD) are comments, left by developers in the source code or elsewhere, aimed at describing the presence of TD, i.e., source code "not ready yet". Although this was never stated in the original paper by Potdar and Shihab, the term SATD might suggest that it refers to a "self-admission" by whoever has written or changed the
Gianmarco Fucci +3 more
openaire +2 more sources
An Exploratory Study on Self-Admitted Technical Debt
2014 IEEE International Conference on Software Maintenance and Evolution, 2014Throughout a software development life cycle, developers knowingly commit code that is either incomplete, requires rework, produces errors, or is a temporary workaround. Such incomplete or temporary workarounds are commonly referred to as 'technical debt'. Our experience indicates that self-admitted technical debt is common in software projects and may
Emad Shihab
exaly +3 more sources
Towards automating self-admitted technical debt repayment
Information and Software TechnologyContext: 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
Recommending when Design Technical Debt Should be Self-Admitted
2017 IEEE International Conference on Software Maintenance and Evolution (ICSME), 2017Previous research has shown how developers "selfadmit" technical debt introduced in the source code, commenting why such code represents a workaround or a temporary, incomplete solution. This paper investigates the extent to which previously self-admitted technical debt can be used to provide recommendations to developers when they write new source ...
Fiorella Zampetti +4 more
openaire +2 more sources
An Empirical Study on the Urgent Self-admitted Technical Debt
Communications in Computer and Information ScienceChengyi Lin +3 more
exaly +3 more sources
On the value of a prioritization scheme for resolving Self-admitted technical debt
Journal of Systems and Software, 2018Abstract Programmers tend to leave incomplete, temporary workarounds and buggy codes that require rework in software development and such pitfall is referred to as Self-admitted Technical Debt (SATD). Previous studies have shown that SATD negatively affects software project and incurs high maintenance overheads.
Qing Mi, Kwabena Bennin, Jacky Keung
exaly +3 more sources
Examining the Impact of Self-Admitted Technical Debt on Software Quality
2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER), 2016Technical debt refers to incomplete or temporary workarounds that allow us to speed software development in the short term at the cost of paying a higher price later on. Recently, studies have shown that technical debt can be detected from source code comments, referred to as self-admitted technical debt.
Emad Shihab
exaly +2 more sources
A Survey of Self-Admitted Technical Debt Detection
Journal of Internet TechnologySelf-Admitted Technical Debt is a key research area in the current software engineering field. By detecting Self-Admitted Technical Debt, potential bugs in software code can be detected early, thus improving software quality. We have systematically organized and analyzed SATD detection in recent years and proposed several future research directions.
Xianzhen Dou, Long Li, Yubin Qu
openaire +1 more source
A large-scale empirical study on self-admitted technical debt
Proceedings of the 13th International Conference on Mining Software Repositories, 2016Technical debt is a metaphor introduced by Cunningham to indicate "not quite right code which we postpone making it right". Examples of technical debt are code smells and bug hazards. Several techniques have been proposed to detect different types of technical debt.
Gabriele Bavota, Barbara Russo
openaire +1 more source
On the Identification of Self-Admitted Technical Debt with Large Language Models
Anais do XXXVIII Simpósio Brasileiro de Engenharia de Software (SBES 2024)Self-Admitted Technical Debt (SATD) refers to a common practice in software engineering involving developers explicitly documenting and acknowledging technical debt within their projects. Identifying SATD in various contexts is a key activity for effective technical debt management and resolution. While previous research has focused on natural language
Pedro Lambert +2 more
openaire +2 more sources