The idea behind perspective-based reading is that various customers of a
product (here: requirements) should read the document from a
particular point of view. For perspective-based reading we use the
different roles within the software development process as a model.
The roles represent the different points of views. We chose the
roles tester, designer and user.
To support the reader throughout the reading process we have developed
operational descriptions (called scenarios) for each role. A scenario
consists of a set of questions and activities that tells the reader
what he should do and how to read the document.
While answering the different questions and carrying out the
activities the reader should write down all the defects he finds
within the product.
Using the classification scheme introduced in chapter 2, perspective-based
reading is a technique that is
The reader knows how he should read the document
The reader is only responsible for his role and the defects that can be detected with regard to his particular point of view.
Each reader has his own role. We assume that there is a broader coverage between them as far as defects from different defect classes are concerned.