A software inspection aims to guarantee that a particular software artifact is complete, consistent, unambiguous, and correct enough to effectively support further system development. For instance, inspections have been used to improve the quality of a system’s design and code [Fagan76]. Typically, inspections require individuals to review a particular artifact, then meet as a team to discuss a...

Practically all inspection and review methods focus on projects for developing new software that involve numerous people, but software companies also have small projects on which only a few people are working, e.g. maintenance-oriented changes to existing software systems. Unfortunately, these small projects do not necessarily have the power to implement inspections efficiently. This paper rais...

The Product Quality Research Institute, in conjunction with the Food and Drug Administration, conducted an anonymous, electronic survey of the biological products manufacturing industry inspected by Team Biologics, with emphasis in obtaining industry input on inspection and compliance aspects of program operations. Representatives from all of the product-specific manufacturing industries inspec...

We examine the interplay between two important decisions that impact environmental performance in a production setting: inspections performed by a regulator and noncompliance disclosure by a production …rm. To preempt the penalty that will be levied once a compliance violation is discovered in an inspection, the …rm dynamically decides whether it should disclose a random occurrence of noncompli...

medication error (me) is the most common preventable cause of adverse drug events which negatively affects patient safety. inadequate, low-quality studies plus wide estimation variations in me from developing countries including iran, decreases the reliability of me evaluations. to clarify sources, underreporting reasons and preventive measures of mes, we reviewed iran current available literat...

Software inspections are a software engineering “best practice” for defect detection and rework reduction. In this paper, we describe our initial empirical evaluation with using a tool aiming to provide Internet groupware support for distributed software inspections. The tool is based on a restructured inspection process to reduce synchronization and coordination problems.

For two decades, software inspections have proven e ective for detecting defects in software. We have reviewed the di erent ways software inspections are done, created a taxonomy of inspection methods, and examined claims about the cost-e ectiveness of di erent methods. We detect a disturbing pattern in the evaluation of inspection methods. Although there is universal agreement on the e ectiven...

We study the case of ‘‘inspect-all’’ policy, using off-line quality inspections to prevent non-conforming items from reaching the final consumer, in domains where an item is rejected upon first ‘‘failure’’ classification. Given a set of inspections with known inspection costs and error probabilities of two types (classifying conforming items as non-conforming and vice versa), the goal is to fin...

California hospital construction projects are large, complex, and extremely difficult projects to execute and navigate successfully. One of the primary reasons for this is the OSHPD permit, review, and inspection process. The quality control rigor imposed by this third party inspection procedure has caused great angst amongst most general contractors and subcontractors. This study examined over...

This paper uses Baudrillard’s orders-of-simulacra theories to investigate the use of inspections at the Hudson’s Bay Company. These inspections were comparable to “modern” internal audits. They were being conducted in 1871, 50 years prior to the accepted date of the arrival of modern internal auditing. Inspections were started as the Hudson’s Bay Company was getting easier to manage, which was ...