Review Metrics & their use

Review Metrics & their use

• Introduction : Technical reviews are one of many actions that are required as part of good software engineering practice.
• Each action requires dedicated human effort.
• The following review metrics can be collected for each review that is conducted
• Preparation effort, Ep—the effort (in person-hours) required to review a work product prior to the actual review meeting.
• Assessment effort, Ea— the effort (in person-hours) that is expending during the actual review
• Rework effort, Er— the effort (in person-hours) that is dedicated to the correction of those errors uncovered during the review
• Work product size, WPS—a measure of the size of the work product that has been reviewed (e.g., the number of UML models, or the number of document pages, or the number of lines of code)
• Minor errors found, Errminor—the number of errors found that can be categorized as minor (requiring less than some pre-specified effort to correct)
• Major errors found, Errmajor— the number of errors found that can be categorized as major (requiring more than some pre-specified effort to correct)