2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER) 2016
DOI: 10.1109/saner.2016.72
|View full text |Cite
|
Sign up to set email alerts
|

Examining the Impact of Self-Admitted Technical Debt on Software Quality

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

1
76
2

Year Published

2017
2017
2024
2024

Publication Types

Select...
3
3
2

Relationship

1
7

Authors

Journals

citations
Cited by 100 publications
(79 citation statements)
references
References 30 publications
1
76
2
Order By: Relevance
“…Wehaibi et al [34] measured the impact of SATD on software development practices nding that the presence of self-admitted technical debt leads to a complex change in the future. From a dierent perspective, Zampetti et al [36] developed a machine learning approach that, by leveraging on structural information (metrics or warnings raised by static analysis tools) is able to recommend developers with design TD to be admitted.…”
Section: Detection and Management Of Technicalmentioning
confidence: 99%
“…Wehaibi et al [34] measured the impact of SATD on software development practices nding that the presence of self-admitted technical debt leads to a complex change in the future. From a dierent perspective, Zampetti et al [36] developed a machine learning approach that, by leveraging on structural information (metrics or warnings raised by static analysis tools) is able to recommend developers with design TD to be admitted.…”
Section: Detection and Management Of Technicalmentioning
confidence: 99%
“…As the prior work showed, not all comments can contain self-admitted technical debt [29], [37]. Therefore, in the preprocessing we exclude the following types of comments:…”
Section: Extracting Source Code Commentsmentioning
confidence: 99%
“…That said, comments that contain task annotations (i.e., "TODO:", "FIXME:", or "XXX:") [36] are not removed since they are usually leveraged by most IDEs, e.g., Eclipse and Netbeans, to automatically generate task lists. • Commented-out source code, which is explicitly commented out by developers and not compiled is also ignored since prior work showed that it generally does not contain self-admitted technical debt [29], [37]. • Automatically generated comments by the IDE are also removed since they, by definition, do not indicate selfadmitted technical debt.…”
Section: Extracting Source Code Commentsmentioning
confidence: 99%
See 1 more Smart Citation
“…Concerning "how" SATD is being removed, Wehaibi et al [52] found that SATD may lead, in general, towards complex software changes, while Maldonado et al [9] conducted a survey on SATD removal and found that this happens either in the context of bug fixing, or feature addition. Starting from the results of Maldonado et al [9], Zampetti et al [58] analyzed the change patterns that lead towards SATD removal, by combining an automated analysis through GumTree [14] with manual analysis.…”
Section: Introductionmentioning
confidence: 99%