Comparer des méthodes

	Métriques de complexité logicielle	Analyse statique de code
Domaine	Génie logiciel	Génie logiciel
Famille	Process / pipeline	Process / pipeline
Année d'origine	1976	2001
Auteur d'origine	Thomas J. McCabe	David Engler and William Pugh
Type	quantitative measurement	automated analysis
Source fondatrice	McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320.	Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional.
Alias	code complexity analysis, complexity measurement	static analysis, code inspection, automated review
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.	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.