Meta model for an enterprise service architecture

• US 8,122,062 B2
• Filed: 12/23/2003
• Issued: 02/21/2012
• Est. Priority Date: 07/22/2003
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Brendle, Rainer, Brunswig, Frank, Dietl, Josef, Fiedler, Thomas, Krane, Rolf, Remmel, Juergen, Ritter, Stephan, Viegener, Johannes
• Primary Examiner(s): TIMBLIN, ROBERT M
• Application Number:
  US10/747,033
• Publication Number:
  US 20050021557A1
• Time in Patent Office: 2,982 Days
• Field of Search: 707/100, 707/803
• US Class Current: 707/803
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Methods and apparatus, including computer program products, for using a meta model for an enterprise service architecture. The meta model includes a first class to represent data organization in a back end data store. The first class includes a data type identifier attribute to permit meta data to identify a data type. The meta model also includes a second class associated with the first class. The second class includes a field identifier attribute to permit meta data to identify fields for a particular data type. The meta model also includes a third class associated with the first class. The third class includes an action identifier attribute to permit meta data to identify an action. In some examples, there is a service provider identifier to permit meta data to identify a service provider class that can effect the action.

Claims

1. A computer program product, tangibly embodied in a storage device, the computer program product comprising instructions operable to cause a data processing apparatus to execute a method for using a meta model for an enterprise service architecture, the method comprising:

defining a first class to represent data types in a back end data store, wherein instances of the first class are data types that are descriptions of business object types in the data store;

defining a second class associated with the first class, wherein instances of the second class represent data fields for a particular one of the data types;

defining a third class associated with the first class, wherein instances of the third class represent actions that can be executed on a particular one of the data types;

defining a service provider identifier to identify a service provider class that can effect each action; and

according to user requests, accessing or modifying data conforming to the defined classes.

2. The computer program product of claim 1, wherein the first class further comprises an association to a fourth class representing a structure of fields included in a particular one of the data types.

3. The computer program product of claim 1, further comprising defining a fourth class representing a service module that is a group of data types.

4. The computer program product of claim 3, further comprising defining a fifth class associated with the fourth class, wherein instances of the fifth class represent queries that can be executed on the data types in the service module represented by the fourth class.

5. The computer program product of claim 1, wherein the first class further comprises a key identifier to represent the data type represented by an instance of the first class.

6. A computer program product, tangibly embodied in a storage device, the computer program product comprising instructions operable to cause a data processing apparatus to execute a method for using a meta model for an enterprise service architecture, the method comprising:

defining an aspect class representing data types in a back end data store, wherein instances of the aspect class are data types that are descriptions of business object types in the data store, the aspect class further comprising a key identifier to represent the data type represented by an instance of the aspect class;

defining a structure class associated with the aspect class, wherein instances of the structure class represent data fields for a particular one of the data types;

defining an aspect action class associated with the aspect class, wherein instances of the aspect action class represent actions that can be executed on a particular one of the data types;

defining a relation class associated with the aspect class, wherein instances of the relation class represent relations between instances of the aspect class; and

according to user requests, accessing or modifying data conforming to the defined classes.

7. The computer program product of claim 6, wherein the aspect class has an association to a service provider class.

8. The computer program product of claim 6, further comprising defining a service module class associated with the aspect class.

9. The computer program product of claim 8, further comprising defining a query class associated with the service module class.

10. The computer program product of claim 9, wherein the association between the query class and the service module class is an aggregation.

11. The computer program product of claim 6, wherein the association between the aspect class and the relation class is an aggregation.

12. The computer program product of claim 11, wherein the aggregation is by a source aspect.

13. The computer program product of claim 6, wherein the association between the aspect class and the aspect action class is an aggregation.

14. A method for storing meta data conforming to a meta model in a repository used by an enterprise service architecture, the method comprising:

defining a first meta data element associated with an aspect class representing a data type in a back end data store, the data type being a description of a business object type;

defining a second meta data element associated with a field class representing a data field of the data type in the back end data store;

defining a third meta data element associated with an action class representing an action that can be executed on the data type in the back end data store;

defining an identifier identifying a service provider class to effect the action defined by the third meta data element; and

storing the meta data elements and the identifier in the repository.

15. The method of claim 14, further comprising verifying the first, second, and third meta data elements conform to the aspect class, the field class, and the action class, respectively.

16. The method of claim 14, further comprising querying the repository to access the meta data elements to determine organization of data in the back end data store.