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.
| Phân tích độ bao phủ mã nguồn× | Các chỉ số đo lường độ phức tạp phần mềm× | |
|---|---|---|
| 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≠ | 1988 | 1976 |
| Người khởi xướng≠ | Test Coverage Community | Thomas J. McCabe |
| Loại≠ | measurement and analysis | quantitative measurement |
| Công trình gốc≠ | 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 ↗ | McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320. DOI ↗ |
| Tên gọi khác≠ | coverage metrics, test coverage, instrumentation-based measurement | code complexity analysis, complexity measurement |
| Liên quan | 4 | 4 |
| Tóm tắt≠ | 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. | 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. |
| ScholarGateBộ dữ liệu ↗ |
|
|