Inspection is necessary to review a product. In software development, software or code inspection refers to peer review of any product by experts who try to unravel defects, if any, present in the system using a well defined method. In an inspection process, the objective is to identify defects, and the inspected parts are generally SRS(Software Requirements Specifications) documents and test plans.
The process of inspection begins like this- a team gathers to plan about the inspection process. A moderator is chosen in the team to carry out the meeting. There is an inspector who approves the product, so when the team meeting is done, they carry out a detailed study about the product and noting the defects as well. So the software inspection is a walk through which is conducted in a well planned manner.
An inspection process passes through the following stages :
the moderator plans the activities to be performed during inspection.
An overview meeting intends to disseminate information regarding the background of the product under review.
Identify possibility of occurrence of a certain defect.
During this phase, the reader reads through the product and the inspector tries to point out the defects.
Based on the inspection meeting, the moderator makes necessary changes to the product.
The changes made are thus reviewed by the author.
The comprises of the following roles assigned to team members.
Author is the person who has created the work product, that is to be inspected.
Moderator is the planner of the inspection. He is basically the coordinator and the leader.
The person responsible for reading the documents.
This person is the one who records the defects that are being discovered.
Responsible for examining the product and identify possible defects.
Entry Criteria- It can be defined as the fulfilment of minimum set of conditions to begin with the process of testing work. The various conditions may be installation and configuration of hardware and software applications as well.
Exit Criteria - To close the project, all necessary tasks should have met by now. All test plans have been executed, requirement coverage has been done, and all the risk affected areas have been covered.