Sammenlign metoder
Gjennomgå de valgte metodene side om side; rader som avviker, er uthevet.
| Måling av teknisk gjeld× | Kodekodedekningsanalyse× | |
|---|---|---|
| Fagfelt | Programvareteknikk | Programvareteknikk |
| Familie | Process / pipeline | Process / pipeline |
| Opprinnelsesår≠ | 1992 | 1988 |
| Opphavsperson≠ | Ward Cunningham | Test Coverage Community |
| Type≠ | quantitative assessment | measurement and analysis |
| Opprinnelig kilde≠ | 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 ↗ |
| Alias | debt metrics, code health scoring, maintenance burden assessment | coverage metrics, test coverage, instrumentation-based measurement |
| Relaterte | 4 | 4 |
| Sammendrag≠ | 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. |
| ScholarGateDatasett ↗ |
|
|