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 CK× | Complexité cyclomatique× | |
|---|---|---|
| Domaine | Méthodes numériques | Méthodes numériques |
| Famille | Machine learning | Machine learning |
| Année d'origine≠ | 1994 | 1976 |
| Auteur d'origine≠ | Shyam Chidamber and Chris Kemerer | Thomas McCabe |
| Type≠ | Design quality metric suite | Control-flow complexity metric |
| Source fondatrice≠ | Chidamber, S. R., & Kemerer, C. F. (1994). A metrics suite for object-oriented design. IEEE Transactions on Software Engineering, 20(6), 476–493. DOI ↗ | McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, SE-2(4), 308–320. DOI ↗ |
| Alias | OO metrics, CK suite, object-oriented complexity | CC, cyclomatic number, McCabe complexity |
| Apparentées | 1 | 1 |
| Résumé≠ | CK Metrics is a suite of six object-oriented design metrics introduced by Chidamber and Kemerer in 1994 to measure class complexity, cohesion, and coupling. The metrics quantify OO design quality; high coupling and low cohesion predict defects and maintenance effort. | Cyclomatic Complexity (CC), introduced by Thomas McCabe in 1976, is a quantitative metric measuring the number of linearly independent paths through a function's control-flow graph. A function with high cyclomatic complexity is harder to understand, test, and maintain; McCabe advocated a threshold of 10 as the complexity limit for maintainability. |
| ScholarGateJeu de données ↗ |
|
|