Comparer des méthodes
Examinez les méthodes sélectionnées côte à côte ; les lignes qui diffèrent sont mises en évidence.
| Métriques de complexité logicielle× | Mesure de la dette technique× | |
|---|---|---|
| Domaine | Génie logiciel | Génie logiciel |
| Famille | Process / pipeline | Process / pipeline |
| Année d'origine≠ | 1976 | 1992 |
| Auteur d'origine≠ | Thomas J. McCabe | Ward Cunningham |
| Type≠ | quantitative measurement | quantitative assessment |
| Source fondatrice≠ | 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 ↗ |
| Alias≠ | code complexity analysis, complexity measurement | debt metrics, code health scoring, maintenance burden assessment |
| Apparentées | 4 | 4 |
| Résumé≠ | 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. |
| ScholarGateJeu de données ↗ |
|
|