ScholarGate
Assistant

Comparer des méthodes

Examinez les méthodes sélectionnées côte à côte ; les lignes qui diffèrent sont mises en évidence.

Estimation par points de cas d'utilisation×Modèle de prédiction de défauts×
DomaineGénie logicielGénie logiciel
FamilleProcess / pipelineProcess / pipeline
Année d'origine19932005
Auteur d'origineGustav KarnerThomas Ostrand, Elaine Weyuker, Robert Bell
Typequantitative estimationmachine learning model
Source fondatriceKarner, 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 ↗
AliasUCP, use case sizing, effort estimationfault prediction, bug prediction, defect classification
Apparentées44
Résumé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.
ScholarGateJeu de données
  1. v1
  2. 3 Sources
  3. PUBLISHED
  1. v1
  2. 3 Sources
  3. PUBLISHED

Aller à la recherche Télécharger les diapositives

ScholarGateComparer des méthodes: Use Case Point Estimation · Defect Prediction Model. Consulté le 2026-06-17 sur https://scholargate.app/fr/compare