Ontology Based Object-Oriented Domain Modeling

2011 ◽  
pp. 37-60
Author(s):  
Joerg Evermann ◽  
Yair Wand
Keyword(s):  
Information System ◽  
Conceptual Modeling ◽  
Object Oriented ◽  
Modeling Languages ◽  
Domain Modeling ◽  
Application Domain ◽  
Structural Elements ◽  
Software Modeling ◽  
Software Models

An important step in developing the requirements for an information system is analyzing the application domain. In this step, conceptual models are used for representing an application domain. However, while languages for software design are available and widely used, no generally accepted language exists for conceptual modeling. This work suggests the use of object-oriented software modeling languages also for conceptual modeling. Such use can support a more accurate transition from domain modes to software models. As software-modeling languages were not intended for modeling application domains, their constructs lack the required semantics. While previous papers addressed the representation of structural elements of domains using object concepts, this paper addresses behavioral aspects, related to change and interaction. The proposed semantics are based on a mapping between ontological concepts that describe behavior and object-oriented constructs related to dynamics. Based on these mappings, modeling rules are proposed to guide the modeler in creating ontologically well-formed models. The mappings and rules are exemplified using UML and are demonstrated using a case study.

Ontology Based Object-Oriented Domain Modeling

2009 ◽  
pp. 505-527
Author(s):  
Joerg Evermann ◽  
Yair Wand
Keyword(s):  
Conceptual Modeling ◽  
Object Oriented ◽  
Modeling Languages ◽  
Domain Modeling ◽  
Application Domain ◽  
Structural Elements ◽  
Software Modeling ◽  
Software Models ◽  
Domain Models

An important step in developing the requirements for an information system is analyzing the application domain. In this step, conceptual models are used for representing an application domain. However, while languages for software design are available and widely used, no generally accepted language exists for conceptual modeling. This work suggests the use of object-oriented software modeling languages also for conceptual modeling. Such use can support a more accurate transition from domain models to software models. As software-modeling languages were not intended for modeling application domains, their constructs lack the required semantics. While previous papers addressed the representation of structural elements of domains using object concepts, this paper addresses behavioral aspects, related to change and interaction. The proposed semantics are based on a mapping between ontological concepts that describe behavior and object-oriented constructs related to dynamics. Based on these mappings, modeling rules are proposed to guide the modeler in creating ontologically well-formed models. The mappings and rules are exemplified using UML and are demonstrated using a case study.

scholarly journals From conceptual modeling to a map

2018 ◽  
Vol 1 ◽  
pp. 1-5
Author(s):  
Dariusz Gotlib ◽  
Robert Olszewski
Keyword(s):  
Information System ◽  
Information Systems ◽  
System Design ◽  
Spatial Modeling ◽  
Conceptual Modeling ◽  
Domain Modeling ◽  
Data Modelling ◽  
Information System Design ◽  
Cartographic Modeling ◽  
Design And Production

Nowadays almost every map is a component of the information system. Design and production of maps requires the use of specific rules for modeling information systems: conceptual, application and data modelling. While analyzing various stages of cartographic modeling the authors ask the question: at what stage of this process a map occurs. Can we say that the “life of the map” begins even before someone define its form of presentation? This question is particularly important at the time of exponentially increasing number of new geoinformation products. During the analysis of the theory of cartography and relations of the discipline to other fields of knowledge it has been attempted to define a few properties of cartographic modeling which distinguish the process from other methods of spatial modeling. Assuming that the map is a model of reality (created in the process of cartographic modeling supported by domain-modeling) the article proposes an analogy of the process of cartographic modeling to the scheme of conceptual modeling presented in ISO 19101 standard.

Forward Engineering of UML Static Models

2005 ◽  
pp. 1212-1217 ◽  
Author(s):  
Liliana Favre ◽  
Liliana Martinez ◽  
Claudia Pereira
Keyword(s):  
Unified Modeling Language ◽  
Object Oriented ◽  
Modeling Language ◽  
Modeling Languages ◽  
Software Modeling ◽  
Visual Languages ◽  
Unified Modeling ◽  
Static Models ◽  
Forward Engineering ◽  
Software Intensive

The Unified Modeling Language (UML) has emerged as a modeling language for specifying, visualizing, constructing, and documenting software-intensive systems. It unifies proven software modeling languages that incorporate the object-oriented community’s consensus on core modeling concepts. It also includes additional expressiveness to handle problems that previous visual languages did not fully address (Rumbaugh, Jacobson & Booch, 1999).

scholarly journals BORM – overview of the methodology and case study of the agrarian information system

2012 ◽  
Vol 49 (No. 9) ◽  
pp. 397-406
Author(s):  
V. Merunka
Keyword(s):  
Information System ◽  
Object Oriented ◽  
Business Systems ◽  
The Past ◽  
Business Object ◽  
Modeling Techniques ◽  
Object Oriented Approach ◽  
Object Relationship ◽  
Tools And Methods

BORM (Business Object Relationship Modelling) is a methodology developed to capture the knowledge of process-based business systems. It has been in development since 1993 and has proved an effective method, which is popular with both users and analysts. This paper presents BORM, its tools, and methods via a case study of the agrarian information system. BORM is based on the combination of object-oriented approach and process-based modelling. Also, an advantage of BORM is the small number of concepts required combined with a considerable expressiveness. In this way, BORM is in the tradition of pure approach established over the past years by structured modeling techniques.

scholarly journals Domain Modeling in the Context of Ontology

2015 ◽  
Vol 40 (1) ◽  
pp. 3-15 ◽  
Author(s):  
Iwona Dubielewicz ◽  
Bogumiła Hnatkowska ◽  
Zbigniew Huzar ◽  
Lech Tuzinkiewicz
Keyword(s):  
Information System ◽  
Design Process ◽  
Domain Knowledge ◽  
Systematic Approach ◽  
Domain Ontology ◽  
Domain Model ◽  
General Level ◽  
Domain Modeling ◽  
Application Domain ◽  
Model Domain

Abstract The domain knowledge represented by ontology should be widely used in the design process of information system. The aim of the paper is to outline a systematic approach of developing a CIM model (domain model, precisely) on the basis of a selected domain ontology. There are presented some hints how ontology concepts can be expressed in domain model. Elaborated example realizes some difficulties in proposed approach, e.g. the domain knowledge is spread over many ontologies, some facts are defined at very general level (their interpretation is more difficult), ontology may contain many irrelevant elements. Nevertheless, we are believed that applying ontology in conscious way can help to achieve higher compliance of the domain model with the application domain.

Cross-disciplinary engineering with AutomationML and SysML

2016 ◽  
Vol 64 (4) ◽  
Author(s):  
Luca Berardinelli ◽  
Stefan Biffl ◽  
Arndt Lüder ◽  
Emanuel Mätzler ◽  
Tanja Mayerhofer ◽  
...  
Keyword(s):  
Production System ◽  
Electrical Engineering ◽  
Structural Modeling ◽  
Modeling Language ◽  
Modeling Languages ◽  
Systems Modeling ◽  
Software Modeling ◽  
Model Driven ◽  
Early Phases

AbstractAutomationML (AML) is an emerging standard in the automation domain to represent and exchange artifacts between heterogeneous engineering tools used in different disciplines, such as mechanical and electrical engineering. The Systems Modeling Language (SysML) is a modeling standard influenced by software modeling languages, such as UML, typically adopted in the early phases of engineering processes. This paper investigates commonalities and differences of the structural modeling parts of AML (CAEX) and SysML (block diagrams) in support of establishing tool-independent interoperability. This support for cross-disciplinary modeling is facilitated by a bridge between AML and SysML built on model-driven interoperability techniques. We demonstrate the interoperability between AML and SysML with a case study concerning a lab-sized production system.

Sign in / Sign up

Export Citation Format

Share Document