قارن الطرق

	قياس الدَّين التقني	التحليل الساكن للتعليمات البرمجية
المجال	هندسة البرمجيات	هندسة البرمجيات
العائلة	Process / pipeline	Process / pipeline
سنة النشأة	1992	2001
صاحب الطريقة	Ward Cunningham	David Engler and William Pugh
النوع	quantitative assessment	automated analysis
المصدر التأسيسي	Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report.	Chess, B., & West, J. (2007). Secure Programming with Static Analysis. Addison-Wesley Professional.
الأسماء البديلة	debt metrics, code health scoring, maintenance burden assessment	static analysis, code inspection, automated review
ذات صلة	4	4
الملخص	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.	Static code analysis automatically examines source code without execution, detecting potential bugs, security vulnerabilities, code smells, and style violations. Pioneered by Engler and Pugh (2001), automated analysis tools scan codebases at scale, identifying defect patterns faster than manual review. Organizations integrate static analysis into continuous integration pipelines to prevent defects early.