ScholarGate
دستیار

مقایسهٔ روش‌ها

روش‌های انتخابی خود را کنار هم مرور کنید؛ ردیف‌های متفاوت برجسته شده‌اند.

معیارهای پیچیدگی نرم‌افزار×مدل پیش‌بینی نقص×
حوزهمهندسی نرم‌افزارمهندسی نرم‌افزار
خانوادهProcess / pipelineProcess / pipeline
سال پیدایش19762005
پدیدآورThomas J. McCabeThomas Ostrand, Elaine Weyuker, Robert Bell
نوعquantitative measurementmachine learning model
منبع بنیادینMcCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320. DOI ↗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 ↗
نام‌های دیگرcode complexity analysis, complexity measurementfault prediction, bug prediction, defect classification
مرتبط44
خلاصه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.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مجموعه‌داده
  1. v1
  2. 3 منابع
  3. PUBLISHED
  1. v1
  2. 3 منابع
  3. PUBLISHED

رفتن به جست‌وجو دریافت اسلایدها

ScholarGateمقایسهٔ روش‌ها: Software Complexity Metrics · Defect Prediction Model. بازیابی‌شده در 2026-06-15 از https://scholargate.app/fa/compare