So sánh phương pháp
Xem các phương pháp đã chọn cạnh nhau; những hàng khác biệt được làm nổi bật.
| Các chỉ số đo lường độ phức tạp phần mềm× | Đo lường Nợ Kỹ thuật× | |
|---|---|---|
| Lĩnh vực | Kỹ thuật phần mềm | Kỹ thuật phần mềm |
| Họ | Process / pipeline | Process / pipeline |
| Năm ra đời≠ | 1976 | 1992 |
| Người khởi xướng≠ | Thomas J. McCabe | Ward Cunningham |
| Loại≠ | quantitative measurement | quantitative assessment |
| Công trình gốc≠ | 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 ↗ |
| Tên gọi khác≠ | code complexity analysis, complexity measurement | debt metrics, code health scoring, maintenance burden assessment |
| Liên quan | 4 | 4 |
| Tóm tắt≠ | 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. |
| ScholarGateBộ dữ liệu ↗ |
|
|