REVIEW PROCESS

These types of review comes under static testing technique.

1) Walkthrough

• In walkthrough, author guides the review team via the document to fulfil the common understanding and collecting the feedback.
• Walkthrough is not a formal process.
• In walkthrough, a review team does not require to do detailed study before meeting while authors are already in the scope of preparation.
• Walkthrough is useful for higher-level documents i.e requirement specification and architectural documents.

Goals of walkthrough

• Make the document available for the stakeholders both outside and inside the software discipline for collecting the information about the topic under documentation.
• Describe and evaluate the content of the document.
• Study and discuss the validity of possible alternatives and proposed solutions.

2) Inspection

• The trained moderator guides the Inspection. It is most formal type of review.
• The reviewers are prepared and check the documents before the meeting.
• In Inspection, a separate preparation is achieved when the product is examined and defects are found. These defects are documented in issue log.
• In Inspection, moderator performs a formal follow-up by applying exit criteria.

Goals of Inspection

• Assist the author to improve the quality of the document under inspection.
• Efficiently and rapidly remove the defects.
• Generating the documents with higher level of quality and it helps to improve the product quality.
• It learns from the previous defects found and prohibits the occurrence of similar defects.
• Generate common understanding by interchanging information.

3) Technical Review

• Technical review is a discussion meeting that focuses on technical content of the document. It is a less formal review.
• It is guided by a trained moderator or a technical expert.

Goals of technical review

• The goal is to evaluate the value of technical concept in the project environment.
• Build the consistency in the use and representation of the technical concepts.
• In early stages it ensures that the technical concepts are used correctly.
• Notify the participants regarding the technical content of the document.