Inspections are justified on an economic basis. The earlier that a software defect can be identified, the cheaper it is to fix. For example, if software developers in an organization tend to make the same types of errors on multiple projects, the organization may wish to understand the root cause for these problems and take action to improve the development process. This list is then passed onto the person who produced the work product. Only error detection.
Error correction is delegated to the person who produced the work product.
Organizations that conduct inspections have found that it is best to use the inspection process to improve the quality of a work product and not use the inspection for performance appraisal. They have found that if inspections are used to formally track performance of IS personnel for performance appraisals, then the inspections become too much of a high-stress activity and some personnel do not want to participate. Consider the work product guilty until proven innocent. For example, during analysis, it may be appropriate to conduct an inspection once the first draft of DFDs for a subset of the project have been completed. During programming, an inspection of code could be conducted once the program for a new module has been coded.