Usage-based readingan experiment to guide reviewers with use cases

Abstract Reading methods for software inspections are used for aiding reviewers to focus on special aspects in a software artefact. Many experiments were conducted for checklist-based reading and scenario-based reading concluding that the focus is important for software reviewers. This paper describes and evaluates a reading technique called usage-based reading (UBR). UBR utilises prioritised use cases to guide reviewers through an inspection. More importantly, UBR drives the reviewers to focus on the software parts that are most important for a user. An experiment was conducted on 27 third year Bachelor's software engineering students, where one group used use cases sorted in a prioritised order and the control group used randomly ordered use cases. The main result is that reviewers in the group with prioritised use cases are significantly more efficient and effective in detecting the most critical faults from a user's point of view. Consequently, UBR has the potential to become an important reading technique. Future extensions to the reading technique are suggested and experiences gained from the experiment to support replications are provided.

[1]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.

[2]  John D. Musa,et al.  Software reliability engineering : more reliable software, faster development and testing , 1999 .

[3]  T. Saaty,et al.  The Analytic Hierarchy Process , 1985 .

[4]  Claes Wohlin,et al.  Statistical Usage Testing for Software Reliability Control , 1995, Informatica.

[5]  Per Runeson A new software engineering programme - structure and initial experiences , 2000, Thirteenth Conference on Software Engineering Education and Training.

[6]  Thomas Gilb,et al.  Software Inspection , 1994 .

[7]  Lawrence G. Votta,et al.  Does every inspection need a meeting? , 1993, SIGSOFT '93.

[8]  Joachim Karlsson,et al.  A Cost-Value Approach for Prioritizing Requirements , 1997, IEEE Softw..

[9]  Walter F. Tichy,et al.  Should Computer Scientists Experiment More? , 1998, Computer.

[10]  S. Siegel,et al.  Nonparametric Statistics for the Behavioral Sciences , 2022, The SAGE Encyclopedia of Research Design.

[11]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[12]  Per Runeson,et al.  Derivation of an integrated operational profile and use case model , 1998, Proceedings Ninth International Symposium on Software Reliability Engineering (Cat. No.98TB100257).

[13]  Colin Atkinson,et al.  An experimental comparison of reading techniques for defect detection in UML design documents , 2000, J. Syst. Softw..

[14]  David Lorge Parnas,et al.  Active design reviews: principles and practices , 1985, ICSE '85.

[15]  Forrest Shull,et al.  How perspective-based reading can improve requirements inspections , 2000, Computer.

[16]  Adam A. Porter,et al.  Comparing Detection Methods for Software Requirements Inspections: A Replicated Experiment , 1995, IEEE Trans. Software Eng..

[17]  Matthias Jarke,et al.  Scenarios in System Development: Current Practice , 1998, IEEE Softw..

[18]  Robert G. Ebenau,et al.  Software Inspection Process , 1993 .

[19]  Michael E. Fagan Advances in software inspections , 1986, IEEE Transactions on Software Engineering.

[20]  Harlan D. Mills,et al.  Structured programming - theory and practice , 1979, The systems programming series.

[21]  Forrest Shull,et al.  Building Knowledge through Families of Experiments , 1999, IEEE Trans. Software Eng..

[22]  Oliver Laitenberger,et al.  Perspective-based reading of code documents at Robert Bosch GmbH , 1997, Inf. Softw. Technol..

[23]  Victor R. Basili,et al.  The role of experimentation in software engineering: past, current, and future , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[24]  Michael Fagan Design and Code Inspections to Reduce Errors in Program Development , 1976, IBM Syst. J..