Difference between revisions of "Code Review Metrics"

From OWASP
Jump to: navigation, search
(New page: == Introduction == The objective of code review is to detect development errors which may cause vulnerabilities and hence give rise to an exploit. Code review can also be used to measure...)
 
Line 16: Line 16:
 
#Risk Density
 
#Risk Density
 
#Defect correction rate
 
#Defect correction rate
 +
#Path complexity/complexity-to-defect/cyclomatic complexity
  
  
Line 25: Line 26:
 
#Inspection Rate
 
#Inspection Rate
 
#Defect detection Rate
 
#Defect detection Rate
 +
#Code Coverage

Revision as of 12:13, 28 May 2008

Introduction

The objective of code review is to detect development errors which may cause vulnerabilities and hence give rise to an exploit. Code review can also be used to measure the progress of a development team in their practice of secure application development. It can pinpoint areas where the development practice is weak, areas where secure development practice is strong and give a security practitioner the ability to address the root cause of the weaknesses within a developed solution.

Metrics can also be taken relating to the performance of the code reviewers and the accuracy of the review process.



Secure Development Metrics

  1. Fault Density
  2. Risk Density
  3. Defect correction rate
  4. Path complexity/complexity-to-defect/cyclomatic complexity



Review Process Metrics

  1. Inspection Rate
  2. Defect detection Rate
  3. Code Coverage