mastering code analysis metrics for alm (hugh wood)

Mastering code analysis metrics for ALMSharePoint Konferenz ErdingHugh Wood – Master Chief – Rencore AB - @HughAJWood

@HughAJWoodhttps//blog.spcaf.com [email protected]

Hugh WoodLeicester, EnglandLead Developer @ SPCAFMastering code analysis metrics for ALM - @HughAJWood

•What are they?•Who are they important to?•Where do they come from?•Looking deeper…

Static Code Analysis Metrics

Mastering code analysis metrics for ALM - @HughAJWood

What are they?


Who are they important to?


Developer

Architect

Project Manager

Business

Where do they come from?


FxCop

StyleCop

Digging deeper…


Visual Studio Metrics


Developer Friendly



Architect Friendly



Architect Friendly

Cyclomatic Complexity Density Ratio: (CC)11 / (LOC)21 = 0.5Class Coupling – Use DirectlyDepth Inheritance – Use DirectlyMaintainability Index – Use Directly



Project Manager Friendly

Cyclomatic Complexity Density Ratio: (CC)11 / (LOC)21 = 0.5Maintainability Index – Use Directly



Business FriendlyProject Complexity: (CC)11 / (LOC)21 = 0.5 x 100 = 50%

25% < Simple50% < Moderate70% < Complex71% > Unsupportable

Maintainability Index – Use Directly< 25% Expensive to maintain26~50% Moderately Expensive51~70% Low Expenditure71%+ Extremely Low Expenditure

Metrics outside ofVisual Studio


• Quality Metrics• Security Metrics• Research & Development metrics

Code Quality Metrics


• Defect Density (High/Medium per 1000 LOC)• Critical Defects / 1000 LOC• Uninspected Defects

Code Quality Metrics


What are Defects?

Code Security Metrics


• Information Security• System Security – System and Web

Research & DevelopmentEfficiency


• Cyclomatic Complexity• Comment Density

Policies & Thresholds


• ISO-9000 / ISO-27001• Defect limits• Developer Vectors• Defect Contingency• Development Language Segregation

Policies & Thresholds


• Assign a Defect Lead• Ignore only false positives• Use custom rule sets• Monitor and track all exceptions

Managing False Positives

Adjusting Project Plans


• Size of Code Base• Outstanding Defects• Number of Developers• Defects Per Developer by Category• Time to Inspect Defects (Average)• Time Scheduled per week for triage per Developer• Weeks until project completion

Adjusting Project Plans


Measure Defects and Metrics Over Time

Summary


• Ensure Defect and Metric policies are in place• Delegate the responsibility for collating data to a developer• Use code quality tools to keep records of progress• Use gathered metrics to inform Business• Decide on course of action and plan

mastering code analysis metrics for alm (hugh wood)

Technology