Comparar métodos
Revisa los métodos seleccionados uno junto a otro; las filas que difieren aparecen resaltadas.
| Análisis de Puntos de Función× | Estimación por Puntos de Caso de Uso× | |
|---|---|---|
| Campo | Ingeniería de software | Ingeniería de software |
| Familia | Process / pipeline | Process / pipeline |
| Año de origen≠ | 1979 | 1993 |
| Autor original≠ | Allan Albrecht | Gustav Karner |
| Tipo≠ | quantitative measurement | quantitative estimation |
| Fuente seminal≠ | 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 |
| Relacionados | 4 | 4 |
| Resumen≠ | 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. |
| ScholarGateConjunto de datos ↗ |
|
|