The browser you are using is not supported by this website. All versions of Internet Explorer are no longer supported, either by us or Microsoft (read more here: https://www.microsoft.com/en-us/microsoft-365/windows/end-of-ie-support).

Please use a modern browser to fully experience our website, such as the newest versions of Edge, Chrome, Firefox or Safari etc.

How much information is needed for usage-based reading? A series of experiments

På svenska

Author

  • Thomas Thelin
  • Per Runeson
  • Claes Wohlin
  • Thomas Olsson
  • Carina Andersson

Summary, in English

Software inspections are regarded as an important technique to detect faults throughout the software development process. The individual preparation phase of software inspections has enlarged its focus from only comprehension to also include fault searching. Hence, reading techniques to support the reviewers on fault detection are needed. Usage-based reading (UBR) is a reading technique, which focuses on the important parts of a software document by using prioritized use cases. This paper presents a series of three UBR experiments on design specifications, with focus on the third. The first experiment evaluates the prioritization of UBR and the second compares UBR against checklist-based reading. The third experiment investigates the amount of information needed in the use cases and whether a more active approach helps the reviewers to detect more faults. The third study was conducted at two different places with a total of 82 subjects. The general result from the experiments is that UBR works as intended and is efficient as well as effective in guiding reviewers during the preparation phase of software inspections. Furthermore, the results indicate that use cases developed in advance are preferable compared to developing them as part of the preparation phase of the inspection

Publishing year

2002

Language

English

Pages

127-138

Publication/Series

2002 International Symposium on Empirical Software Engineering Proceedings

Document type

Conference paper

Publisher

IEEE - Institute of Electrical and Electronics Engineers Inc.

Topic

  • Computer Science

Keywords

  • software development fault detection
  • software inspections
  • experiments
  • usage-based reading
  • checklist-based reading
  • design specifications
  • software document
  • prioritized use cases

Conference name

2002 International Symposium on Empirical Software Engineering Proceedings

Conference date

2002-10-03 - 2002-10-04

Conference place

Nara, Japan

Status

Published

ISBN/ISSN/Other

  • ISBN: 0-7695-1796-X