Porównaj metody
Przeglądaj wybrane metody obok siebie; wiersze, które się różnią, są wyróżnione.
| Estymacja punktów przypadków użycia× | Model przewidywania defektów× | |
|---|---|---|
| Dziedzina | Inżynieria oprogramowania | Inżynieria oprogramowania |
| Rodzina | Process / pipeline | Process / pipeline |
| Rok powstania≠ | 1993 | 2005 |
| Twórca≠ | Gustav Karner | Thomas Ostrand, Elaine Weyuker, Robert Bell |
| Typ≠ | quantitative estimation | machine learning model |
| Źródło pierwotne≠ | 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 ↗ |
| Inne nazwy | UCP, use case sizing, effort estimation | fault prediction, bug prediction, defect classification |
| Pokrewne | 4 | 4 |
| Podsumowanie≠ | 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. |
| ScholarGateZbiór danych ↗ |
|
|