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-17 من https://scholargate.app/ar/compare