Face-to-face (F2F) meeting is the cornerstone of the traditional inspection process. However, F2F meetings hinder the applicability of software inspections in the context of distributed software development. We present a preliminary study where we compare six collocated versus six distributed inspections. In the former group team members physically meet and discuss in a collocated manner, while...

We consider a game between two polluting firms and an inspection agency, which can inspect ambient pollution levels before inspecting individual firms, but without committing itself to announced inspection probabilities. Without ambient inspections, we have a unique equilibrium. With ambient inspections, we obtain several equilibria, depending on the relative values of the environmental cost of...

0 7 4 0 7 4 5 9 / 0 1 / $ 1 0 . 0 0 © 2 0 0 1 I E E E One example of software process improvement is the development and execution of inspections of software development documents as a mature technique to detect and prevent software defects. Part of an inspection is a meeting where the participants log detected defects and search for more defects. Unfortunately, the effectiveness and efficiency...

Fagan inspections are a structured review of software development documents that consists of individual preparation, a meeting and rework by the author of the document. The meeting is used to log the defects found in preparation and to search for more defects. The effectiveness and efficiency of the meeting is often low as compared to that of the preparation. This paper describes the results of...

Software inspections are formal evaluations of the intermediate work products (artifacts) of the development process. These artifacts are examined to ensure that a high quality work-product is delivered to the testers and ultimately to the end-users of the software product. The crucial role of inspections in determining quality of the software makes it important to assess the effectiveness of i...

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...