N-Fold inspection: a requirements analysis technique
Communications of the ACM
Object-oriented software engineering
Object-oriented software engineering
An improved inspection technique
Communications of the ACM
Does every inspection need a meeting?
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
Detecting defects in object-oriented designs: using reading techniques to increase software quality
Proceedings of the 14th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Building Knowledge through Families of Experiments
IEEE Transactions on Software Engineering
Experimentation in software engineering: an introduction
Experimentation in software engineering: an introduction
An encompassing life cycle centric survey of software inspection
Journal of Systems and Software
Proceedings of the 24th International Conference on Software Engineering
Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment
IEEE Transactions on Software Engineering
Software Requirements: Styles and Techniques
Software Requirements: Styles and Techniques
Comparing Inspection Strategies for Software Requirement Specifications
ASWEC '96 Proceedings of the 1996 Australian Software Engineering Conference
Meeting the Challenge of Large-Scale Software Development in an Educational Environment
CSEET '97 Proceedings of the 10th Conference on Software Engineering Education and Training
A New Software Engineering Program Structure and Initial Experiences
CSEET '00 Proceedings of the 13th Conference on Software Engineering Education & Training
An Experimental Comparison of Usage-Based and Checklist-Based Reading
IEEE Transactions on Software Engineering
Software Reliability Engineering: More Reliable Software Faster and Cheaper
Software Reliability Engineering: More Reliable Software Faster and Cheaper
Team-Based Fault Content Estimation in the Software Inspection Process
Proceedings of the 26th International Conference on Software Engineering
Improving object-oriented micro architectural design through knowledge systematization
ER'05 Proceedings of the 24th international conference on Perspectives in Conceptual Modeling
Automatic assessment of software documentation quality
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Hi-index | 0.00 |
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.