Next: Reading Techniques
Up: Introduction to the Experiment
Previous: Separation of Reading
Typically, reviewers are not told how to read, what
to look for, or for what they are really responsible. These issues
can be used to classify and characterize reading techniques
[PVB]:
- Strategy
One way to characterize a reading technique is the
strategy
which is used. There are several strategies for
detecting defects in a document. The characteristic which is
used here is the degree of prescriptiveness. We can distinguish
between systematic and non-systematic
techniques to finding defects.
- Reviewer responsibility
A second way of characterizing reading techniques
is the responsibility
each reviewer has to find defects of a specific class.
The characteristic which is used here is breadth of scope. We can
distinguish between a specific and a
general approach to find defects.
- Coordination policy
The third way of characterizing reading techniques is
the coordination
policy: How are different responsibilities assigned to
review team members? The characteristic which is used here is
the degree of overlap. We can distinguish between distinct
responsibilities and identical responsibilities.
In many cases reading as it is used today in practice can be
characterized as:
- non-systematic
- general
- identical
The goal of our research is the development of reading techniques
that are:
- systematic - the reader knows how to read
- specific - the reader is focused to look for a
specific defect class
- distinct - there is minimal overlap among several readers.
In the rest of this section we will explain how reading can be
integrated into the software development process and the research that
has already been done.
Generated by latex2html-95.1
Mon Jun 24 13:58:35 EDT 1996
Web Accessibility