ScholarGate
المساعد

قارن الطرق

راجع الطرق التي اخترتها جنبًا إلى جنب؛ الصفوف المختلفة مميَّزة.

قياس الدَّين التقني×مقاييس تعقيد البرمجيات×
المجالهندسة البرمجياتهندسة البرمجيات
العائلةProcess / pipelineProcess / pipeline
سنة النشأة19921976
صاحب الطريقةWard CunninghamThomas J. McCabe
النوعquantitative assessmentquantitative measurement
المصدر التأسيسيCunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report. link ↗McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320. DOI ↗
الأسماء البديلةdebt metrics, code health scoring, maintenance burden assessmentcode complexity analysis, complexity measurement
ذات صلة44
الملخصTechnical debt represents accumulated shortcuts, deferred maintenance, and design compromises that incur future costs through slower development, higher defect rates, and deployment difficulty. Introduced by Ward Cunningham (1992), technical debt measurement quantifies these burdens using metrics like code complexity, duplication, test coverage gaps, and maintainability indices. Organizations use debt measurement to balance immediate delivery with long-term sustainability.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.
ScholarGateمجموعة البيانات
  1. v1
  2. 3 المصادر
  3. PUBLISHED
  1. v1
  2. 3 المصادر
  3. PUBLISHED

انتقل إلى البحث تنزيل الشرائح

ScholarGateقارن الطرق: Technical Debt Measurement · Software Complexity Metrics. استُرجع بتاريخ 2026-06-17 من https://scholargate.app/ar/compare