Code Review - Review Metrics and Review Frequency

Review Metrics are normally used to compute the efficiency of the process known as code review:

Rate of Inspection, usually measures every man-hour and is used calculate the review code. Fault Rate, usually measures the number of faults found for each man-hour and is used find faults. Fault Density, usually measures number of faults found for each review and is used to find faults in a given number of codes. Higher the fault density the more the number of faults are recognized which normally involves more efficient review procedures.

Two samples were used to exemplify the complications that can arise when assessing these metrics,

In the first sample a small number of lines of the code which are specific to the mission critical module was assessed by almost three reviewers to properly make sure that no faults were found. The outcome in high effect density shows the slow assessment rate and the fault rate which is 1 defect for each hour.

In the second sample amendments were made to the GUI dialog boxes, it resulted in one hundred and twenty lines of altered codes, to which some codes were created by GUI designers. One of the reviewers is allocated to confirm the alterations made and the same reviewer decides to overlook the designer who creates codes and only assess those codes following the GUI basics added. This outcome reveals low fault density, speed assessment rate and a fault rate of two faults per hour.

As apparent metrics are mostly dissimilar and as the code is not mission specific, the reviewer may be asked to devote lesser time in reviewing the alterations.

Review Frequency consists of effecient and speedy rules and regulations to determine the code frequency review.

The code frequency can be prejudiced by some issues and one has to make a decision contextually. Some issues to consider are:

Review type which requires additional time and attempts used for completing than required in the Lightweight Code Review. The code used to guide and recover team relationship that may be needed to perform regularly. Scope and Frequency of Code Changes are small frequent check-ins against the irregular and larger check-ins. Nature of development effort are open source and on and offshore reviews.

If your looking for the best code review tool on the web, please visit Smart Bear Software Inspection

Code Review - Review Metrics and Review Frequency