Use and abuse cases

Use Case Modeling (UCM) has become an essential ingredient of computing courses, as it is widely used in object-oriented analysis and design. Although a simple concept, UCM is not straightforward to teach. We report on our experience gained in teaching students as a part of requirements engineering education at both undergraduate and postgraduate level. Two case studies reveal a number of problems students have, and we suggest consequent improvements to make in the teaching and assessing our students. We believe these tactics can be equally beneficial to the wider community.

[1]  Robert M. Hayes,et al.  Systems analysis and design , 1970, ACM '70.

[2]  Leszek A. Maciaszek.  Requirements analysis and system design: developing information systems with UML , 2001 .

[3]  Ian K. Bray,et al.  An Introduction to Requirements Engineering , 2002 .

[4]  Julie E. Kendall,et al.  Systems analysis and design , 1981 .

[5]  Neil A. M. Maiden,et al.  CREWS-SAVRE: Scenarios for Acquiring and Validating Requirements , 1998, Automated Software Engineering.

[6]  Didar Zowghi,et al.  Teaching requirements engineering through role playing: lessons learnt , 2003, Proceedings. 11th IEEE International Requirements Engineering Conference, 2003..

[7]  Keith Phalp,et al.  Comparing Use Case Writing Guidelines , 2001 .

[8]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

[9]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[10]  Ivar Jacobson,et al.  The Unified Modeling Language User Guide , 1998, J. Database Manag..

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

[12]  Sooyong Park,et al.  Scenario-based Goal-oriented Approach for Use Case Modeling , 2002 .

[13]  I. Alexander.  Stakeholders: who is your system for? , 2003 .

[14]  Andreas L. Opdahl,et al.  Templates for Misuse Case Description , 2001 .

[15]  William Mackaness,et al.  The Devil is in the Detail: Visualising Analogical Thought in Retail Location Decisionmaking , 2003, Intensive & critical care nursing.

[16]  Leszek A. Maciaszek,et al.  Requirements analysis and system design: developing information systems with UML , 2001 .

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

[18]  Ivar Jacobson,et al.  Object-oriented development in an industrial environment , 1987, OOPSLA '87.

[19]  Alistair Cockburn,et al.  Question time! about use cases , 1998, OOPSLA '98.

[20]  Abstraction - is it teachable? 'the devil is in the detail' , 2003, CSEE&T.

[21]  Ivar Jacobson,et al.  Use cases – Yesterday, today, and tomorrow , 2004, Software & Systems Modeling.

[22]  Alain Abran,et al.  The Guide to the Software Engineering Body of Knowledge , 1999, IEEE Softw..

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

[24]  Richard Stevens,et al.  Writing Better Requirements , 2002 .

[25]  Richard Vidgen.  Requirements analysis and UML use cases and class diagrams , 2003 .

[26]  Ian Sommerville,et al.  Requirements Engineering: Processes and Techniques , 1998 .