Abstract

The paper provides a concise discussion of the most important theoretical aspects of the Association-Oriented Database (AODB) Metamodel. Even though the model has been practically verified, the author has focused on its formal aspects and modeling language. The AODB Metamodel has been developed for the purposes of building the knowledge representation systems. Basically, such systems are structurally and functionally complex, hence they require advanced solutions to be applied for the purpose of data modeling. The modeling language enables designing database structures in the AODB Metamodel, taking into account various features of this database metamodel. The language in question is fully integrated and compatible with AODB Metamodel. It has been developed for the purposes of this metamodel, it operates with categories specific to it and, as such, it constitutes neither a version nor an extension of any of the existing languages. The second part of the paper provides the definition and discussion concerning the graphical modeling language — Association-Oriented Modeling Language (AML). The last section of the paper introduces the case-study that presents the key features of the metamodel, as well as the use of modeling language. The topics of presented examples comprise a simplified model of degree programs for universities and the model of Ontological Core, the main module of Semantic Knowledge Base (SKB).

Highlights

  • Nowadays, database engineering focuses on excelling the use of relational database model.[1,2] There have been attempts towards the object-oriented databases implementation, so far they have been futile

  • Its characteristic di®ers from the one known in other metamodels, where visibility scopes are bound with the inheritance properties as well as inheritance modes

  • The foregoing means that many aspects which frequently is used to be established by means of the system logic layer are supported directly from the database level

Read more

Summary

Introduction

Database engineering focuses on excelling the use of relational database model.[1,2] There have been attempts towards the object-oriented databases implementation, so far they have been futile. The assumptions and properties of the database model developed, being a direct response to the research problems indicated in this scope, have been presented along with a formal denition of the proposed AODB. The paper is completed with the denition and discussion concerning the graphical modeling language It enables designing database structures in the AODB, taking into account various features. Reasons to Undertake the Research Problem This section addresses the most important problems recognized in the sphere of database models from the perspective of model denitions and their consequences It provides substantiation for the main subject elaborated upon and introduces the problems discussed in detail in subsequent sections. Modeling naturalness (intuitiveness), . model's power of expression, . semantic unambiguity of schemata

Primary needs
Semantic unambiguity of database schemata
Many-to-many relationships
Category-specic separability of data and relationships between them
N-arity of relationships
Possibility to apply dependencies to the lifetime of associated objects
Single metamodel in all layers
Association as an individual model category
Mechanism for establishing relationships of composition
Role as an individual model category
Possibility of inheriting relationships
Independence in role and attribute inheritance
Inheritance with real mode
Mechanism for ensuring intrinsic coherence of relationships
Database Terms and Concepts Denition
Metamodel primitive
Domain
Database metamodel
Database
Database management system
Intensional database part
Direction
Composition
Inheritability
Virtuality
Data type int8 j int16 j int32 j int64 j float j double j
Intentional types
Collection attrs
Inheritance
Extensional types
Metastructure of the association-oriented metamodel
Descriptions
Inherited relationships
Case Studies
Simplied studies denition system
Reference to type issue
The issue of joining the storage function and data binding in one concept
Uninavigability associations
Association generalization
Modeling of dependency graph
Uniqueness
Ontological core module model
Abstract data containers
Roles multiplicity
Lifetime dependency
The constrains on inheritance of elements
Description of association
Attribute types
Discussion
Summary
Full Text
Published version (Free)

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call