The DOI matches its Crossref record; 19 of the 19 references it cites were found in a registry or an index.
An Exploratory Study on Self-Admitted Technical Debt
Abstract
Throughout 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 negatively impact software maintenance, however, to date very little is known about them. Therefore, in this paper, we use source-code comments in four large open source software projects-Eclipse, Chromium OS, Apache HTTP Server, and ArgoUML to identify self-admitted technical debt. Using the identified technical debt, we study 1) the amount of self-admitted technical debt found in these projects, 2) why this self-admitted technical debt was introduced into the software projects and 3) how likely is the self-admitted technical debt to be removed after their introduction. We find that the amount of self-admitted technical debt exists in 2.4%-31% of the files. Furthermore, we find that developers with higher experience tend to introduce most of the self-admitted technical debt and that time pressures and complexity of the code do not correlate with the amount of self-admitted technical debt. Lastly, although self-admitted technical debt is meant to be addressed or removed in the future, only between 26.3%-63.5% of self-admitted technical debt gets removed from projects after introduction.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Don't touch my code!: examining the effects of ownership on software quality
Bird, C., Nagappan, N., Murphy, B., Gall, H., & Devanbu, P. (2011) · Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering · doi:10.1145/2025113.2025119 · Cited by 340
/*icomment: bugs or bad comments?*/
Tan, L., Yuan, D., Krishna, G., & Zhou, Y. (2007) · Proceedings of twenty-first ACM SIGOPS symposium on Operating systems principles · doi:10.1145/1294261.1294276 · Cited by 268
Toward an understanding of bug fix patterns
Pan, K., Kim, S., & Whitehead, E. J. (2009) · Empirical Software Engineering · doi:10.1007/s10664-008-9077-5 · Cited by 246
Do Code and Comments Co-Evolve? On the Relation between Source Code and Comment Changes
Fluri, B., Wursch, M., & Gall, H. C. (2007) · 14th Working Conference on Reverse Engineering (WCRE 2007) · doi:10.1109/wcre.2007.21 · Cited by 228
A Balancing Act: What Software Practitioners Have to Say about Technical Debt
Lim, E., Taksande, N., & Seaman, C. (2012) · IEEE Software · doi:10.1109/ms.2012.130 · Cited by 201
@tComment: Testing Javadoc Comments to Detect Comment-Code Inconsistencies
Tan, S. H., Marinov, D., Tan, L., & Leavens, G. T. (2012) · 2012 IEEE Fifth International Conference on Software Testing, Verification and Validation · doi:10.1109/icst.2012.106 · Cited by 197
Investigating the impact of design debt on software quality
Zazworka, N., Shaw, M. A., Shull, F., & Seaman, C. (2011) · Proceedings of the 2nd Workshop on Managing Technical Debt · doi:10.1145/1985362.1985366 · Cited by 180
An industrial study on the risk of software changes
Shihab, E., Hassan, A. E., Adams, B., & Jiang, Z. M. (2012) · ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering (ESEC/FSE) · doi:10.1145/2393596.2393670 · Cited by 175
Self-citationAllman, E. (2012) · Communications of the ACM · doi:10.1145/2160718.2160733 · Cited by 168
A case study on effectively identifying technical debt
Zazworka, N., Spinola, R. O., Vetrò, A., Shull, F. J., & Seaman, C. B. (2013) · International Conference on Evaluation and Assessment in Software Engineering (EASE) · doi:10.1145/2460999.2461005 · Cited by 142
Cited by
Examining the Impact of Self-Admitted Technical Debt on Software Quality
Wehaibi, S., Shihab, E., & Guerrouj, L. (2016) · 2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER) · doi:10.1109/saner.2016.72 · Cited by 114
Self-citationOn the Use of ChatGPT for Code Review: Do Developers Like Reviews By ChatGPT?
Watanabe, M., Kashiwa, Y., Lin, B., Hirao, T., Yamaguchi, K., & Iida, H. (2024) · Proceedings of the 28th International Conference on Evaluation and Assessment in Software Engineering · doi:10.1145/3661167.3661183 · Cited by 28
CODE reuse in practice: Benefiting or harming technical debt
Feitosa, D., Ampatzoglou, A., Gkortzis, A., Bibi, S., & Chatzigeorgiou, A. (2020) · Journal of Systems and Software · doi:10.1016/j.jss.2020.110618 · Cited by 20
“To this end, the roots of TD have been extensively studied ( Kazman et al., 2015 ; Mo et al., 2015 ; Xiao et al., 2016 ) along with factors that encourage developers to manage it efficiently ( Amanatidis et al., 2018 ; Ernst et al., 2014; Palomba et al., 2014 ; Potdar and Shihab, 2014 ).”
BackgroundSelf-Admitted GenAI Usage in Open-Source Software
Xiao, T., Fan, Y., Calefato, F., Treude, C., Kula, R. G., Hata, H., & Baltes, S. (2026) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2026.3681886 · Cited by 1
Metadata
- Authors
- Potdar, A., & Shihab, E.
- Venue
- 2014 IEEE International Conference on Software Maintenance and Evolution
- Publisher
- IEEE
- Published
- 2014-09
- Pages
- 91-100
- OpenAlex
- W2045336717
- Cited by
- 281
- References
- 19
- FWCI
- 7.98
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.