Comparer des méthodes
Examinez les méthodes sélectionnées côte à côte ; les lignes qui diffèrent sont mises en évidence.
| Estimation par points de cas d'utilisation× | Métriques de complexité logicielle× | |
|---|---|---|
| Domaine | Génie logiciel | Génie logiciel |
| Famille | Process / pipeline | Process / pipeline |
| Année d'origine≠ | 1993 | 1976 |
| Auteur d'origine≠ | Gustav Karner | Thomas J. McCabe |
| Type≠ | quantitative estimation | quantitative measurement |
| Source fondatrice≠ | Karner, G. (1993). Resource estimation for objectory projects. Objective Systems SF, Inc. link ↗ | McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320. DOI ↗ |
| Alias≠ | UCP, use case sizing, effort estimation | code complexity analysis, complexity measurement |
| Apparentées | 4 | 4 |
| Résumé≠ | Use case point (UCP) estimation quantifies software development effort by analyzing use cases and environmental factors. Introduced by Karner (1993) for Objectory methodology, UCP provides structured approach to estimate labor hours from system requirements. Organizations use UCP to forecast project duration, allocate resources, and validate high-level project plans early in development. | 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. |
| ScholarGateJeu de données ↗ |
|
|