Sammenlign metoder
Gjennomgå de valgte metodene side om side; rader som avviker, er uthevet.
| Måling av teknisk gjeld× | Statisk kodeanalyse× | |
|---|---|---|
| Fagfelt | Programvareteknikk | Programvareteknikk |
| Familie | Process / pipeline | Process / pipeline |
| Opprinnelsesår≠ | 1992 | 2001 |
| Opphavsperson≠ | Ward Cunningham | David Engler and William Pugh |
| Type≠ | quantitative assessment | automated analysis |
| Opprinnelig kilde≠ | Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report. link ↗ | Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. link ↗ |
| Alias | debt metrics, code health scoring, maintenance burden assessment | static analysis, code inspection, automated review |
| 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. | Static code analysis automatically examines source code without execution, detecting potential bugs, security vulnerabilities, code smells, and style violations. Pioneered by Engler and Pugh (2001), automated analysis tools scan codebases at scale, identifying defect patterns faster than manual review. Organizations integrate static analysis into continuous integration pipelines to prevent defects early. |
| ScholarGateDatasett ↗ |
|
|