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

Software quality can be defined as the customers' perception of how a system works. Inspection is a method to monitor and control the quality throughout the development cycle. Reading techniques applied to inspections help reviewers to stay focused on the important parts of an artifact when ins...

Full description

Saved in:
Bibliographic Details
Published in:IEEE transactions on software engineering 2003-08, Vol.29 (8), p.687
Main Authors: Thelin, Thomas, Runeson, Per, Wohlin, Claes
Format: Article
Language:English
Subjects:
Comparative analysis
Design specifications
Experiments
Inspections
Methods
Reading
Software development
Software engineering
Software quality
Software reviews
Statistical analysis
Studies
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Software quality can be defined as the customers' perception of how a system works. Inspection is a method to monitor and control the quality throughout the development cycle. Reading techniques applied to inspections help reviewers to stay focused on the important parts of an artifact when inspecting. However, many reading techniques focus on finding as many faults as possible, regardless of their importance. Usage-based reading helps reviewers to focus on the most important parts of a software artifact from a user's point of view. This paper presents an experiment which compares usage-based and checklist-based reading. The results show that reviewers applying usage-based reading are more efficient and effective in detecting the most critical faults from a user's point of view than reviewers using checklist-based reading. Usage-based reading may be preferable for software organizations that utilize or will start utilizing use cases in their software development. [PUBLICATION ABSTRACT]
ISSN:0098-5589
1939-3520
DOI:10.1109/TSE.2003.1223644