Method for transforming relational data base schemas into object models using ideal table meta models

• US 5,596,746 A
• Filed: 10/26/1994
• Issued: 01/21/1997
• Est. Priority Date: 10/21/1991
• Status: Expired due to Fees

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Shen, Hwa N., Blaha, Michael R., Premerlani, William J.
• Primary Examiner(s): Lim, Krisna
• Application Number:
  US08/329,805
• Time in Patent Office: 818 Days
• Field of Search: 395/500, 395/600
• US Class Current: 1/1
• CPC Class Codes: G06F 16/284 Relational databases
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation

Abstract

An algorithm for transforming data base schema information to object modeling notation utilizes meta models of the data base tables and the target object modeling notation respectively to bridge the gap between the data base schema representation and the object model representation. Detection of associations between classes of objects is performed for one-to-one, one-to-many, and many-to-many associations by analyzing unique key attributes. Once an object meta model is populated, the underlying object model may be displayed using existing software packages.

Claims

1. A computer-implemented method for transforming a data base schema of a relational data base into an object model representative of said data base schema, the object model showing various objects within the data schema and their data attributes, operations, and relationships between each object in the data schema, said method comprising the steps of:

constructing an ideal table meta model of said data base schema;

populating said ideal table meta model with data extracted from said data base schema;

constructing an object diagram meta model of said data base schema from said ideal table meta model;

populating said object diagram meta model with data extracted from said ideal table meta model; and

transforming said object diagram meta model into said object model representative of said data base schema, the object model showing various objects within the data schema and their data attributes, operations, and relationships between each object in the data schema, said transforming including the step of transforming said object diagram meta model into a series of successive, intermediate, populated object diagram meta models describing the object model, wherein said step of transforming said object diagram meta model into said series of successive, intermediate, populated object diagram meta models comprises the steps of determining the multiplicity of associations on classes mapped from tables with foreign keys;

converting classes mapped from tables whose primary keys can be partitioned into mutually exclusive primary key attributes of other classes, to many-to-many associations;

converting classes mapped from tables whose primary keys are primary keys of other classes and whose non-primary key attributes include primary keys of other classes, to one-to-many associations;

converting classes mapped from tables having multiple primary keys and wherein each said primary key is a primary key of another class, to one-to-one associations; and

determining the actual multiplicity of said one-to-many and many-to-many associations.

2. The computer-implemented method of claim 1 further comprising the step of:

outputting a file from said object model, said file being effective as input to an object modeling tool.

3. The computer-implemented method of claim 2 wherein said step of populating said ideal table meta model comprises the steps of:

a) mapping tables from said data base schema to ideal tables in said ideal table meta model; and

b) mapping table columns from said data base schema to ideal table columns in said ideal table meta model.

4. The computer-implemented method of claim 2, wherein said step of populating said object diagram meta model comprises the steps of:

mapping ideal tables to classes in said object diagram meta model;

mapping ideal tables having a foreign key and ideal tables having a primary key equivalent to said foreign key as an association with an nary primary key equal to the primary key of the ideal table containing said foreign key; and

mapping ideal table columns to class attributes.

5. The computer-implemented method of claim 1 wherein said step of populating said ideal table meta model comprises the steps of:

a) mapping tables from said data base schema to ideal tables in said ideal table meta model; and

b) mapping table columns from said data base schema to ideal table columns in said ideal table meta model.

6. The computer-implemented method of claim 1, wherein said step of populating said object diagram meta model comprises the steps of:

mapping ideal tables to classes in said object diagram meta model;

mapping ideal tables having a foreign key and ideal tables having a primary key equivalent to said foreign key as an association with an nary primary key equal to the primary key of the ideal table containing said foreign key; and

mapping ideal table columns to class attributes.

7. A computer system for transforming a data base schema of a relational data base into an object model representative of said data base schema, the object model showing various objects within the data schema and their data attributes, operations, and relationships between each object in the data schema, said computer system comprising a means to interact with a user, a visual display means, a data base management system including a data dictionary, and a computer programmed to:

construct an ideal table meta model of said data base schema;

populate said ideal table meta model with data extracted from said data base schema;

construct an object diagram meta model of said data base schema from said ideal table meta model;

populate said object diagram meta model with data extracted from said ideal table meta model; and

transform said object diagram meta model into said object model representative of said data base schema, the object model showing various objects within the data schema and their data attributes, operations, and relationships between each object in the data schema, said transform including transforming said object diagram meta model into a series of successive, intermediate, populated object diagram meta models describing the object model, wherein said transformation of said object diagram meta model into said series of successive, intermediate, populated object diagram meta models includes determining the multiplicity of associations on classes mapped from tables with foreign keys;

converting classes mapped from tables whose primary keys can be partitioned into mutually exclusive primary key attributes of other classes, to many-to-many associations;

converting classes mapped from tables whose primary keys are primary keys of other classes and whose non-primary key attributes include primary keys of other classes, to one-to-many associations;

converting classes mapped from tables having multiple primary keys and wherein each said primary key is a primary key of another class, to one-to-one associations; and

determining the actual multiplicity of said one-to-many and many-to-many associations.

8. The computer system of claim 7, wherein said programmed computer is further programmed to:

output a file from said object model, said file being effective as input to an object modeling tool.

9. The computer system of claim 8, wherein said computer programmed to populate said object diagram meta model is programmed to:

map ideal tables to classes in said object diagram meta model;

map ideal tables having a foreign key and ideal tables having a primary key equivalent to said foreign key as an association with an nary primary key equal to the primary key of the ideal table containing said foreign key; and

map ideal table columns to class attributes.

10. The computer system of claim 8 wherein said computer programmed to populate said ideal table meta model is programmed to:

a) map tables from said data base schema to ideal tables in said ideal table meta model; and

b) map table columns from said data base schema to ideal table columns in said ideal table meta model.

11. The computer system of claim 7 wherein said computer programmed to populate said ideal table meta model is programmed to:

a) map tables from said data base schema to ideal tables in said ideal table meta model; and

b) map table columns from said data base schema to ideal table columns in said ideal table meta model.

12. The computer system of claim 7, wherein said computer programmed to populate said object diagram meta model is programmed to:

map ideal tables to classes in said object diagram meta model;

map ideal tables having a foreign key and ideal tables having a primary key equivalent to said foreign key as an association with an nary primary key equal to the primary key of the ideal table containing said foreign key; and

map ideal table columns to class attributes.