Evaluation of Usage-Based Reading—Conclusions after Three Experiments. Thelin, T., Runeson, P., Wohlin, C., Olsson, T., & Andersson, C. Empirical Software Engineering, 9(1-2):77--110, March, 2004. ![Evaluation of Usage-Based Reading—Conclusions after Three Experiments [link]](https://bibbase.org/img/filetypes/link.svg "link")
Paper doi abstract bibtex 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 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.
@article{ thelin_evaluation_2004,
title = {Evaluation of {Usage}-{Based} {Reading}—{Conclusions} after {Three} {Experiments}},
volume = {9},
issn = {1382-3256, 1573-7616},
url = {http://link.springer.com/article/10.1023/B%3AEMSE.0000013515.86806.d4},
doi = {10.1023/B:EMSE.0000013515.86806.d4},
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 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.},
language = {en},
number = {1-2},
urldate = {2014-07-22TZ},
journal = {Empirical Software Engineering},
author = {Thelin, Thomas and Runeson, Per and Wohlin, Claes and Olsson, Thomas and Andersson, Carina},
month = {March},
year = {2004},
keywords = {Empirical study, Programming Languages, Compilers, Interpreters, Software Engineering/Programming and Operating Systems, Software inspection, _done, _model_of_failures, reading technique, usage-based reading},
pages = {77--110}
}
Downloads: 0
{"_id":"pMQRbW8Kxk3gbRtEG","bibbaseid":"thelin-runeson-wohlin-olsson-andersson-evaluationofusagebasedreadingconclusionsafterthreeexperiments-2004","downloads":0,"creationDate":"2015-04-15T11:01:18.489Z","title":"Evaluation of Usage-Based Reading—Conclusions after Three Experiments","author_short":["Thelin, T.","Runeson, P.","Wohlin, C.","Olsson, T.","Andersson, C."],"year":2004,"bibtype":"article","biburl":"http://bibbase.org/zotero/troeger","bibdata":{"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 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","Runeson, Per","Wohlin, Claes","Olsson, Thomas","Andersson, Carina"],"author_short":["Thelin, T.","Runeson, P.","Wohlin, C.","Olsson, T.","Andersson, C."],"bibtex":"@article{ thelin_evaluation_2004,\n title = {Evaluation of {Usage}-{Based} {Reading}—{Conclusions} after {Three} {Experiments}},\n volume = {9},\n issn = {1382-3256, 1573-7616},\n url = {http://link.springer.com/article/10.1023/B%3AEMSE.0000013515.86806.d4},\n doi = {10.1023/B:EMSE.0000013515.86806.d4},\n 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 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.},\n language = {en},\n number = {1-2},\n urldate = {2014-07-22TZ},\n journal = {Empirical Software Engineering},\n author = {Thelin, Thomas and Runeson, Per and Wohlin, Claes and Olsson, Thomas and Andersson, Carina},\n month = {March},\n year = {2004},\n keywords = {Empirical study, Programming Languages, Compilers, Interpreters, Software Engineering/Programming and Operating Systems, Software inspection, _done, _model_of_failures, reading technique, usage-based reading},\n pages = {77--110}\n}","bibtype":"article","doi":"10.1023/B:EMSE.0000013515.86806.d4","id":"thelin_evaluation_2004","issn":"1382-3256, 1573-7616","journal":"Empirical Software Engineering","key":"thelin_evaluation_2004","keywords":"Empirical study, Programming Languages, Compilers, Interpreters, Software Engineering/Programming and Operating Systems, Software inspection, _done, _model_of_failures, reading technique, usage-based reading","language":"en","month":"March","number":"1-2","pages":"77--110","title":"Evaluation of Usage-Based Reading—Conclusions after Three Experiments","type":"article","url":"http://link.springer.com/article/10.1023/B%3AEMSE.0000013515.86806.d4","urldate":"2014-07-22TZ","volume":"9","year":"2004","bibbaseid":"thelin-runeson-wohlin-olsson-andersson-evaluationofusagebasedreadingconclusionsafterthreeexperiments-2004","role":"author","urls":{"Paper":"http://link.springer.com/article/10.1023/B%3AEMSE.0000013515.86806.d4"},"keyword":["Empirical study","Programming Languages","Compilers","Interpreters","Software Engineering/Programming and Operating Systems","Software inspection","_done","_model_of_failures","reading technique","usage-based reading"],"downloads":0},"search_terms":["evaluation","usage","based","reading","conclusions","three","experiments","thelin","runeson","wohlin","olsson","andersson"],"keywords":["empirical study","programming languages","compilers","interpreters","software engineering/programming and operating systems","software inspection","_done","_model_of_failures","reading technique","usage-based reading"],"authorIDs":[],"dataSources":["zHc5HdgBCDgkarEqH"]}