RELATIONAL DEDUCTIVE OBJECT-ORIENTED MODELING (RDOOM) APPROACH FOR FINDING,  REPRESENTING AND INTEGRATING APPLICATION-SPECIFIC CONCEPTS

Next generation information systems (NGISs) have to support the manipulation of data-oriented, behavioral and deductive aspects of application domains. Many modeling methods, e.g. UML and other object-oriented modeling methods offer primitives for modeling data-oriented and behavioral aspects but they do not support the modeling of deductive aspects. In addition, NGISs may be implemented by several separate software/database systems that are based on different paradigms. Therefore it is not appropriate to use such a modeling method which is based on one paradigm. In NGISs it is essential to integrate the value-oriented approach with the object-oriented approach. We develop a relational deductive object-oriented modeling (RDOOM) approach for NGISs. Our goal is to combine into one modeling method, the navigation power of the relational model, the modeling power of the object-orientation and the inference power of the deductive (logical) framework. It is obvious that in NGISs complex and large specifications have to be embedded in application-specific concepts and structures that are defined beforehand for users to facilitate their query formulation. The detection and specification of application-specific concepts and structures means a new challenge for analysis methods. We show that on the basis of the primitives of RDOOM it is possible to represent this kind of application-specific information in a natural way. It is also necessary that the appropriateness and adequacy of application-specific concepts and structures can be tested before their expensive design and implementation phases. For the definition of these concepts and structures a diagrammatic representation typical of many modeling methods is not sufficient. Rather, a precise and executable representation is needed. Especially the complex and large derivation rules behind deductive concepts cannot be expressed precisely with diagrammatic representations. We develop set-theoretical representations for our primitives. The precise representation of the result of systems analysis also gives a more substantial starting point for the design and implementation of NGISs.

Download Full-text

Implementation Techniques for Extensible Object Storage Systems

Advances in Database Research - Advanced Topics in Database Research, Volume 2 ◽

10.4018/978-1-59140-063-9.ch006 ◽

2011 ◽

pp. 104-127

Author(s):

Jung-Ho Ahn ◽

Ha-Joo Song ◽

Hyoung-Joo Kim

Keyword(s):

High Performance ◽

Storage System ◽

Object Oriented ◽

Middle Layer ◽

Database Systems ◽

Object Oriented Design ◽

Design And Implementation ◽

Pointer Swizzling ◽

Implementation Techniques ◽

Object Storage

An efficient object manager, a middle layer on top of a storage system, is essential to ensure acceptable performance of object-oriented database systems, since a traditional record-based storage system is too simple to provide object abstraction. In this chapter, we design and implement an extensible object storage system, called Soprano, in an object-oriented fashion which has shown great potential in extensibility and code reusability. Soprano provides a uniform object abstraction and gives us the convenience of persistent programming through many useful persistent classes. Also, Soprano supports efficient object management and pointer swizzling for fast object access. This chapter investigates several aspects of the design and implementation of the extensible object storage system. Our experience shows the feasibility of using an object-oriented design and implementation in building an object storage system that should have both extensibility and high performance.

Download Full-text

Object-Relational Modeling

Handbook of Research on Innovations in Database Technologies and Applications ◽

10.4018/978-1-60566-242-8.ch019 ◽

2009 ◽

pp. 162-170

Author(s):

Jaroslav Zendulka

Keyword(s):

Relational Database ◽

Relational Databases ◽

Conceptual Modeling ◽

Object Oriented ◽

Database Systems ◽

Object Relational ◽

The Difference ◽

Object Oriented Approach ◽

Entity Relationship ◽

Oriented Approach

Modeling techniques play an important role in the development of database applications. Well-known entity-relationship modeling and its extensions have become a widely-accepted approach for relational database conceptual design. An object-oriented approach has brought a new view of conceptual modeling. A class as a fundamental concept of the object-oriented approach encapsulates both data and behavior, whereas traditional relational databases are able to store only data. In the early 1990s, the difference between the relational and object-oriented (OO) technologies, which were, and are still used together to build complex software systems, was labeled the object-relational impedance mismatch (Ambler, 2003). The object-oriented approach and the need of new application areas to store complex data have greatly influenced database technology since that time. Besides appearance of object-oriented database systems, which fully implement objectoriented paradigm in a database environment (Catell et al., 2003), traditional relational database management systems become object-relational (Stonebraker & Brown, 1999). The most recent versions of the SQL standard, SQL: 1999 (Melton & Simon (2001) and SQL: 2003 (Eisenberg et al., 2004), introduced object-relational features to the standard and leading database producers have already released packages which incorporate them.

Download Full-text

Formal specification, object oriented design, and implementation of an ephemeral logger for database systems

Lecture Notes in Computer Science - Database and Expert Systems Applications ◽

10.1007/bfb0034693 ◽

1996 ◽

pp. 333-355 ◽

Cited By ~ 4

Author(s):

Paul Hennessey ◽

Mohamed T. Ibrahim ◽

Alexander M. Fedorec

Keyword(s):

Formal Specification ◽

Object Oriented ◽

Database Systems ◽

Object Oriented Design ◽

Design And Implementation

Download Full-text

Integration of database systems using an object-oriented approach

[1991] Proceedings. First International Workshop on Interoperability in Multidatabase Systems ◽

10.1109/ims.1991.153682 ◽

2002 ◽

Cited By ~ 11

Author(s):

B. Czejdo ◽

M. Taylor

Keyword(s):

Object Oriented ◽

Database Systems ◽

Object Oriented Approach ◽

Oriented Approach

Download Full-text

A FRAMEWORK FOR SUPPORTING TRIGGERS IN OBJECT-ORIENTED DATABASE SYSTEMS

International Journal of Cooperative Information Systems ◽

10.1142/s0218215792000064 ◽

1992 ◽

Vol 01 (01) ◽

pp. 127-143 ◽

Cited By ~ 9

Author(s):

WON KIM ◽

YOON-JOON LEE ◽

JUNGYUN SEO

Keyword(s):

Object Oriented ◽

Database Systems ◽

Relational Model ◽

General Mechanism ◽

Constraint Specification ◽

Active Data ◽

Inheritance Hierarchy ◽

Cooperating Agents ◽

Object Oriented Database ◽

Centralized System

An active database system reacts to a set of external events such as a timer interrupt or access to a particular object in the database. A trigger is a general mechanism for active data management, both in the context of a centralized system or a distributed system (including that of autonomous and cooperating agents). It consists of three parts; event specification, integrity constraint specification, and action specification. The event specification in a trigger is a set of events which will cause the condition in the constraint specification to be checked. If the condition is true, the actions in the action specification will be initiated. In this paper, we develop a framework for supporting triggers in object-oriented database systems. The framework consists of a categorization for each of the three components of a trigger. The framework is first cast in the context of the relational model of data, and is then extended to account for object-oriented concepts that constitute an object-oriented data model, including nested objects, methods, and inheritance hierarchy.

Download Full-text