Information repository system and method including data objects and a relationship object

• US 6,263,341 B1
• Filed: 06/07/1995
• Issued: 07/17/2001
• 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:
  US08/475,247
• Time in Patent Office: 2,232 Days
• Field of Search: 395/600, 707/100-104
• US Class Current: 707/812
• 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 modeling data in an information repository, comprising the steps of:

identifying and defining a plurality of data objects including said data;

formulating a first set of relationships between said data objects and defining a relationship object;

defining physical storage information for each of said data objects;

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

maintaining method entities for said data objects in said information repository, said method entities including information to implement said first set of relationships in order to display said data in said data objects.

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 data objects.

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 one of said first set of relationships; and

returning one of said data objects and one of said first set of 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 said one of said first set of relationships.

6. The method, as set forth in claim 1, wherein said identifying and defining step further comprises the step of identifying and defining computer application software and said formulating step further comprises the step of formulating a second set of relationships between said computer application software and said data objects.

7. The method, as set forth in claim 1, wherein said identifying and defining step further comprises the step of identifying and defining enterprise data and said formulating step further comprises the step of formulating a third set of relationships between said enterprise data and said data objects.

8. The method, as set forth in claim 1, wherein said identifying and defining step further comprises the step of identifying and defining operational system data and said formulating step further comprises the step of formulating a fourth set of relationships between said operational systems data and said data objects.

9. The method, as set forth in claim 1, wherein said identifying and defining step further comprises the step of identifying and defining databases and data therein said formulating step further comprises the step of formulating a fifth set of relationships between said databases and data therein and said data objects.

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

11. An information repository system, comprising:

a plurality of objects including data;

a relationship object defining a first set of relationships interconnecting said plurality of objects and describing interdependencies between said plurality of objects;

physical storage information associated with each of said plurality of objects; and

rule information defining organization of said plurality of objects into classes and processing of said data included in said plurality of objects in accordance with one of said classes.

12. The information repository system, as set forth in claim 11, wherein said information repository further comprises rules associated with each of said first set of relationships, said rules defining accessibility of corresponding objects of each of said first set of relationships.

13. The information repository system, as set forth in claim 12, wherein said accessibility rules comprise required clearance for accessing said objects.

14. The information repository system, as set forth in claim 12, wherein said accessibility rules specify required data manipulations of said objects for presenting said data.

15. The information repository system, as set forth in claim 11, further comprising a query server for accepting a user input specifying one of said objects and one of said first set of relationships and returning one of said first set of relationships and said object in response to said user input.

16. The information repository system, as set forth in claim 15, wherein said query server further displays said returned object and said one of said first set of relationships.

17. The information repository system, as set forth in claim 11, wherein said plurality of objects include computer application software and said first set of relationships include a second set of relationships between said computer application software and said data objects.

18. The information repository system, as set forth in claim 11, wherein said plurality of objects include enterprise data and said first set of relationships include a third set of relationships between said enterprise data and said data objects.

19. The information repository system, as set forth in claim 11, wherein said plurality of objects include data in operational systems and said first set of relationships include a fourth set of relationships between said operational systems data and said data objects.

20. The information repository system, as set forth in claim 11, wherein said plurality of objects include a plurality of databases and said first set of relationships include a fifth set of relationships between said databases and data therein and said data objects.

21. The information repository system, as set forth in claim 11, wherein said plurality of objects include object oriented systems and objects therein and said first set of relationships include a sixth set of relationships between said object oriented systems, said objects therein.

22. An information repository, comprising:

at least one database for storing and maintaining a collection of enterprise data, said collection of enterprise data including data objects, a separately accessible relationship object defining relationships between said data objects, physical storage information of said objects, and accessibility information of said objects; and

a navigator connected to said at least one database for enabling a user to browse separately among said data objects and said relationship object.

23. An information repository comprising:

a first accessible storage containing a plurality of data objects;

a second separately accessible storage containing a relationship object defining relationships between said data objects; and

means coupled to said first storage and said second storage for separately accessing records in said data objects and relationship object.

24. The repository of claim 23 including a third storage containing an attributes object and said means for accessing including means for accessing records in said attributes object.

25. A method for modeling data in an information repository, comprising the steps of:

identifying and defining a plurality of data objects including said data;

formulating a first set of relationships between said data objects and defining said set of relationship as a relationship object;

defining physical storage information for each of said data objects and separately defining physical storage information for said relationship object; and

storing said data objects and said relationship objects in separately accessible files.