Salīdzināt metodes

	Programmatūras sarežģītības metriks	Tehniskā parāda mērīšana
Nozare	Programmatūras inženierija	Programmatūras inženierija
Saime	Process / pipeline	Process / pipeline
Izcelsmes gads	1976	1992
Autors	Thomas J. McCabe	Ward Cunningham
Tips	quantitative measurement	quantitative assessment
Pirmavots	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.
Citi nosaukumi	code complexity analysis, complexity measurement	debt metrics, code health scoring, maintenance burden assessment
Saistītās	4	4
Kopsavilkums	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.