Evaluation of usage-based reading - Conclusions after three experiments
Thelin, Thomas LU ; Runeson, Per LU
; Wohlin, C
; Olsson, T
and Andersson, Carina
LU
(2004)
In Empirical Software Engineering
9(1-2).
p.77-110
- Abstract
- Software inspections have been introduced in software engineering in order to detect faults before testing is performed. Reading techniques provide reviewers in software inspections with guidelines on how they should check the documents under inspection. Several reading techniques with different 16 purposes have been introduced and empirically evaluated. In this paper, we describe a reading technique with the special aim to detect faults that are severe from a user's point of view. The reading technique is named usage-based reading (UBR) and it can be used to inspect all software artefacts. In the series of experiments, a high-level design document is used. The main focus of the paper is on the third experiment, which investigates the... (More)
- Software inspections have been introduced in software engineering in order to detect faults before testing is performed. Reading techniques provide reviewers in software inspections with guidelines on how they should check the documents under inspection. Several reading techniques with different 16 purposes have been introduced and empirically evaluated. In this paper, we describe a reading technique with the special aim to detect faults that are severe from a user's point of view. The reading technique is named usage-based reading (UBR) and it can be used to inspect all software artefacts. In the series of experiments, a high-level design document is used. The main focus of the paper is on the third experiment, which investigates the information needed for UBR in the individual preparation and the meeting of software inspections. Hence, the paper discusses (1) the series of three experiments of UBR, (2) the individual preparation of the third experiment, and (3) the meeting part of the third experiment. For each of these three parts, results are produced. The main results are (1) UBR is an efficient and effective reading technique that can be used for user-focused software inspections, (2) UBR is more efficient and effective if the information used for UBR is developed prior to, instead of during the individual preparation, and (3) the meeting affects the UBR inspection in terms of increased effectiveness and decreased efficiency. In summary, the empirical evidence shows that UBR is an efficient and effective reading technique to be used by software organizations that produce software for which the user perceived quality is important. (Less)
Please use this url to cite or link to this publication:
https://lup.lub.lu.se/record/284700
- author
- Thelin, Thomas
LU
; Runeson, Per
LU
; Wohlin, C
; Olsson, T
and Andersson, Carina
LU
- organization
- publishing date
- 2004
- type
- Contribution to journal
- publication status
- published
- subject
- keywords
- reading, usage-based, software inspection, empirical study, reading technique
- in
- Empirical Software Engineering
- volume
- 9
- issue
- 1-2
- pages
- 77 - 110
- publisher
- Springer
- external identifiers
-
- wos:000220373800003
- scopus:1442332441
- ISSN
- 1573-7616
- DOI
- 10.1023/B:EMSE.0000013515.86806.d4
- language
- English
- LU publication?
- yes
- id
- 0e449df9-2bfe-421d-a0b1-cf00c3b1e498 (old id 284700)
- date added to LUP
- 2016-04-01 12:15:48
- date last changed
- 2022-01-27 01:11:57
@article{0e449df9-2bfe-421d-a0b1-cf00c3b1e498,
abstract = {{Software inspections have been introduced in software engineering in order to detect faults before testing is performed. Reading techniques provide reviewers in software inspections with guidelines on how they should check the documents under inspection. Several reading techniques with different 16 purposes have been introduced and empirically evaluated. In this paper, we describe a reading technique with the special aim to detect faults that are severe from a user's point of view. The reading technique is named usage-based reading (UBR) and it can be used to inspect all software artefacts. In the series of experiments, a high-level design document is used. The main focus of the paper is on the third experiment, which investigates the information needed for UBR in the individual preparation and the meeting of software inspections. Hence, the paper discusses (1) the series of three experiments of UBR, (2) the individual preparation of the third experiment, and (3) the meeting part of the third experiment. For each of these three parts, results are produced. The main results are (1) UBR is an efficient and effective reading technique that can be used for user-focused software inspections, (2) UBR is more efficient and effective if the information used for UBR is developed prior to, instead of during the individual preparation, and (3) the meeting affects the UBR inspection in terms of increased effectiveness and decreased efficiency. In summary, the empirical evidence shows that UBR is an efficient and effective reading technique to be used by software organizations that produce software for which the user perceived quality is important.}},
author = {{Thelin, Thomas and Runeson, Per and Wohlin, C and Olsson, T and Andersson, Carina}},
issn = {{1573-7616}},
keywords = {{reading; usage-based; software inspection; empirical study; reading technique}},
language = {{eng}},
number = {{1-2}},
pages = {{77--110}},
publisher = {{Springer}},
series = {{Empirical Software Engineering}},
title = {{Evaluation of usage-based reading - Conclusions after three experiments}},
url = {{http://dx.doi.org/10.1023/B:EMSE.0000013515.86806.d4}},
doi = {{10.1023/B:EMSE.0000013515.86806.d4}},
volume = {{9}},
year = {{2004}},
}