Figure - available via license: Creative Commons Attribution 4.0 International
Content may be subject to copyright.
Download
View publication
Frequently occurring n-gram features in each category

Frequently occurring n-gram features in each category

Source publication
Performance of classifiers for SABD reason
Frequently occurring n-gram features in each category
Distribution of 'ready-to-be-addressed' SABD
Characterizing and Mitigating Self-Admitted Build Debt
Preprint
Full-text available
  • Feb 2021
Technical Debt is a metaphor used to describe the situation in which long-term code 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. Although prior work has made important...
Cite
Download full-text

Context in source publication

Context 1
... Table 6, we list the most frequently occurring Ngram features. For example, 'workaround for' appeared 54 times for SABD comments with the Workaround purpose, and 'be break' appeared 18 times for SABD comments about Limitation reason. ...

Similar publications

Performance of classifiers for SATD reason
Performance of classifiers for SATD purpose
Frequently occurring n-gram features in each category
Frequency of link target types in 90 SATD com- ments
Demographics of survey participants
Characterizing and Mitigating Self-Admitted Technical Debt in Build Systems
Article
Full-text available
  • Sep 2021
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. Although prior work has ma...
View