Comparer des méthodes

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