Software inspections improve quality by finding errors earlier, shortening development time and reducing maintenance needs later. Inspections involve an author, moderator, reader, recorder and inspectors reviewing software artifacts like designs or code. Effective inspections of user interfaces involve walking through usage scenarios to simulate interactions. All issues found are recorded in detail so the author can address them. Tracking inspection results helps organizations assess quality and determine the most effective inspection methods.

1. Improving Quality Through
Software Inspections
Software Project Management
Student:
Vlad-Andrei STĂICULESCU

2. Summary
 Benefits
of Inspections
 Inspections, Walkthroughs, and Reviews
 Inspecting for Usability
 Keeping Records

3. Benefits of Inspections



Inspections shorten delivery time by reducing the
time spent in the integration and system test/debug
phases
Better quality in the completed product saves on
maintenance time
Inspections tend to reveal different kinds of errors
than do testing activities

4. Inspections, Walkthroughs, and
Reviews
 An
inspection team consists of 3-8 members
and includes these roles:
–
–
–
–
–
Moderator
Author
Reader
Recorder
Inspector

5. Inspecting for Usability

The usability inspection process differs somewhat
from that of other software artifacts. Participants are
not expected to prepare for the inspection by
examining the materials in advance. The best
inspection results are obtained by making two
passes through the user interface. In the first pass,
the interface is "executed" by walking through
various usage scenarios. This can be simulated with
paper prototypes if an operational interface is not yet
available.

6. Keeping Records



Each error found is described in enough detail that the author
can refer to this list during the rework step and understand the
point that was raised
As inspectors raise issues during the review meeting, the
recorder enters them on the issues list
While results will vary from one organization to the next for
many reasons, if you begin recording and analyzing your
inspection data, you will be able to determine which methods
work best for you and you can begin to assess the quality of
your work products
Source: http://www.processimpact.com/articles/inspects.html

7. Keeping Records



Each error found is described in enough detail that the author
can refer to this list during the rework step and understand the
point that was raised
As inspectors raise issues during the review meeting, the
recorder enters them on the issues list
While results will vary from one organization to the next for
many reasons, if you begin recording and analyzing your
inspection data, you will be able to determine which methods
work best for you and you can begin to assess the quality of
your work products
Source: http://www.processimpact.com/articles/inspects.html