Comparer des méthodes
Examinez les méthodes sélectionnées côte à côte ; les lignes qui diffèrent sont mises en évidence.
| Détection des odeurs architecturales× | Analyse statique de code× | |
|---|---|---|
| Domaine | Génie logiciel | Génie logiciel |
| Famille | Process / pipeline | Process / pipeline |
| Année d'origine≠ | 2009 | 2001 |
| Auteur d'origine≠ | Martin Fowler and García et al. | David Engler and William Pugh |
| Type≠ | pattern-based analysis | automated analysis |
| Source fondatrice≠ | Fowler, M. (2018). Code smell. Martin Fowler's Website. link ↗ | Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional. link ↗ |
| Alias | design smell detection, architectural debt analysis, system quality assessment | static analysis, code inspection, automated review |
| Apparentées | 4 | 4 |
| Résumé≠ | Architecture smells are recurring patterns in system structure that indicate potential design problems. Introduced by García et al. (2009), these patterns signal violations of architectural principles (modularity, independence, abstraction) at system scale. Detection combines code metrics, dependency analysis, and pattern recognition to identify smells early, guiding refactoring and architectural improvements. | 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. |
| ScholarGateJeu de données ↗ |
|
|