<P> An inspection is one of the most common sorts of review practices found in software projects . The goal of the inspection is to identify defects . Commonly inspected work products include software requirements specifications and test plans . In an inspection, a work product is selected for review and a team is gathered for an inspection meeting to review the work product . A moderator is chosen to moderate the meeting . Each inspector prepares for the meeting by reading the work product and noting each defect . In an inspection, a defect is any part of the work product that will keep an inspector from approving it . For example, if the team is inspecting a software requirements specification, each defect will be text in the document which an inspector disagrees with . </P> <P> The inspection process was developed in the mid-1970s and it has later been extended and modified . </P> <P> The process should have entry criteria that determine if the inspection process is ready to begin . This prevents unfinished work products from entering the inspection process . The entry criteria might be a checklist including items such as "The document has been spell - checked". </P> <P> The stages in the inspections process are: Planning, Overview meeting, Preparation, Inspection meeting, Rework and Follow - up . The Preparation, Inspection meeting and Rework stages might be iterated . </P>

Who fixes the defect by modifying the code