Results 21 to 30 of about 9,472,967 (176)
Organizing the Technical Debt Landscape [PDF]
, 2012 To date, several methods and tools for detecting source code and design anomalies have been developed. While each method focuses on identifying certain classes of source code anomalies that potentially relate to technical debt (TD), the overlaps and gaps
Nico Zazworka +8 more
core +2 more sources
On the documentation of self-admitted technical debt in issues
Empirical Software Engineering, 2022 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
, 2023 This dataset includes a trained weight file for identifying the relations between self-admitted technical debt ...
Mohamed Soliman +2 more
core +3 more sources
Self-Admitted Technical Debt and comments’ polarity: an empirical study
Empirical Software Engineering, 2022 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 +3 more sources
Self-Admitted Technical Debt and Comments’ Polarity: An Empirical Study
, 2021 Replication package for the paper: 'Self-Admitted Technical Debt and Comments’ Polarity: An Empirical Study'
Nicole Novielli (5853110) +4 more
core +1 more source
Waiting around or job half-done? Sentiment in self-admitted technical debt [PDF]
, 2021 Self-Admitted Technical Debt (SATD) represents the admission, made through source code comments or other channels, of portions of a program being poorly implemented, containing provisional solutions or, in general, simply being not ready yet.
Nathan Cassee +11 more
core +1 more source
An Empirical Study on the Removal of Self-Admitted Technical Debt
2017 IEEE International Conference on Software Maintenance and Evolution (ICSME), 2017 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
Skuld: a self-learning tool for impact-driven technical debt management
, 2022 S.113-114As the development progresses, software projects tend to accumulate Technical Debt and become harder to maintain. Multiple tools exist with the mission to help practitioners to better manage Technical Debt. Despite this progress, there is a lack
Bas, Pieter +4 more
core +1 more source
Identifying Self-Admitted Technical Debts With Jitterbug: A Two-Step Approach [PDF]
IEEE Transactions on Software Engineering, 2022 Keeping track of and managing Self-Admitted Technical Debts (SATDs) are important to maintaining a healthy software project. This requires much time and effort from human experts to identify the SATDs manually. The current automated solutions do not have satisfactory precision and recall in identifying SATDs to fully automate the process.
Zhe Yu 0002 +3 more
openaire +2 more sources
, 2022 Art. 106270Context Previous work has shown that one can explore code comments to detect Self-Admitted Technical Debt (SATD) using a contextualized vocabulary.
Freitas Farias, M.A. de +3 more
core +1 more source