An Ontological Analysis of Use Case Modeling Grammar

Use case modeling is a popular technique for representing the functional requirements of an information system. The simple graphical notation of use case diagrams, accompanied by well-structured narrative descriptions, makes use case models fairly easy to read and understand. This simplicity, however, belies the challenges associated with creating use case models. There is little, if any, theory underlying use cases, and little more than loose guidelines for creating a complete, consistent, and integrated set of use cases. We argue that there is a need for more rigor and consistency in the grammatical constructs used in use case modeling. Toward this end, we present a theoretically- and practice-based assessment of use case modeling constructs, and make recommendations for future research to improve and strengthen this technique.

[1]  Veda C. Storey,et al.  An ontological analysis of the relationship construct in conceptual modeling , 1999, TODS.

[2]  Alistair Cockburn,et al.  Goals and Use Cases , 1997, J. Object Oriented Program..

[3]  Yair Wand,et al.  Ontology as a foundation for meta-modelling and method engineering , 1996, Inf. Softw. Technol..

[4]  How to Avoid Use-Case Pitfalls , 2000 .

[5]  Brian Henderson-Sellers,et al.  Ontological Evaluation of the UML Using the Bunge–Wand–Weber Model , 2002, Software and Systems Modeling.

[6]  Jeffrey Parsons,et al.  An Information Model Based on Classification Theory , 1996 .

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

[8]  Steven L. Alter,et al.  Information Systems: Foundation of E-Business , 2002 .

[9]  Ramez Elmasri,et al.  Fundamentals of database systems (2nd ed.) , 1994 .

[10]  Yair Wand,et al.  Emancipating instances from the tyranny of classes in information modeling , 2000, TODS.

[11]  Kendall Scott,et al.  Applying Use Case Driven Object Modeling with UML: An Annotated e-Commerce Example , 2001 .

[12]  Jeffrey Parsons,et al.  Understanding the Role of Use Cases in UML: A Review and Research Agenda , 2000, J. Database Manag..

[13]  Larry Constantine,et al.  Structure and style in use cases for user interface design , 2001 .

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

[15]  Brian Henderson-Sellers,et al.  Grounding the OML metamodel in ontology , 2001, J. Syst. Softw..

[16]  Daniel L. Sherrell,et al.  Communications of the Association for Information Systems , 1999 .

[17]  Omar El Sawy,et al.  Building an Information System Design Theory for Vigilant EIS , 1992, Inf. Syst. Res..

[18]  Ron Weber,et al.  An Ontological Model of an Information System , 1990, IEEE Trans. Software Eng..

[19]  Ivar Jacobson,et al.  The Unified Software Development Process , 1999 .

[20]  Per Capita,et al.  About the authors , 1995, Machine Vision and Applications.

[21]  M. Bunge Treatise on basic philosophy , 1974 .

[22]  Scott W. Ambler,et al.  The Object Primer: Introduction to Techniques for Agile Modeling , 2001 .

[23]  Hee Beng Kuan Tan,et al.  On Formalization of the Whole-Part Relationship in the Unified Modeling Language , 2003, IEEE Trans. Software Eng..

[24]  E. F. Codd,et al.  A relational model of data for large shared data banks , 1970, CACM.

[25]  Ivar Jacobson,et al.  Unified Modeling Language , 2020, Definitions.

[26]  E. F. Codd,et al.  A Relational Model for Large Shared Data Banks , 1970 .

[27]  Michael Rosemann,et al.  Developing a meta model for the Bunge-Wand-Weber ontological constructs , 2002, Inf. Syst..

[28]  Yanchun Zhang,et al.  An Ontological Evaluation Of Niam's Grammar For Conceptual Schema Diagrams , 1991, ICIS.

[29]  Mark Lycett,et al.  Actor Perception in Business Use Case Modeling , 2003, Commun. Assoc. Inf. Syst..

[30]  Yair Wand,et al.  Theoretical foundations for conceptual modelling in information systems development , 1995, Decis. Support Syst..

[31]  Björn Regnell,et al.  From Requirements to Design with Use Cases - Experiences from Industrial Pilot Projects , 1997 .

[32]  Ramez Elmasri,et al.  Fundamentals of Database Systems , 1989 .

[33]  Ron Weber,et al.  On the deep structure of information systems , 1995, Inf. Syst. J..

[34]  Morten Hertzum,et al.  Making use of scenarios: a field study of conceptual design , 2003, Int. J. Hum. Comput. Stud..

[35]  Annie I. Antón,et al.  A Representational Framework for Scenarios of System Use , 1998, Requirements Engineering.

[36]  Matthias Jarke,et al.  Scenario Management: An Interdisciplinary Approach , 1998, Requirements Engineering.

[37]  Ron Weber,et al.  Should Optional Properties Be Used in Conceptual Modelling? A Theory and Three Empirical Tests , 2001, Inf. Syst. Res..

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

[39]  Ron Weber,et al.  Research Commentary: Information Systems and Conceptual Modeling - A Research Agenda , 2002, Inf. Syst. Res..

[40]  Jonathan Lee,et al.  Analyzing User Requirements by Use Cases: A Goal-Driven Approach , 1999, IEEE Softw..

[41]  Les Gasser,et al.  A Design Theory for Systems That Support Emergent Knowledge Processes , 2002, MIS Q..

[42]  Edward V. Berard,et al.  Be Careful With “Use Cases” , 1995 .