Results 11 to 20 of about 1,295 (147)
Automated Identification of On-hold Self-admitted Technical Debt [PDF]
Replication package of "Automated Identification of On-hold Self-admitted Technical Debt"
Rungroj Maipradit +6 more
openaire +4 more sources
An empirical study on self-admitted technical debt in Dockerfiles [PDF]
AbstractIn 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 possible. Meanwhile, container virtualization has been attracting attention in recent years as a technology
Hideaki Azuma +3 more
openaire +1 more source
Data Balancing Improves Self-Admitted Technical Debt Detection [PDF]
11 pages, 1 figure, for ...
Rantala Leevi +3 more
openaire +3 more sources
Self-admitted technical debt in R: detection and causes
AbstractSelf-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 comments’ semantics are different (i.e., more aligned with algorithms and statistics when compared ...
Rishab Sharma +4 more
openaire +2 more sources
Automatically Learning Patterns for Self-Admitted Technical Debt Removal [PDF]
Technical Debt (TD) expresses the need for improvements in a software system, e.g., to its source code or architecture. In certain circumstances, developers “self-admit” technical debt (SATD) in their source code comments. Previous studies investigate when SATD is admitted, and what changes developers perform to remove it. Building on these studies, we
Fiorella Zampetti +2 more
openaire +2 more sources
On the documentation of self-admitted technical debt in issues
Self-Admitted Technical Debt (SATD) is a particular case of Technical Debt (TD) in which developers rely on source code comments (SATD-C) or labeled issues (SATD-I) to report their sub-optimal technical solutions. In this paper, we first explore a sample of 286 SATD-I instances collected from five open source projects, including Microsoft Visual Studio
Laerte Xavier +4 more
openaire +3 more sources
Self-Admitted Technical Debt and comments’ polarity: an empirical study
AbstractSelf-Admitted Technical Debt (SATD) consists of annotations—typically, but not only, source code comments—pointing out incomplete features, maintainability problems, or, in general, portions of a program not-ready yet. The way a SATD comment is written, and specifically its polarity, may be a proxy indicator of the severity of the problem and ...
Nathan Cassee +4 more
openaire +2 more sources
short ...
Barbara Russo +2 more
openaire +2 more sources
An Empirical Study on the Removal of Self-Admitted Technical Debt
Technical debt refers to the phenomena of taking shortcuts to achieve short term gain at the cost of higher maintenance efforts in the future. Recently, approaches were developed to detect technical debt through code comments, referred to as Self-Admitted Technical Debt (SATD).
Everton da S. Maldonado +3 more
openaire +1 more source
Characterizing and Mitigating Self-Admitted Technical Debt in Build Systems [PDF]
Technical Debt is a metaphor used to describe the situation in which long-term software artifact quality is traded for short-term goals in software projects. In recent years, the concept of self-admitted technical debt (SATD) was proposed, which focuses on debt that is intentionally introduced and described by developers.
Tao Xiao 0001 +6 more
openaire +2 more sources

