The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Measuring and Monitoring Technical Debt
Open accessAbstract
Abstract Technical debt is a metaphor for immature, incomplete, or inadequate artifacts in the software development lifecycle that cause higher costs and lower quality in the long run. These artifacts remaining in a system affect subsequent development and maintenance activities, and so can be seen as a type of debt that the system developers owe the system. Incurring technical debt may speed up software development in the short run, but such benefit is achieved at the cost of extra work in the future, as if paying interest on the debt. In this sense, the technical debt metaphor characterizes the relationship between the short-term benefits of delaying certain software maintenance tasks or doing them quickly and less carefully, and the long-term cost of those delays. However, managing technical debt is more complicated than managing financial debt because of the uncertainty involved. In this chapter, the authors review the main issues associated with technical debt, and propose a technical debt management framework and a research plan for validation. The objective of our research agenda is to develop and validate a comprehensive technical debt theory that formalizes the relationship between the cost and benefit sides of the concept. Further, we propose to use the theory to propose mechanisms (processes and tools) for measuring and managing technical debt in software product maintenance. The theory and management mechanisms are intended ultimately to contribute to the improved quality of software and facilitate decision making in software maintenance.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
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
The WyCash portfolio management system
Cunningham, W. (1992) · Addendum to the proceedings on Object-oriented programming systems, languages, and applications (Addendum) - OOPSLA '92 · doi:10.1145/157709.157715 · Cited by 742
Cited by
A systematic mapping study on technical debt and its management
Li, Z., Avgeriou, P., & Liang, P. (2015) · Journal of Systems and Software · doi:10.1016/j.jss.2014.12.027 · Cited by 743
Azeem, M. I., Palomba, F., Shi, L., & Wang, Q. (2019) · Information and Software Technology · doi:10.1016/j.infsof.2018.12.009 · Cited by 289
Design Rule Spaces: A New Model for Representing and Analyzing Software Architecture
Cai, Y., Xiao, L., Kazman, R., Mo, R., & Feng, Q. (2019) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2018.2797899 · Cited by 39
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
Muszynski, M., Lugtigheid, S., Castor, F., & Brinkkemper, S. (2022) · 2022 IEEE 19th International Conference on Software Architecture (ICSA) · doi:10.1109/icsa53651.2022.00013 · Cited by 10
Metadata
- Authors
- Seaman, C., & Guo, Y.
- Venue
- Advances in Computers
- Publisher
- Elsevier
- Published
- 2011
- Pages
- 25-46
- ISSN
- 0065-2458 (ISSN-L)
- OpenAlex
- W140915724
- Cited by
- 217
- References
- 1
- FWCI
- 47.28
- Type
- book chapter
- Language
- en
- Open access
- green
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
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Measuring and Monitoring Technical Debt. https://app.cochat.ai/papers/10.1016/b978-0-12-385512-1.00002-5
- The paper
- Seaman, C., & Guo, Y. (2011). Measuring and Monitoring Technical Debt. Advances in Computers. https://doi.org/10.1016/b978-0-12-385512-1.00002-5
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.