ScholarGate
Asistent

Uporedite metode

Pregledajte izabrane metode jednu pored druge; redovi koji se razlikuju su istaknuti.

Model za predviđanje defekata×Метрике сложености софтвера×
OblastSoftversko inženjerstvoSoftversko inženjerstvo
PorodicaProcess / pipelineProcess / pipeline
Godina nastanka20051976
TvoracThomas Ostrand, Elaine Weyuker, Robert BellThomas J. McCabe
Tipmachine learning modelquantitative measurement
Temeljni izvorOstrand, 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 ↗McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320. DOI ↗
Drugi nazivifault prediction, bug prediction, defect classificationcode complexity analysis, complexity measurement
Srodne44
SažetakDefect 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.Software complexity metrics quantify the structural and operational difficulty of code through numerical measurements. Introduced by Thomas McCabe in 1976, cyclomatic complexity became the foundational approach. These metrics assess maintainability, testability, and defect risk, enabling teams to identify problematic code regions and guide refactoring efforts.
ScholarGateSkup podataka
  1. v1
  2. 3 Izvori
  3. PUBLISHED
  1. v1
  2. 3 Izvori
  3. PUBLISHED

Idi na pretragu Preuzmi slajdove

ScholarGateUporedite metode: Defect Prediction Model · Software Complexity Metrics. Preuzeto 2026-06-15 sa https://scholargate.app/sr/compare