विधियों की तुलना करें

	सॉफ्टवेयर जटिलता मेट्रिक्स	तकनीकी ऋण मापन
क्षेत्र	सॉफ्टवेयर इंजीनियरिंग	सॉफ्टवेयर इंजीनियरिंग
परिवार	Process / pipeline	Process / pipeline
उद्भव वर्ष	1976	1992
प्रवर्तक	Thomas J. McCabe	Ward Cunningham
प्रकार	quantitative measurement	quantitative assessment
मौलिक स्रोत	McCabe, T. J. (1976). A complexity measure. IEEE Transactions on Software Engineering, 2(4), 308–320.	Cunningham, W. (1992). The WyCash Portfolio Management System. OOPSLA 92 Experience Report.
उपनाम	code complexity analysis, complexity measurement	debt metrics, code health scoring, maintenance burden assessment
संबंधित	4	4
सारांश	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.	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.