Technical Debt Quantification
Technical Debt Quantification is the measurement and monetization of technical shortcuts taken during development (incomplete refactoring, outdated dependencies, deferred testing). Coined by Cunningham in 1992, the metaphor frames accumulated shortcuts as financial debt: taking shortcuts saves immediate time but incurs interest (slower future development) and risk (outages).
Kilderegistrering
Citater kopieret ordret fra metodens kilderegistrering. Ingen påstandsniveauverifikation er udledt heraf.
- Cunningham, W. (1992). The WyCash portfolio management system. OOPSLA '92 Experience Report. · URL
- Seaman, C. B., & Guo, Y. (2011). Measuring and monitoring technical debt. Advances in Computers, 82, 25–46. · DOI 10.1016/B978-0-12-385512-1.00002-5
- Tom, E., Aurum, A., & Vidgen, R. (2013). An exploration of technical debt. Journal of Systems and Software, 86(6), 1498–1516. · DOI 10.1016/j.jss.2012.12.052
Kuraterede påstande
Påstande gemt i bevis-loggen, hver med sin egen vurdering.
Denne visning opfinder ikke en påstandsvurdering, når loggen ingen har.
Relaterede metoder
Genereret fra metodegrafen og vist som maskinelt foreslåede relationer — ingen bevispåstand er udledt.
Den genererede relationsgraf har ingen udgående relation for denne metode.