A Normal Form Object-Oriented Entity Relationship Diagram

A normal form object-oriented entity relationship (OOER) diagram is presented to address a set of OO data modelling issues, viz. the inability to judge the quality of an OO schema, the presence of inheritance conflicts in ISA hierarchies, the lack of explicit support for different relationship types (m-n, n-ary, recursive etc.) in some OO data models and the lack of general and flexible support for views. Three approaches are described to translate good quality OO schemas from a normal form OOER diagram. The first approach translates OO schemas whose underlying OO data models support the notion of relationship. There are no undesirable redundancies in the translated schemas. The second approach provides for OO data models that do not support the notion of relationship. Some redundancies may arise because of m-n, n-ary relationships, but these can be controlled. The third approach treats each OO schema as an external schema of a conceptual schema represented by a normal form OOER diagram. Redundancies may exist at the external schema level, but no redundancies exist at the conceptual schema level.

[1]  Catriel Beeri,et al.  A complete axiomatization for functional and multivalued dependencies in database relations , 1977, SIGMOD '77.

[2]  Peter F. Sweeney,et al.  Three steps to views: extending the object-oriented paradigm , 1989, OOPSLA '89.

[3]  O. Deux,et al.  The O2 system , 1991 .

[4]  Tok Wang Ling,et al.  Overview of an Entity-Relationship Based Database Management System , 1992, Future Databases.

[5]  Tok Wang Ling,et al.  Generating Object-Oriented Views from an ER-Based Conceptual Schema , 1993, DASFAA.

[6]  Tok Wang Ling,et al.  Inheritance Conflicts in Object-Oriented Systems , 1993, DEXA.

[7]  Jay Banerjee,et al.  Data model issues for object-oriented applications , 1987, TOIS.

[8]  Tok Wang Ling A Three Level Schema Architecture ER-based Data Base Management System , 1987, ER.

[9]  Laurian M. Chirica,et al.  The entity-relationship model: toward a unified view of data , 1975, SIGF.

[10]  Harold Ossher,et al.  Extending Objects to Support Multiple Interfaces and Access Control , 1990, IEEE Trans. Software Eng..

[11]  Ming-Chien Shan,et al.  Iris: An Object-Oriented Database Management System , 1989, ACM Trans. Inf. Syst..

[12]  Peter F. Sweeney,et al.  Three steps to views: extending the object-oriented paradigm , 1989, OOPSLA 1989.

[13]  O. Deux,et al.  The O2 system , 1991 .

[14]  Database and Expert Systems Applications , 1996, Lecture Notes in Computer Science.

[15]  Jay Banerjee,et al.  Composite object support in an object-oriented database system , 1987, OOPSLA 1987.

[16]  C. J. Date An Introduction to Database Systems, Volume I, 5th Edition , 1986 .

[17]  Serge Abiteboul,et al.  Objects and views , 1991, SIGMOD '91.

[18]  Won Kim,et al.  Introduction to Object-Oriented Databases , 1991, Computer systems.

[19]  Won Kim,et al.  Indexing Techniques for Object-Oriented Databases , 1989, Object-Oriented Concepts, Databases, and Applications.

[20]  Tok Wang Ling A Normal Form For Entity-Relationship Diagrams , 1985, ER.

[21]  Tok Wang Ling,et al.  Toward resolving inadequacies in object-oriented data models , 1993, Inf. Softw. Technol..

[22]  Tok Wang Ling External Schemas of Entity-Relationship Based Data Base Management Systems , 1988, ER.

[23]  Michael Stonebraker,et al.  The POSTGRES Data Model , 1987, Research Foundations in Object-Oriented and Semantic Database Systems.

[24]  Tok Wang Ling,et al.  A Prolog Implementation of an Entity-Relationship Based Database Management System , 1991, ER.

[25]  Fernando Vélez,et al.  O2, an Object-Oriented Data Model , 1992, Building an Object-Oriented Database System, The Story of O2.

[26]  Jay Banerjee,et al.  Composite object support in an object-oriented database system , 1987, OOPSLA '87.