Revision as of 15:13, 22 December 2023 edit Miniapolis (talk \| contribs) Edit filter managers, Autopatrolled, Administrators 73,123 edits →Explanation in terms of algebraic topology: Ce, fixes, links, rmv OR ← Previous edit		Revision as of 15:15, 22 December 2023 edit undo Miniapolis (talk \| contribs) Edit filter managers, Autopatrolled, Administrators 73,123 edits →Interpretation: Ce Next edit →
Line 78: === Interpretation === In his presentation '"Software Quality Metrics to Identify Risk'"<ref>{{cite web \|url=http://www.mccabe.com/ppt/SoftwareQualityMetricsToIdentifyRisk.ppt \|title=Software Quality Metrics to Identify Risk \|author=Thomas McCabe Jr. \|year=2008 \|archive-url=https://web.archive.org/web/20220329072759/http://www.mccabe.com/ppt/SoftwareQualityMetricsToIdentifyRisk.ppt \|archive-date=2022-03-29 \|url-status=live}}</ref> for the Department of Homeland Security, Tom McCabe introduces the following categorisation ~~to interpret~~of cyclomatic complexity: * 1 - 10: Simple procedure, little risk * 11 - 20: More complex, moderate risk * 21 - 50: Complex, high risk * > 50: Untestable code, very high risk ==Applications==

Cyclomatic complexity: Difference between revisions