Information repository system and method for modeling data

• US 5,978,811 A
• Filed: 07/29/1992
• Issued: 11/02/1999
• Est. Priority Date: 07/29/1992
• Status: Expired due to Term

• Current Assignee: Texas Instruments, Inc.
• Original Assignee: Texas Instruments, Inc.
• Inventors: Smiley, Phillip L.
• Primary Examiner(s): Kulik, Paul V.
• Application Number:
  US07/921,826
• Time in Patent Office: 2,652 Days
• Field of Search: 395/600, 707/103, 707/1, 707/10, 707/100, 707/102, 707/104, 705/1
• US Class Current: 1/1
• CPC Class Codes: G06F 16/288 Entity relationship models
• CPC Class Codes: Y10S 707/954 Relational
• CPC Class Codes: Y10S 707/955 Object-oriented
• CPC Class Codes: Y10S 707/959 Network
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing

Abstract

A data model for an information repository (10) models data as objects (12), the relationships (14) or interdependencies between the data, their physical storage or access information (18) and rules or methods of accessing the data (16).

Claims

1. A method for modelling data in an information repository, comprising the steps of:

identify and defining a plurality of data objects including data;

formulating relationships between said data objects;

defining physical storage information for each of said data objects;

storing said data objects, relationships and physical storage information as a network including a plurality of nodes associated with said data objects and said relationships as connectivities therebetween and;

maintaining a method entity for said information repository including information to implement said relationship in a database.

2. The method, as set forth in claim 1, wherein said maintaining step comprises the step of defining required clearance for accessing said data objects.

3. The method, as set forth in claim 1, wherein said method further comprises the step of specifying data manipulation of said data objects for presenting said data in said object.

4. The method, as set forth in claim 1, wherein said method further comprises the steps of:

accepting a user input specifying one of said data objects and said relationships; and

returning one of said data objects and relationships in response to said user input.

5. The method, as set forth in claim 4, wherein said returning step comprises the step of displaying said one of said data objects and relationships.

6. The method, as set forth in claim 1, wherein said data object identification and defining step comprises the step of identifying and defining computer application software and said relationship formulating step comprises the step of formulating relationship between said computer application software.

7. The method, as set forth in claim 1, wherein said data object identification and defining step comprises the step of identifing and defining enterprise data and said relationship formulating step comprises the step of formulating relationships between said enterprise data.

8. The method, as set forth in claim 1, wherein said data object identification and defining step comprises the step of identifying and defining data in operational systems and said relationship formulating step comprises the step of formulating relationships between said data of said operational systems.

9. The method, as set forth in claim 1, wherein said data object identification and defining step comprises the step of identifying and defining databases and said relationship formulating step comprises formulating relationships between said databases and data therein.

10. The method, as set forth in claim 1, wherein said data object identification and defining step comprises the step of identifying and defining object oriented systems and objects therein and said relationship formulating step comprises the step of formulating relationships between said object oriented systems and between objects therein.

11. An information repository, comprising:

at least one database for storing and maintaining a collection of enterprise data, said collection of enterprise data including objects containing data of interest, relationship entity containing relationships between said objects, method entity containing information to implement said relationship entity, access information entity containing physical storage information of said objects and accessibility information of said objects; and

a navigator connected to said database for enabling a user to browse among said objects, said relationship entity, method entity and access information entity to build operational data in a more accessible format.