Process / pipelineCost estimation
技术债务度量
技术债务代表了累积的捷径、延迟的维护和设计妥协，这些都会通过开发速度减慢、缺陷率升高和部署困难等方式产生未来成本。技术债务度量由 Ward Cunningham (1992) 提出，使用代码复杂度、重复度、测试覆盖率差距和可维护性指数等指标来量化这些负担。组织使用债务度量来平衡即时交付与长期可持续性。
阅读完整方法
仅限会员
登录使用免费账户登录即可阅读本节。
Method map
The neighbourhood of related methods — select a node to explore.
来源
- Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report. link ↗
- 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 ↗
如何引用本页
ScholarGate. (2026, June 3). Technical Debt Quantification and Assessment. ScholarGate. https://scholargate.app/zh/software-engineering/technical-debt-measurement
Which method?
Set this method beside its closest kin and read them side by side — the library lays the books on the table; the choice is yours.
Compare side by side →