方法对比
并排查看您选择的方法；存在差异的行会高亮显示。
| 技术债务度量× | 代码覆盖率分析× | |
|---|---|---|
| 领域 | 软件工程 | 软件工程 |
| 方法族 | Process / pipeline | Process / pipeline |
| 起源年份≠ | 1992 | 1988 |
| 提出者≠ | Ward Cunningham | Test Coverage Community |
| 类型≠ | quantitative assessment | measurement and analysis |
| 开创性文献≠ | Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report. link ↗ | Zhu, H., Hall, P. A. V., & May, J. H. R. (1997). Software unit test coverage and adequacy. ACM Computing Surveys, 29(4), 366–427. DOI ↗ |
| 别名 | debt metrics, code health scoring, maintenance burden assessment | coverage metrics, test coverage, instrumentation-based measurement |
| 相关 | 4 | 4 |
| 摘要≠ | 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. | Code coverage analysis measures the extent to which source code is executed by a test suite, quantifying which lines, branches, or paths are exercised. Tools instrument code to track execution, reporting coverage percentages and identifying untested regions. Coverage analysis guides test creation, detects dead code, and validates test adequacy in quality assurance processes. |
| ScholarGate数据集 ↗ |
|
|