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).
Rekodi ya chanzo
Nukuu zimehamishwa kwa uhalisi kutoka kwa rekodi ya chanzo cha mbinu. Hakuna uthibitisho wa kiwango cha dai unaodokezwa kutoka kwao.
- 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
Madai yaliyotunzwa
Madai yamehifadhiwa katika daftari la ushahidi, kila moja ikiwa na tathmini yake.
Mwonekano huu haubuni tathmini ya dai wakati daftari haina yoyote.
Mbinu zinazohusiana
Zilizotengenezwa kutoka kwa grafu ya mbinu na kuonyeshwa kama uhusiano uliopendekezwa na mashine — hakuna dai la ushahidi linalodokezwa.
Grafu ya uhusiano iliyotengenezwa haina uhusiano wowote unaotoka kwa mbinu hii.