An experimental comparison of usage-based and checklist-based reading

Thelin, Thomas; Runeson, Per; Wohlin, Claes

doi:10.1109/tse.2003.1223644

Cited by 113 publications

(94 citation statements)

References 35 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…We use the results of an external replication of the UBR experiment as described in [ 27] and [ 28]. In addition to CBR and UBR inspection we introduce a slightly adjusted version of CBR, namely CBR-tc (CBR using tailoring approaches to prioritize requirements and corresponding system functions).…”

Section: Research Questionsmentioning

confidence: 99%

“…The experiment setup contains two different types of variables [ 27] [ 28], (a) independent and (b) dependent variables. We use the reading technique used as independent variable, i.e.…”

Section: Variablesmentioning

confidence: 99%

“…to investigate the benefits of the individual RT approaches. Examples for empirical studies are: checklist-based RT (CBR) [ 15][ 27] and usage-based RT (UBR) [ 23][ 24] [ 25][ 26] [ 27]. Gilb et al presents an overview and comparison of CBR and SBR [ 7].…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Investigating the Impact of Active Guidance on Design Inspection

Winkler

Biffl

Thurnher

2005

Product Focused Software Process Improvement

View full text Add to dashboard Cite

Abstract. Software inspection helps to improve the quality of software products early in the development process. For design inspection recent research showed that usage-based reading of documents is more effective and efficient than traditional checklists. Usage-based reading guides actively the inspector with pre-sorted use cases, while traditional checklists let the inspector figure out how best to proceed. This paper investigates the impact of active guidance on an inspection process: We introduced checklists that give the inspector a process to follow, which should be as flexible as traditional checklists but more efficient. We compared the performance of this approach in a controlled experiment in an academic environment with traditional checklist and usage-based reading. Main results of the investigation are (a) checklists with active guidance are significantly more efficient than traditional checklists for finding major defects and (b) usage-based reading is more effective and efficient than both types of checklists. These results suggest that active guidance improves the efficiency of inspectors while the upfront investment into usage-based reading pays off during inspection.

show abstract

Section: Research Questionsmentioning

confidence: 99%

“…The experiment setup contains two different types of variables [ 27] [ 28], (a) independent and (b) dependent variables. We use the reading technique used as independent variable, i.e.…”

Section: Variablesmentioning

confidence: 99%

See 1 more Smart Citation

Investigating the Impact of Active Guidance on Design Inspection

Winkler

Biffl

Thurnher

2005

Product Focused Software Process Improvement

View full text Add to dashboard Cite

show abstract

“…"Reading by Stepwise Abstraction" [11] is a review technique advocated by the Cleanroom community, which requires an inspector to read a sequence of statements in the code and to abstract the functions these statements compute. Traceability-based Reading [6] is to describe how to perform consistency and correctness checks among various working products. The method is divided into Vertical and Horizontal Reading.…”

Section: Related Workmentioning

confidence: 99%

A review approach to detecting structural consistency violations in programs

Chen

Liu

Nagoya

2005

Fourth Annual ACIS International Conference on Computer and Information Science (ICIS'05)

View full text Add to dashboard Cite

show abstract

“…According to experiments reported in (Basili et al 1996), less experienced inspectors in particular considered perspectives more helpful than checklists. Thelin, Runeson and Wohlin (2003) have introduced an usage-based reading technique that helps inspectors to focus on the most important issues. Their research also suggests that the usage-based reading technique is more efficient than traditional checklists.…”

Section: User Rolementioning

confidence: 99%

Improving software inspection process with patterns

Harjumaa

Tervonen

Vuorio³

Fourth International Conference onQuality Software, 2004. QSIC 2004. Proceedings.

View full text Add to dashboard Cite

The quality of a software product depends largely on the quality of the process that is used to develop it. In small software companies, the development process may be informal or even ad hoc, which causes uncertainty and variation in the product quality. However, quality issues are as important in small companies as in their larger counterparts. To sustain their dynamics and competitiveness, small organizations need to concentrate on the most effective quality assurance methods.Software inspection is a proven method for improving product quality and it provides a very costeffective way for small companies to improve their development processes. This study introduces a framework for adjusting the inspection process for the organization's specific needs and evaluating its capabilities. The main focus of this work, however, is on refining and improving the inspection process. The improvement is guided by concrete instructions that are documented as process patterns. The pattern approach has already been used successfully in several other areas of software engineering. Patterns aim at capturing the best practices of software development and transferring this knowledge between people or organizations.The framework for inspection process capability originates from the literature relating to different types of peer review methods and experiments with flexible and tool-supported inspections in small companies. Furthermore, generic process improvement models are studied to find a feasible structure for the framework. As a result of the analysis, the i3 capability model is introduced. The feasibility of the model has been investigated in real-life software organizations carrying out inspections.After the capability evaluation, the inspection process can be upgraded with the aid of improvement patterns, which provide structured and easy-to-follow guidelines for implementing improvements. An initial list of patterns, describing solutions to the most common problems confronted in the establishment of inspections, is extracted from related inspection research and an industrial experiment.The contributions of this study are, first, the new view of the inspection process, based on the fundamental activities that are performed during an inspection instead of a series of stages, as it is usually presented. An activity-based process description enables tailoring of the process for organization-specific needs and its targeted improvement. Second, the study introduces a practical, lightweight method for implementing the improvement. Patterns are especially suitable in companies where resources are limited and full-scale improvement programmes cannot be initiated. Furthermore, the generic process improvement models do not provide detailed information on how improvements should be carried out, and the pattern approach represents a promising method for that. Third, the inspection process currently does not have a very significant role in generic software process improvement models; this study helps in outlining the importance ...

show abstract

An experimental comparison of usage-based and checklist-based reading

Cited by 113 publications

References 35 publications

Investigating the Impact of Active Guidance on Design Inspection

Investigating the Impact of Active Guidance on Design Inspection

A review approach to detecting structural consistency violations in programs

Improving software inspection process with patterns

Contact Info

Product

Resources

About