השוואת שיטות
סקרו את השיטות שבחרתם זו לצד זו; שורות שבהן יש הבדל מודגשות.
| ניתוח נקודות פונקציה× | אומדן נקודות מקרה שימוש× | |
|---|---|---|
| תחום | הנדסת תוכנה | הנדסת תוכנה |
| משפחה | Process / pipeline | Process / pipeline |
| שנת המקור≠ | 1979 | 1993 |
| הוגה השיטה≠ | Allan Albrecht | Gustav Karner |
| סוג≠ | quantitative measurement | quantitative estimation |
| מקור מכונן≠ | 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 ↗ |
| כינויים | FPA, function points, IFPUG sizing | UCP, use case sizing, effort estimation |
| קשורות | 4 | 4 |
| תקציר≠ | 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. |
| ScholarGateמערך נתונים ↗ |
|
|