Comparer des méthodes
Examinez les méthodes sélectionnées côte à côte ; les lignes qui diffèrent sont mises en évidence.
| Analyse des points de fonction× | Estimation par points de cas d'utilisation× | |
|---|---|---|
| Domaine | Génie logiciel | Génie logiciel |
| Famille | Process / pipeline | Process / pipeline |
| Année d'origine≠ | 1979 | 1993 |
| Auteur d'origine≠ | Allan Albrecht | Gustav Karner |
| Type≠ | quantitative measurement | quantitative estimation |
| Source fondatrice≠ | Albrecht, A. J. (1979). Measuring application development productivity. In Proceedings of the IBM Applications Development Symposium (pp. 83–92). link ↗ | Karner, G. (1993). Resource estimation for objectory projects. Objective Systems SF, Inc. link ↗ |
| Alias | FPA, function points, IFPUG sizing | UCP, use case sizing, effort estimation |
| Apparentées | 4 | 4 |
| Résumé≠ | Function point analysis (FPA) quantifies software size by counting business functions and user interactions independent of technology or programming language. Introduced by Albrecht (1979), FPA measures delivered functionality, enabling effort estimation, productivity benchmarking, and software value assessment. Organizations use FPA for project contracts, vendor comparison, and portfolio management. | 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. |
| ScholarGateJeu de données ↗ |
|
|