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× | Medición de la Deuda Técnica× | |
|---|---|---|
| Campo | Ingeniería de software | Ingeniería de software |
| Familia | Process / pipeline | Process / pipeline |
| Año de origen≠ | 1979 | 1992 |
| Autor original≠ | Allan Albrecht | Ward Cunningham |
| Tipo≠ | quantitative measurement | quantitative assessment |
| Fuente seminal≠ | Albrecht, A. J. (1979). Measuring application development productivity. In Proceedings of the IBM Applications Development Symposium (pp. 83–92). link ↗ | Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report. link ↗ |
| Alias | FPA, function points, IFPUG sizing | debt metrics, code health scoring, maintenance burden assessment |
| 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. | 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. |
| ScholarGateConjunto de datos ↗ |
|
|