Ontology based object-oriented domain modelling: fundamental concepts

Understanding the business is an important step in information system (IS) development. Conceptual models are descriptions of the organizational context for which a system is developed, and are used to help understanding this context. However, conceptual modelling methods do not provide well-formalized ways to create domain descriptions. On the other hand, in the area of IS design and software modelling, languages exist (such as UML) that possess a high level of formality. Extending the use of these IS design languages to conceptual modelling, even though they have not been specifically intended for this, can lead to several advantages. In particular, it can enable the use of similar notation in several stages of system development. However, while object-oriented constructs such as “object” and “operation” have clear meaning in the context of software design, it is not clear what they might mean in terms of the application domain, and no rules or guidelines exist for using them to create useful descriptions of such domains. This paper suggests specific semantics for object-oriented constructs based on a mapping between ontologically derived concepts and object-oriented language constructs. The paper also proposes modelling rules to guide the construction of object-oriented conceptual models and to assure that such models describe only ontologically feasible application domain situations. While the results are applicable to object-oriented constructs in general, UML is used as an example. A case study to test the use of the proposed semantics and modelling rules is described.

[1]  Nicola Guarino,et al.  Evaluating ontological decisions with OntoClean , 2002, CACM.

[2]  Chris Dollin,et al.  Object-oriented development: the fusion method , 1994 .

[3]  J. Weitzman,et al.  Two for the price of one , 2000, Genome Biology.

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

[5]  Michael Rosemann,et al.  Ontological analysis of integrated process modeling: Some initial insights , 2000 .

[6]  Michael Uschold,et al.  Ontologies: principles, methods and applications , 1996, The Knowledge Engineering Review.

[7]  Peter Loos,et al.  Ontological Evaluation of Reference Models Using the Bunge-Wand-Weber Model , 2003, AMCIS.

[8]  Michael Rosemann,et al.  Integrated Process Modeling: An Ontological Evaluation , 2000, Inf. Syst..

[9]  Paul Roe.  Distributed XML Objects , 2003, JMLC.

[10]  Andreas L. Opdahl,et al.  Concepts for Real-World Modelling , 1993, CAiSE.

[11]  Brian Henderson-Sellers,et al.  An Ontological Evaluation of the OML Metamodel , 2000, ISCO.

[12]  Michael Rosemann,et al.  An Ontological Analysis of Integrated Process Modelling , 1999, CAiSE.

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

[14]  Ron Weber,et al.  On the ontological expressiveness of information systems analysis and design grammars , 1993, Inf. Syst. J..

[15]  Carole D. Hafner,et al.  The State of the Art in Ontology Design: A Survey and Comparative Review , 1997, AI Mag..

[16]  Michael Haupt,et al.  The Convergence of AOP and Active Databases: Towards Reactive Middleware , 2003, GPCE.

[17]  Yanchun Zhang,et al.  An analytical evaluation of NIAM'S grammar for conceptual schema diagrams , 1996, Inf. Syst. J..

[18]  Gerald W. Both,et al.  Object-oriented analysis and design with applications , 1994 .

[19]  Eckhard D. Falkenberg,et al.  Information System Concepts: An Integrated Discipline Emerging , 2000, IFIP — The International Federation for Information Processing.

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

[21]  Sophie Cockcroft,et al.  Ontological Evaluation of Health Models: Some Early Findings , 2003, PACIS.

[22]  Yair Wand,et al.  A Proposal for a Formal Model of Objects , 1989, Object-Oriented Concepts, Databases, and Applications.

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

[24]  Ron Weber,et al.  An Ontological Evaluation of Systems Analysis and Design Methods , 1989, ISCO.

[25]  Yair Wand,et al.  Using objects for systems analysis , 1997, CACM.

[26]  Dennis Shasha,et al.  Using a relational system on Wall Street: the good, the bad, the ugly, and the ideal , 1989, CACM.

[27]  Dov Dori,et al.  Modelling Off-the-Shelf Information Systems Requirements: An Ontological Approach , 2001, Requirements Engineering.

[28]  Andrew C. Gemino.  Empirical comparisons of system analysis modeling techniques , 1999 .

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

[30]  Ron Weber,et al.  Optional Properties Versus Subtyping in Conceptual Modeling: A Theory and Empirical Test , 1996, ICIS.

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

[32]  Michel Patry,et al.  An Evaluation of Inter-Organizational Workflow Modeling Formalisms , 2002 .

[33]  A. D. Ritchie.  The Dictionary of Philosophy , 1945, Nature.