Inspection

Inspection is a more formal way of reviewing a meeting process. In inspection the documents are checked thoroughly and reviewed by reviewer’s before the meeting. it basically involves peers to examine the product or software.

A preparation is been carried out separately in which the product is been examined properly and scanned for any defects or errors. The process of inspection is led and done by trained moderators. A formal follow up is carried out by this trained moderators. Inspection is been done to improve the product quality more efficiently.

Objectives of Inspection:

Following are some of the objectives of Inspection.

• To efficiently improve the quality of a software or product.
• To create common understanding between individuals who are been involved in the inspection.
• To remove defects and errors as early as possible.
• To learn and improve from defects which are been found during inspection.
• Helping author to improve and increase the quality of product which is been developed.

Prerequisite:

• What is software engineering?
• What is the difference between an Inspection and Walkthrough?
   

The walkthrough is a review meeting process but it is different from the  Inspection, as it does not involve any formal process i.e. it is a nonformal process. Basically, the walkthrough [review meeting process] is started by the Author of the code.

In the walkthrough, the code or document is read by the author, and others who are present in the meeting can note down the important points or can write notes on the defects and can give suggestions about them. The walkthrough is an informal way of testing, no formal authority is been involved in this testing.

As there is an informal way of testing involved so there is no need for a moderator while performing a walkthrough. We can call a walkthrough an open-ended discussion, it does not focus on the documentation. Defect tracking is one of the challenging tasks in the walkthrough.