ACM Home Page
Please provide us with feedback. Feedback
Data model issues for object-oriented applications
Full text PdfPdf (1.99 MB)
Source ACM Transactions on Information Systems (TOIS) archive
Volume 5 ,  Issue 1  (January 1987) table of contents
Pages: 3 - 26  
Year of Publication: 1987
ISSN:1046-8188
Authors
Jay Banerjee  MCC, Austin, TX
Hong-Tai Chou  MCC, Austin, TX
Jorge F. Garza  MCC, Austin, TX
Won Kim  MCC, Austin, TX
Darrell Woelk  MCC, Austin, TX
Nat Ballou  MCC, Austin, TX
Hyoung-Joo Kim  Univ. of Texas, Austin, TX
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 26,   Downloads (12 Months): 142,   Citation Count: 107
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/22890.22945
What is a DOI?

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.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
AFSARMANESH, H., KNAPP, D., MCLEOD, D., AND PARKER, A. An object-oriented approach to VLSI/CAD. In Proceedings of the 11th International Conference on Very Large Data Bases (Stockholm, Sweden, Aug.). VLDB Endowment, Saratoga, Calif., 1985.
2
 
3
ATWOOD, T.M. An object-oriented DBMS for design support applications. In Proceedings of IEEE First International Conference on Computer-Aided Technologies 85 (Montreal, Canada, Sept.). IEEE, New York, 1985, pp. 299-307.
 
4
BANERJEE, j., KIM, H. J., KIM, W., AND KORTH, H.F. Schema evolution in object-oriented persistent databases. In Proceedings of the 6th Advanced Database Symposium (Tokyo, Japan, Aug.). Information Processing Society of Japan's Special Interest Group on Database Systems, 1986, pp. 23-31.
 
5
BOBROW, D. G., AND STEFIK, M. The LOOPS Manual. Xerox PARC, Palo Alto, Calif., 1983.
 
6
BOBROW, D. G., KAHN, K., KICZALES, G., MASINTER, L., STEFIK, M., AND ZDYBEL, F. CommonLoops: Merging Common Lisp and Object-Oriented Programming, Intelligent Systems Laboratory Series ISL-85-8. Xerox PARC, Palo Alto, Calif., 1985.
 
7
 
8
9
 
10
 
11
DITTRICH, K., AND LORIE, R. Version support for engineering database systems. IBM Research Rep. RJ4769, IBM Research, San Jose, Calif., July 1985.
 
12
GOLDBERG, A. Introducing the Smalltalk-80 system. BYTE 6, 8 (Aug. 1981), 14-26.
 
13
 
14
IBM CORPORATION. SQL/Data System: Concepts and Facilities. GH24-5013-0, File No. $370- 50, IBM Corporation, San Jose, Jan. 1981.
 
15
IEEE. Database Eng. 8, 4 (Dec. 1985), Special Issue on Object-Oriented Systems, F. Lochovsky, Ed. IEEE, New York.
 
16
KAISER, G., AND HABERMANN, A. An environment for system version control. Tech. Rep., Dept. of Computer Science, Carnegie-Mellon University, Pittsburgh, Pa., Nov. 1982.
 
17
KATZ, R., AND LEHMAN, T. Database support for versions and alternatives of large design files. IEEE Trans. Softw. Eng. SE-IO, 2 (Mar. 1984), 191-200.
18
 
19
KIM, W. CAD database requirements. Tech. Rep., MCC, Austin, Tex., July 1985.
 
20
 
21
LMI, INC. Lisp Machine Manual. LMI, Cambridge, Mass., 1983.
 
22
LMI, INC. ObjectLISP User Manual. LMI, Cambridge, Mass., 1985.
 
23
LORIE, R., AND PLOUFFE, W. Complex objects and their use in design transactions. In Proc. ACM Database Week: Eng. Design Appl. (May 1983), 115-121.
 
24
MAIER, D., STEIN, J., OTIS, A., AND PURDY, A. Development of an object-oriented DBMS. Tech. Rep. CS/E-86-005, Oregon Graduate Center, Beaverton, Oreg., Apr. 1986.
 
25
MCLEOD, D., NARAYANASWAMY, K., AND BAPA RAO, K. An Approach to Information Management for CAD/VLSI Applications. In Proceedings of the Conference on Databases for Engineering Applications, Database Week 1983 (ACM, May). ACM, New York, 1983, pp. 39-50.
 
26
ROCHKIND, M. The source code control system. IEEE Trans. Softw. Eng. SE-1, 4 (Dec. 1975), 364-370.
27
 
28
 
29
SYMBOLICS, INC. FLA V Objects, Message Passing, and Flavors. Symbolics, Cambridge, Mass., 1984.
 
30
31

CITED BY  107

Collaborative Colleagues:
Jay Banerjee: colleagues
Hong-Tai Chou: colleagues
Jorge F. Garza: colleagues
Won Kim: colleague listing is not available.
Darrell Woelk: colleagues
Nat Ballou: colleagues
Hyoung-Joo Kim: colleagues