Enterprise architecture analysis framework database

• US 20060106825A1
• Filed: 11/18/2004
• Published: 05/18/2006
• Est. Priority Date: 11/18/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Cozzi, Matthew
• Granted Patent: US 7,970,729 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/288 Entity relationship models

Abstract

A method of modeling an enterprise includes storing core objects, where the core objects include an information object defining information used in the enterprise, a participant object defining a participant in the enterprise, an enabler object defining a tool used in the enterprise, and an activity object defining a process performed in the enterprise, and storing relationship objects that define interactions between two or more of the core objects.

Claims

1. A method of modeling an enterprise, comprising:

storing core objects, the core objects comprising an information object defining information used in the enterprise, a participant object defining a participant in the enterprise, an enabler object defining a tool used in the enterprise, and an activity object defining a process performed in the enterprise; and

storing relationship objects that define interactions between two or more of the core objects.

2. The method of claim 1, further comprising:

storing a cell comprising at least some of the core objects and the relationship objects, the cell comprising a set of objects needed to complete a specific objective and/or derive the information.

3. The method of claim 2, further comprising:

storing a process scenario object that links the cell with other cells, the process scenario object defining how the information is transformed over time.

4. The method of claim 3, further comprising:

defining influences and settings that have a bearing on the process scenario, the process scenario object being built in accordance with the influences and settings.

5. The method of claim 3, wherein the process scenario object comprises data defining a domain to which the process scenario object belongs.

6. The method of claim 5, wherein the domain comprises a decision-making layer within the enterprise.

7. The method of claim 3, wherein the information object is common to the process scenario object and a second process scenario object.

8. The method of claim 3, wherein the activity object and the information object correspond to associated values.

9. The method of claim 8, further comprising:

determining a value of the process scenario based the associated values.

10. The method of claim 1, wherein the relationship objects define one of common object relationships and cross-object relationships.

13. The method of claim 8, wherein the cell and the other cells define a process scenario, and the method further comprises:

determining a value of the process scenario based on a value of the activity object and a value of the information object.

14. The method of claim 3, wherein the value of the process scenario comprises a ratio of the value of the activity object to the value of the information object.

11. A method of modeling an enterprise, comprising:

building core objects that define elements of an enterprise;

building relationship objects that define interactions between two or more of the core objects;

building a cell comprising at least some of the core objects and the relationship objects; and

relating the cell to other cells.

12. The method of claim 11, wherein the core objects comprise an information object defining information used in the enterprise, a participant object defining a participant in the enterprise, an enabler object defining a tool used in the enterprise, and an activity object defining a process performed in the enterprise.

15. A memory for storing data for access by an application program being executed on a data processing system, comprising:

a data structure stored in the memory, the data structure including information resident in a database used by the application program and comprising;

core objects, the core objects comprising an information object defining information used in the enterprise, a participant object defining a participant in the enterprise, an enabler object defining a tool used in the enterprise, and an activity object defining a process performed in the enterprise; and

relationship objects that define interactions between two or more of the core objects.

16. The memory of claim 15, wherein the information further comprises a cell comprising at least some of the core objects and the relationship objects, the cell comprising a set of objects needed to complete a specific objective and/or derive the information.

17. The memory of claim 16, wherein the information further comprises a process scenario object comprising the cell linked with other cells, the process scenario object defining how the information is transformed over time.

18. The memory of claim 17, wherein the cell and other cells are linked by information objects.

19. The memory of claim 17, wherein the information further comprises an environmental object that defines an environment in which a process scenario defined by the process scenario object operates.

20. The memory of claim 17, wherein the information further comprises an influences object that defines an influence on a process scenario defined by the process scenario object.