Towards an inspection technique for use case models

A use case model describes the functional requirements of a software system and is used as input to several activities in a software development project. The quality of the use case model therefore has an important impact on the quality of the resulting software product. Software inspection is regarded as one of the most efficient methods for verifying software documents. There are inspection techniques for most documents produced in a software development project, but no comprehensive inspection technique exists for use case models. This paper presents a taxonomy of typical defects in use case models and proposes a checklist-based inspection technique for detecting such defects. This inspection technique was evaluated in two studies with undergraduate students as subjects. The results from the evaluations indicate that inspections are useful for detecting defects in use case models and motivate further studies to improve the proposed inspection technique.

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

[2]  Magne Jørgensen,et al.  Estimating Software Development Effort Based on Use Cases-Experiences from Industry , 2001, UML.

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

[4]  James Miller,et al.  Further Experiences with Scenarios and Checklists , 1998, Empirical Software Engineering.

[5]  Ian Sommerville,et al.  Software engineering (5th ed.) , 1995 .

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

[7]  Magne Jørgensen,et al.  Quality and Understandability of Use Case Models , 2001, ECOOP.

[8]  Eugene Miya,et al.  On "Software engineering" , 1985, SOEN.

[9]  Russell R. Hurlbut.  A Survey of Approaches For Describing and Formalizing Use Cases , 1998 .

[10]  Ola Blomkvist,et al.  An Extended Replication of an Experiment for Assessing Methods for Software Requirements Inspections , 1998, Empirical Software Engineering.

[11]  Edward Yourdon,et al.  Structured walkthroughs , 1978 .

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

[13]  Mordechai Ben-Menachem,et al.  Writing effective use cases , 2001, SOEN.

[14]  Daryl Kulak,et al.  Use cases: requirements in context , 2000, SOEN.

[15]  Claes Wohlin,et al.  An Experimental Comparison of Usage-Based and Checklist-Based Reading , 2003, IEEE Trans. Software Eng..

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

[17]  Frank Armour,et al.  Advanced Use Case Modeling: Software Systems , 2000 .

[18]  W BoyerKenneth.  Advanced use case modeling , 2002 .

[19]  Geri Schneider,et al.  Applying Use Cases: A Practical Guide , 1998 .

[20]  Khaled El Emam,et al.  Evaluating Capture-Recapture Models with Two Inspectors , 2001, IEEE Trans. Software Eng..

[21]  Jeffrey C. Carver,et al.  Evolving a Set of Techniques for OO Inspections , 1999 .

[22]  D. Ross Jeffery,et al.  Comparing inspection strategies for software requirement specifications , 1996, Proceedings of 1996 Australian Software Engineering Conference.