Role-based object models

• US 20050257197A1
• Filed: 09/01/2004
• Published: 11/17/2005
• Est. Priority Date: 05/11/2004
• Status: Abandoned Application

• Current Assignee: SAP AG (SAP SE)
• Original Assignee: SAP AG (SAP SE)
• Inventors: Kalthoff, Wolfgang, Herter, Klaus, Staeck, Jens
• Application Number:
  US10/931,225
• Publication Number:
  US 20050257197A1
• Time in Patent Office: Days
• US Class Current: 717/116
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques

Abstract

A data management system is described for managing software objects to provide services and functionality to users in an efficient manner. The system separates objects from roles associated with the objects, so that applications accessing the system interface only with the roles, rather than with the objects. The roles each provide a functionality to the applications that may be common to multiple ones of the objects. The roles may be tailored to specific accessing applications, without affecting the objects themselves. As a result, the applications may easily gain a desired functionality or behavior by accessing the appropriate role.

Claims

1. An apparatus comprising a storage medium having instructions stored thereon, the instructions including:

a first code segment for maintaining a plurality of software objects, including an object representing an abstraction of an entity and having a plurality of object attributes that characterize the object and the entity;

a second code segment for maintaining a plurality of roles, including a role having a plurality of role attributes derived from the object attributes based on requirements of a requesting application, and operable to provide a functionality to the requesting application to fulfill the requirements; and

a third code segment for receiving a request from the requesting application at the role and providing the functionality to the requesting application, using the role and independently of any interaction between the object and the application.

2. The apparatus of claim 1 comprising a fourth code segment for maintaining relationship information describing relationships between the objects and the roles, based on the object attributes and the role attributes.

3. The apparatus of claim 1 comprising a fourth code segment for adding additional role attributes to the role attributes, independently of the object attributes and based on the requirements of the requesting application.

4. The apparatus of claim 1 comprising a fourth code segment for modifying the role attributes, independently of the object attributes and based on the requirements of the requesting application.

5. The apparatus of claim 1 comprising a fourth code segment for modifying the object attributes, independently of the role attributes.

6. The apparatus of claim 1 comprising a fourth code segment including persistence rules for maintaining the object across multiple sessions.

7. The apparatus of claim 6 comprising a fifth code segment for modifying a selected one of the roles independently of the persistence rules.

8. The apparatus of claim 1 comprising a fourth code segment for maintaining an object model that organizes and defines the objects.

9. The apparatus of claim 1 wherein all interaction between the software objects and the application occurs through the roles.

10. A method comprising:

inputting an object representing an abstraction of an entity and having a plurality of object attributes characterizing the object and the entity;

defining a role by deriving role attributes from the object attributes, based on requirements of an application; and

providing a service to the application to fulfill the requirements, using the role and independently of any communication between the object and the application.

11. The method of claim 10 wherein providing the service comprises:

receiving a request from the application at the role;

accessing the object to obtain object attribute information; and

providing the service to the application, based on the object attribute information.

12. The method of claim 11 wherein accessing the object comprises selecting the object from among a plurality of objects that are associated with the role.

13. The method of claim 12 wherein selecting the object comprises determining required object attributes required by the role to provide the service to the application.

14. The method of claim 11 wherein accessing the object comprises invoking the object according to persistence rules associated with the object.

15. The method of claim 14 wherein providing the service to the application comprises maintaining the role separately from the persistence rules associated with the object.

16. The method of claim 10 comprising adding additional role attributes to the role attributes, independently of the object attributes and based on the requirements of the application.

17. The method of claim 10 comprising modifying the role attributes, independently of the object attributes and based on the requirements of the application.

18. The method of claim 10 comprising modifying the object attributes, independently of the role attributes.

19. The method of claim 10 wherein providing the service comprises conducting all communication between the object and the application through the role.

20. A system comprising:

an object modifier operable to modify object attributes of an object selected from among a plurality of objects that represent abstractions of entities; and

a role modifier operable to modify role attributes, wherein the role attributes partially define a role interface for interfacing with an application to provide a service to the application, independently of communications between the object and the application.

21. The system of claim 20 wherein the role modifier is operable to modify the role attributes based on requirements of the application for providing the service to the application.

22. The system of claim 21 wherein the role modifier is operable to derive the role attributes from the object attributes, based on the requirements.

23. The system of claim 20 wherein the object modifier is operable to modify the objects independently of the roles.

24. The system of claim 20 wherein the role modifier is operable to modify the roles independently of the objects.

25. The system of claim 20 wherein the system includes a master data management system that is operable to provide an object model that includes the objects and the roles and that enables a common use of the objects or the roles to a plurality of applications or systems.

26. The system of claim 25 wherein the master data management system comprises:

a content consolidator that is operable to consolidate objects uploaded from the systems or applications; and

a harmonizer that is operable to ensure consistency of data within the objects or the roles, throughout the systems or applications.