Method of transforming graphical object diagrams to product data manager schema

• US 5,937,410 A
• Filed: 10/16/1997
• Issued: 08/10/1999
• Est. Priority Date: 10/16/1997
• Status: Expired due to Fees

• Current Assignee: Johnson Controls Technology Company (Johnson Controls International plc)
• Original Assignee: Johnson Controls Technology Company (Johnson Controls International plc)
• Inventors: Shen, Hwa N.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): Shah, Sanjiv
• Application Number:
  US08/951,331
• Time in Patent Office: 663 Days
• Field of Search: 707/103, 707/101, 707/100
• US Class Current: 1/1
• CPC Class Codes: G06F 16/289 Object oriented databases
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure

Abstract

The present invention provides a method, and associated system, for converting object oriented models into an actual operable database. The method and system automatically converts object oriented models into inputs that are compatible with a target product data manager platform. Errors are detected during the conversion process, thereby allowing the PDM designer to correct the errors before actual PDM platform implementation. The method and system of the present invention generate ancillary outputs that further enhance the usefulness of the method and system. Errors and inconsistencies between the object oriented model and the PDM platform can thus more easily be tracked, thereby enhancing the integrity of the resulting PDM database.

Claims

1. A method of constructing a database, comprising the steps of:

generating an object relationship model;

extracting a logical model from the object relationship model that includes;

compiling the logical model into recognizable entities and relationships having a pre-defined grammar context; and

transforming the compiled ogical model into a hierarchial model of context-free grammar schema files for use in a database system.

2. The method of claim 1, wherein the step of extracting a logical model from the object relationship model comprises the step of compensating for structural inconsistencies in the object relationship model.

3. The method of claim 2, wherein the step of compensating for structural inconsistencies in the object relationship model comprises filtering object relationship model information that is not essential to the step of compiling the logical model.

4. The method of claim 1, wherein the step of extracting the logical model from the object relationship model comprises the step of identifying elements of the logical model;

and

extracting the identified elements from the logical model for use in the step of compiling the logical model.

5. The method of claim 1, wherein the step of compiling the logical model comprises the step of identifying all entities, relationships and associated information;

and

creating files from the entities, relationships and associated information for use in the step of transforming the compi ed logical model to the hierarchial model.

6. The method of claim 1, wherein the step of transforming the logical model to the hierarchial model comprises the step of mapping information in the logical model to the hierarchial model.

7. The method of claim 1, further comprising the step of detecting errors and generating error warnings during the step of transforming the compiled logical model to the hierarchial model.

8. The method of claim 1, further comprising the step of generating ancillary database files that assist in building the target database platform.

9. The method of claim 1, wherein the step of transforming the compiled logical model to a hierarchial model comprises the step of transforming the compiled logical model to a plurality of context-free grammar product data manager files for a target product data manager platform.

10. A method of transforming graphical object oriented models into a product data manager database platform, comprising the steps of:

generating an object oriented (OO) model output;

extracting a logical (OO) model from the step of generating an (OO) model output;

determining if structural inconsistencies exist in the logical (OO) model;

compensating for the structural inconsistencies;

compiling the logical (OO) model into recognizable entities and relationships; and

transforming the compiled logical (OO) model to a target product data manager (PDM) platform.

11. A database generator, comprising:

a data input through which input data indicative of relationships among objects is input;

an object modeler in communication with the data input that generates an object model of the database from the data;

a compiler connected to the object modeler that transforms the object model of the database into a hierarchial model; and

a data output that outputs the database hierarchial model for implementation purposes.

12. The database generator of claim 11, wherein the compiler generates, and the data output outputs, error and warning files indicative of inconsistencies detected by the compiler during transformation of the object model into the database hierarchial model.

13. The database generator of claim 11, wherein the database output further outputs database platform dependent ancillary files that help to further define the database hierarchial model.

14. The database generator of claim 11, wherein the database hierarchial model comprises a product data manager schema files for a product data manager platform.

15. The database generator of claim 11, wherein the compiler comprises:

a filter that filters presentation layer data from the input data; and

a logical model extractor that extracts a logical model from the output model, the logical model containing grammar to be parsed to general class files by the compiler.

16. The database generator of claim 15, wherein the compiler further comprises a software block that parses the logical model grammar into a plurality of context-free grammar class files.

17. The database generator of claim 16, wherein the compiler further comprises a target mapping engine that maps the class files to a plurality of database schema files that comprise the database hierarchial model.