Data model issues for object-oriented applications

  • Authors:

  • Jay Banerjee;Hong-Tai Chou;Jorge F. Garza;Won Kim;Darrell Woelk;Nat Ballou;Hyoung-Joo Kim

  • Affiliations:

  • MCC, Austin, TX;MCC, Austin, TX;MCC, Austin, TX;MCC, Austin, TX;MCC, Austin, TX;MCC, Austin, TX;Univ. of Texas, Austin, TX

  • Venue:
  • ACM Transactions on Information Systems (TOIS)
  • Year:
  • 1987

Quantified Score

Hi-index 0.05

Visualization

Abstract

Presented in this paper is the data model for ORION, a prototype database system that adds persistence and sharability to objects created and manipulated in object-oriented applications. The ORION data model consolidates and modifies a number of major concepts found in many object-oriented systems, such as objects, classes, class lattice, methods, and inheritance. These concepts are reviewed and three major enhancements to the conventional object-oriented data model, namely, schema evolution, composite objects, and versions, are elaborated upon. Schema evolution is the ability to dynamically make changes to the class definitions and the structure of the class lattice. Composite objects are recursive collections of exclusive components that are treated as units of storage, retrieval, and integrity enforcement. Versions are variations of the same object that are related by the history of their derivation. These enhancements are strongly motivated by the data management requirements of the ORION applications from the domains of artificial intelligence, computer-aided design and manufacturing, and office information systems with multimedia documents.