Advanced

Experimentation with usage-based reading

Thelin, Thomas LU ; Erlansson, M; Höst, Martin LU and Wohlin, Claes LU (2003) In Lecture Notes in Computer Science (Empirical Methods and Studies in Software Engineering) 2765. p.193-207
Abstract
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 from a user's point of view in a software document by using prioritized use cases. UBR has been evaluated in two previously conducted experiments, which investigate the prioritization of UBR and compare UBR against checklist-based reading (CBR). This chapter presents two controlled experiments with UBR on requirements... (More)
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 from a user's point of view in a software document by using prioritized use cases. UBR has been evaluated in two previously conducted experiments, which investigate the prioritization of UBR and compare UBR against checklist-based reading (CBR). This chapter presents two controlled experiments with UBR on requirements and design specifications. The experiments include individual preparation and inspection meeting, i.e. the first steps of the traditional inspection process. For the requirements inspection, UBR is evaluated against CBR, and for the design inspection, the amount of information needed in the use cases are studied. The studies were conducted in different environments with a total of about 100 students. The result from these experiments shows that UBR is not better than CBR for requirements inspections. Results from the experiment on design inspection indicate that use cases developed in advance are preferable compared to developing them as part of the preparation phase of the inspection. (Less)
Please use this url to cite or link to this publication:
author
organization
publishing date
type
Chapter in Book/Report/Conference proceeding
publication status
published
subject
in
Lecture Notes in Computer Science (Empirical Methods and Studies in Software Engineering)
volume
2765
pages
193 - 207
publisher
Springer
external identifiers
  • wos:000185939200011
  • scopus:35248865377
ISSN
1611-3349
0302-9743
ISBN
978-3-540-40672-3
DOI
10.1007/978-3-540-45143-3_11
language
English
LU publication?
yes
id
d073cee5-3127-4f1e-bfe4-22929b8271eb (old id 298459)
date added to LUP
2007-12-18 12:37:29
date last changed
2018-01-07 05:26:56
@inbook{d073cee5-3127-4f1e-bfe4-22929b8271eb,
  abstract     = {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 from a user's point of view in a software document by using prioritized use cases. UBR has been evaluated in two previously conducted experiments, which investigate the prioritization of UBR and compare UBR against checklist-based reading (CBR). This chapter presents two controlled experiments with UBR on requirements and design specifications. The experiments include individual preparation and inspection meeting, i.e. the first steps of the traditional inspection process. For the requirements inspection, UBR is evaluated against CBR, and for the design inspection, the amount of information needed in the use cases are studied. The studies were conducted in different environments with a total of about 100 students. The result from these experiments shows that UBR is not better than CBR for requirements inspections. Results from the experiment on design inspection indicate that use cases developed in advance are preferable compared to developing them as part of the preparation phase of the inspection.},
  author       = {Thelin, Thomas and Erlansson, M and Höst, Martin and Wohlin, Claes},
  isbn         = {978-3-540-40672-3},
  issn         = {1611-3349},
  language     = {eng},
  pages        = {193--207},
  publisher    = {Springer},
  series       = {Lecture Notes in Computer Science (Empirical Methods and Studies in Software Engineering)},
  title        = {Experimentation with usage-based reading},
  url          = {http://dx.doi.org/10.1007/978-3-540-45143-3_11},
  volume       = {2765},
  year         = {2003},
}