方法对比
并排查看您选择的方法；存在差异的行会高亮显示。
| 软件复杂度度量× | 技术债务度量× | |
|---|---|---|
| 领域 | 软件工程 | 软件工程 |
| 方法族 | Process / pipeline | Process / pipeline |
| 起源年份≠ | 1976 | 1992 |
| 提出者≠ | Thomas J. McCabe | Ward Cunningham |
| 类型≠ | quantitative measurement | quantitative assessment |
| 开创性文献≠ | McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320. DOI ↗ | Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report. link ↗ |
| 别名≠ | code complexity analysis, complexity measurement | debt metrics, code health scoring, maintenance burden assessment |
| 相关 | 4 | 4 |
| 摘要≠ | Software complexity metrics quantify the structural and operational difficulty of code through numerical measurements. Introduced by Thomas McCabe in 1976, cyclomatic complexity became the foundational approach. These metrics assess maintainability, testability, and defect risk, enabling teams to identify problematic code regions and guide refactoring efforts. | 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. |
| ScholarGate数据集 ↗ |
|
|