← Back to Patent Explorer
US5596746A Expired / Lapsed US ⏱️ 0.0 years remaining

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

Assignee: General Electric Co
•
Filing: 1994-10-26
•
Granted: 1997-01-21
•
Expires: 2014-10-26
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

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.

Inventors

  • 👤 Hwa N. Shen
  • 👤 William J. Premerlani
  • 👤 Michael R. Blaha

Bibliographic Details

Application Number —
Jurisdiction US
Data Source google_patents
Last Synchronized 2026-10-26 18:29
CPC Classifications
G; G06; G06F; G06F16/00; G06F16/20; G06F16/28; G06F16/289; G06F16/284; Y; Y10; Y10S; Y10S707/00; Y10S707/99941; Y10S707/99942

Claims Analysis

Total Claims: 14
Claim 1
Independent Claim 304 words
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.
Claim 2
Dependent Claim 304 words
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.
Claim 3
Dependent Claim 29 words
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.
Claim 4
Dependent Claim 57 words
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.
Claim 5
Dependent Claim 79 words
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.
Claim 6
Dependent Claim 57 words
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.
Claim 7
Dependent Claim 79 words
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.
Claim 8
Dependent Claim 320 words
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.
Claim 9
Dependent Claim 320 words
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.
Claim 10
Dependent Claim 32 words
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.
Claim 11
Dependent Claim 79 words
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.
Claim 12
Dependent Claim 57 words
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.
Claim 13
Dependent Claim 57 words
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.
Claim 14
Dependent Claim 79 words
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.

References Cited (Backward Citations)

US5133075A Cited
US5019961A Cited
US5201046A Cited
US5295256A Cited

USPTO Annuity & Maintenance Windows

Annuity Stage Window Opens Payment Deadline Surcharge Period Until Estimated Fee Status
3.5 Years (Year 4) 2000-01-21 2000-07-22 2001-01-21 $2000.00 Window Closed / Lapsed
7.5 Years (Year 8) 2004-01-21 2004-07-22 2005-01-21 $3760.00 Window Closed / Lapsed
11.5 Years (Year 12) 2008-01-21 2008-07-22 2009-01-21 $7700.00 Window Closed / Lapsed

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag