Introducing Object-Oriented Data Modeling

2006 ◽  
pp. 107-129
Keyword(s):  
Data Modeling ◽  
Object Oriented

Integrated 3D Spatial Data Model of Object-Oriented Digital Landslide

2012 ◽  
Vol 204-208 ◽  
pp. 4872-4877
Author(s):  
Da Xi Ma ◽  
Xiao Hong Liu ◽  
Li Wei Ma
Keyword(s):  
Spatial Data ◽  
Data Model ◽  
Dimensional Space ◽  
Three Dimensional ◽  
Data Modeling ◽  
Object Oriented ◽  
Landslide Modeling ◽  
Space Data ◽  
Spatial Data Model ◽  
Three Dimensional Space

By analyzing the attributes of three-dimensional space data model, the integrated 3D spatial data adopts object-oriented method for digital landslide modeling. It achieves spatial data modeling for landslide geological entity. An experimental case is given to indicate the feasibility of this approach for spatial data modeling.

Integration and specialization

1994 ◽  
Author(s):  
Douglas Schenck ◽  
Peter Wilson
Keyword(s):  
Inverse Problem ◽  
Data Modeling ◽  
Object Oriented ◽  
Major Topic ◽  
Type Lattice ◽  
The Relationship ◽  
Object Oriented Languages

The major topic of this Chapter is modeling in the large. By this we mean looking at methods to integrate several different models into a single cohesive whole, and also examining the inverse problem of extracting a small specialized model from a larger one. Before we can sensibly discuss these, though, we need to look more closely at two aspects of EXPRESS, namely subtyping and schema interfacing. EXPRESS has a concept of Supertype and Subtype which taken together enable a type lattice to be constructed. A Subtype-Supertype relationship is typically called an ‘Isa’ relationship in data modeling terms. That is, a Subtype is a kind of its Supertype(s). For example, if we define an entity pet and also define two subtypes of this called cat and goldfish then an instance of cat is also an instance of pet, and similarly for a goldfish. The relationship, though, is asymmetrical, as a pet may be something other than a cat or goldfish; for instance a pet may also be a dog. A Subtype is a more specialized kind of thing than its Supertype and, conversely, a Supertype is a generalization of its Subtypes. A Subtype inherits all the attributes and constraints of its Supertype(s). In EXPRESS an entity is a Subtype of another entity if it declares its Supertype entity within its Subtype declaration. A Supertype does not declare its Subtypes. In general, an instance of a Subtype requires an instantiation of each of its Supertypes, while an instance of a Supertype does not require instantiation of its Subtypes. This later behavior may be modified by declaring the Supertype to be an Abstract Supertype, in which case an instance of the Supertype does require instantiation of at least one of its Subtypes. In most data modeling and Object Oriented languages that support similar notions to Subtyping, if an instance of a Supertype requires instantiation of a Subtype, then one and only one Subtype can be instantiated. EXPRESS does not have this restriction. Unless otherwise constrained, an instance of a Supertype may be accompanied by one instance of each of its Subtypes.

Combining 3D Simulation Technology With Object-Oriented Databases: A Database Oriented Approach to Virtual Reality Systems

2011 ◽  
Author(s):  
Martin Hoppen ◽  
Juergen Rossmann ◽  
Michael Schluse ◽  
Ralf Waspe ◽  
Malte Rast
Keyword(s):  
Virtual Reality ◽  
Data Modeling ◽  
Object Oriented ◽  
Simulation System ◽  
Primary Data ◽  
Graph Database ◽  
Modeling Tools ◽  
External Database ◽  
Object Oriented Databases ◽  
Oriented Approach

Using object-oriented databases as the primary data source in VR applications has a variety of advantages, but requires the development of new techniques concerning data modeling, data handling and data transfer from a Virtual Reality system’s point of view. The many advantages are outlined in the first part of this paper. We first introduce versioning and collaboration techniques as our main motivation. These can also be used in the traditional file based approach, but are much more powerful when realized with a database on an object and attribute level. Using an object-oriented approach to data modeling, objects of the real world can be modeled more intuitively by defining appropriate classes with their relevant attributes. Furthermore, databases can function as central communication hubs for consistent multi user interaction. Besides, the use of databases with open interface standards allows to easily cooperate with other applications such as modeling tools and other data generators. The second part of this paper focuses on our approach to seamlessly integrate such databases in Virtual Reality systems. For this we developed an object-oriented internal graph database and linked it to object-oriented external databases for central storage and collaboration. Object classes defined by XML data schemata allow to easily integrate new data models in VR applications at run-time. A fully transparent database layer in the simulation system makes it easy to interchange the external database. We present the basic structure of our simulation graph database, as well as the mechanisms which are used to transparently map data and meta-data from the external database to the simulation database. To show the validity and flexibility of our approach selected applications realized with our simulation system so far e. g. applications based on geoinformation databases such as forest inventory systems and city models, applications in the field of distributed control and simulation of assembly lines or database-driven virtual testbeds applications for automatic map generation in planetary landing missions are introduced.

scholarly journals RANCANG BANGUN SISTEM INFORMASI BERBASIS DEKSTOP PADA KOPERASI MELATI

2018 ◽  
Vol 10 (2) ◽  
pp. 1031
Author(s):  
Kemal Farouq Mauladi
Keyword(s):  
Information Systems ◽  
System Design ◽  
Data Modeling ◽  
Object Oriented ◽  
Object Oriented Design ◽  
Functional Models

Applications,  Plans  to  Build  Desktop-Based  Information  Systems  on  Melati  Cooperatives,  as  one  form  of organization  are  the  implementing  units  of  members  of  the  welfare  sector  in  this  case  especially  small  and medium entrepreneurs. In making the system, it is necessary to have a system design, the system design used is object-oriented design by making object diagrams, functional models, and ERDs and normalization techniques for data modeling

Information Analysis in UML and ORM

2002 ◽  
pp. 307-323 ◽  
Author(s):  
Terry Halpin
Keyword(s):  
Unified Modeling Language ◽  
Data Modeling ◽  
Object Oriented ◽  
Information Analysis ◽  
Domain Experts ◽  
Unified Modeling ◽  
Data Intensive ◽  
Class Diagrams ◽  
Conceptual Data ◽  
Data Intensive Applications

Since its adoption by the Object Management Group as a language for object-oriented analysis and design, the Unified Modeling Language (UML) has become widely used for designing object-oriented code. However, UML has had only minimal adoption among practitioners for the purposes of information analysis and database design. One main reason for this is that the class diagrams used in UML for data modeling provide only weak, and awkward, support for the kinds of business rules found in data-intensive applications. Moreover, UML’s graphical language does not lend itself readily to verbalization and multiple instantiation for validating data models with domain experts. These defects can be remedied by using a fact-oriented approach for information analysis, from which UML class diagrams may be derived. Object-Role Modeling (ORM) is currently the most popular fact-oriented modeling approach. This chapter examines the relative strengths and weaknesses of UML and ORM for conceptual data modeling, and indicates how models in one notation can be translated into the other.

Sign in / Sign up

Export Citation Format

Share Document