Comparar métodos
Revisa los métodos seleccionados uno junto a otro; las filas que difieren aparecen resaltadas.
| Estimación por Puntos de Caso de Uso× | Modelo de Predicción de Defectos× | |
|---|---|---|
| Campo | Ingeniería de software | Ingeniería de software |
| Familia | Process / pipeline | Process / pipeline |
| Año de origen≠ | 1993 | 2005 |
| Autor original≠ | Gustav Karner | Thomas Ostrand, Elaine Weyuker, Robert Bell |
| Tipo≠ | quantitative estimation | machine learning model |
| Fuente seminal≠ | Karner, G. (1993). Resource estimation for objectory projects. Objective Systems SF, Inc. link ↗ | Ostrand, T. J., Weyuker, E. J., & Bell, R. M. (2005). Predicting the location and number of faults in large software systems. IEEE Transactions on Software Engineering, 31(4), 340–355. DOI ↗ |
| Alias | UCP, use case sizing, effort estimation | fault prediction, bug prediction, defect classification |
| Relacionados | 4 | 4 |
| Resumen≠ | 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. | Defect prediction models forecast the likelihood of software faults in code modules using statistical or machine learning approaches. Pioneered by Ostrand, Weyuker, and Bell (2005), these models correlate code metrics (complexity, churn, coupling) with historical defect data to identify high-risk components. Organizations use predictions to allocate testing resources, guide code review, and prioritize refactoring. |
| ScholarGateConjunto de datos ↗ |
|
|