Results 141 to 150 of about 2,119 (166)
Some of the next articles are maybe not open access.
A survey of self-admitted technical debt
Journal of Systems and Software, 2019Abstract Technical Debt is a metaphor used to express sub-optimal source code implementations that are introduced for short-term benefits that often need to be paid back later, at an increased cost. In recent years, various empirical studies have focused on investigating source code comments that indicate Technical Debt often referred to as Self ...
Giancarlo Sierra +2 more
exaly +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 +2 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, Latifa Guerrouj
exaly +2 more sources
Recommending when Design Technical Debt Should be Self-Admitted [PDF]
2017 IEEE International Conference on Software Maintenance and Evolution (ICSME), 2017 Previous 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 +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.
Jacky Keung +2 more
exaly +2 more sources
Multiclass Classification for Self-Admitted Technical Debt Based on XGBoost
IEEE Transactions on Reliability, 2022Xin Chen, Dongjin Yu
exaly +2 more sources
An Empirical Study on the Urgent Self-admitted Technical Debt
Communications in Computer and Information ScienceHuang Qiao
exaly +2 more sources
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 +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