Review Process and Types of Review Process

What is a Review Process?

A review is a static testing technique in which a work product (requirements, design, or code) is examined by individuals other than the author to identify defects early, without executing the software. Reviews are one of the most cost-effective ways to catch defects, since fixing an issue in a document is far cheaper than fixing it after coding or release.

Typical Review Process

• Planning: The moderator defines the scope, participants, and schedule for the review.
• Kick-off: The objectives and work product are introduced to the review team.
• Individual Preparation: Reviewers examine the work product independently and note issues.
• Review Meeting: The team discusses findings and logs defects.
• Rework: The author fixes the identified defects.
• Follow-up: The moderator verifies that all defects have been resolved.

Types of Review Process

• Informal Review: A quick, unstructured review with no formal process or documentation, often a simple peer check.
• Walkthrough: The author guides reviewers through the work product to gather feedback.
• Technical Review: A structured review by technical peers focused on technical correctness and adherence to standards.
• Inspection: The most formal type of review, following a strict process with defined roles, checklists, and metrics.