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× | Mesure de la dette technique× | |
|---|---|---|
| Domaine | Génie logiciel | Génie logiciel |
| Famille | Process / pipeline | Process / pipeline |
| Année d'origine≠ | 1993 | 1992 |
| Auteur d'origine≠ | Gustav Karner | Ward Cunningham |
| Type≠ | quantitative estimation | quantitative assessment |
| Source fondatrice≠ | Karner, G. (1993). Resource estimation for objectory projects. Objective Systems SF, Inc. link ↗ | Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report. link ↗ |
| Alias | UCP, use case sizing, effort estimation | debt metrics, code health scoring, maintenance burden assessment |
| 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. | Technical debt represents accumulated shortcuts, deferred maintenance, and design compromises that incur future costs through slower development, higher defect rates, and deployment difficulty. Introduced by Ward Cunningham (1992), technical debt measurement quantifies these burdens using metrics like code complexity, duplication, test coverage gaps, and maintainability indices. Organizations use debt measurement to balance immediate delivery with long-term sustainability. |
| ScholarGateJeu de données ↗ |
|
|