قارن الطرق
راجع الطرق التي اخترتها جنبًا إلى جنب؛ الصفوف المختلفة مميَّزة.
| تقدير نقاط حالة الاستخدام× | نموذج التنبؤ بالعيوب× | |
|---|---|---|
| المجال | هندسة البرمجيات | هندسة البرمجيات |
| العائلة | Process / pipeline | Process / pipeline |
| سنة النشأة≠ | 1993 | 2005 |
| صاحب الطريقة≠ | Gustav Karner | Thomas Ostrand, Elaine Weyuker, Robert Bell |
| النوع≠ | quantitative estimation | machine learning model |
| المصدر التأسيسي≠ | 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 ↗ |
| الأسماء البديلة | UCP, use case sizing, effort estimation | fault prediction, bug prediction, defect classification |
| ذات صلة | 4 | 4 |
| الملخص≠ | 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. |
| ScholarGateمجموعة البيانات ↗ |
|
|