方法证据记录
Technical Debt Measurement
Technical debt represents accumulated shortcuts, deferred maintenance, and design compromises that incur future costs through slower development, higher defect rates, and deployment difficulty. Introduced by Ward Cunningham (1992), technical debt measurement quantifies these burdens using metrics like code complexity, duplication, test coverage gaps, and maintainability indices. Organizations use debt measurement to balance immediate delivery with long-term sustainability.
源记录
引文逐字复制自方法源记录。这些引文不代表任何层级的验证。
Technical Debt Quantification and Assessment
分类方法记录 · process-pipeline / software-engineering
- 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
精选声明
声明已持久化到证据分类账中，每个声明都有自己的评估。
尚无精选声明
当分类账中没有声明时，此视图不会自行创建声明评估。
相关方法
从方法图中生成，显示为机器建议的关系 — 不推断任何证据声明。