Software model process interaction

• US 20070168303A1
• Filed: 12/30/2005
• Published: 07/19/2007
• Est. Priority Date: 12/30/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Moosmann, Gerd, Kaetker, Stefan, Freund, Jens, Latocha, Peter
• Granted Patent: US 8,327,319 B2
• Time in Patent Office: Days
• US Class Current: 705/400
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 30/0283 Price estimation or determination

Abstract

Methods and apparatus, including computer program products, for defining interactions between two process components. For each process component, at least one inbound operation and at least one outbound operation are defined. The inbound operations can be initiated by the other process component to read or modify data encapsulated in a business object solely associated with the process component. The outbound operations can read or modify data encapsulated in a business object solely associated with the other process component. Each of the process components characterizes software implementing a respective and distinct process, and each of the process components defines a respective at least one service interface for communicating and interacting with other process components. In addition, all communication and interaction between process components takes place through the respective interfaces of the process components.

Claims

1. A method of defining interactions between two process components, the method comprising:

defining, for each process component, at least one inbound operation initiated by the other process component to read or modify data encapsulated in a business object solely associated with the process component; and

defining, for each process component, at least one outbound operation to read or modify data encapsulated in a business object solely associated with the other process component;

wherein each of the process components characterizes software implementing a respective and distinct process, and each of the process components defines a respective at least one service interface for communicating and interacting with other process components, and all communication and interaction between process components takes place through the respective interfaces of the process components.

2. A method as in claim 1, wherein the at least one outbound operation is called after the business object associated with the outbound operation is read or modified.

3. A method as in claim 2, wherein the at least one outbound operation sends a message after it is called.

4. A method as in claim 1, wherein one or more of the inbound operations is a synchronous operation operable to receive a synchronous message generated by an external synchronous outbound operation defined by the other process component.

5. A method as in claim 1, wherein one or more of the outbound operations is an asynchronous outbound operation operable to generate an asynchronous message for receipt by an asynchronous inbound operation defined by the other process component.

6. A method as in claim 1, further comprising:

defining, for each process component, at least one inbound process agent characterizing the at least one inbound operation.

7. A method as in claim 6, wherein at least one inbound process agent specifies a response to each of at least two inbound operations.

8. A method as in claim 1, further comprising:

defining at least one inbound interface comprising at least two inbound operations.

9. A method as in claim 1, further comprising:

defining, for each process component, at least one outbound process agent characterizing the at least one outbound operation.

10. A method as in claim 1, wherein at least one outbound process agent specifies a trigger to each of at least two outbound operations.

11. A method as in claim 1, further comprising:

defining at least one outbound interface comprising at least two outbound operations.

12. A method as in claim 1, wherein each inbound operation and each outbound operation are solely associated with one of the process components.

13. A method as in claim 1, wherein one or more of the inbound operations is operable to receive a message of a first type and convert it into a message of a second type.

14. A method as in claim 1, wherein a first of the process components is associated with a first deployment unit and a second of the process components is associated with a second deployment unit, the deployment units characterizing independently operable software.

15. A method as in claim 14, further comprising:

defining types of messages to transfer between the first and second deployment units.

16. A method as in claim 1, wherein at least two process components within a single deployment unit communicate without messages.

17. A method of defining interactions between two process components, the method comprising:

defining at least one inbound operation, at least one outbound operation, and at least one business object for each of the process components, each of the process components characterizing software implementing a respective and distinct process, and each of the process components defining a respective at least one service interface for communicating and interacting with other process components, and all communication and interaction between process components taking place through the respective interfaces of the process components;

wherein the inbound operations are operable to start an execution of a step requested in an inbound message originating from the other process component by reading or modifying its respective business object;

wherein the outbound operations are called after their respective business object is modified or read and is operable to trigger a generation of an outgoing message requesting a step reading or modifying a business object associated with the other process component.

18. A method of defining interactions between two process components, the method comprising:

defining, for each process component, a plurality of process agents, each process agent being either an inbound process agent or an outbound process agent, an inbound process agent being operable to receive a message from an inbound operation, an outbound process agent being operable to cause an outbound operation to send a message; and

defining interactions between at least one inbound process agent of a first process component and at least one outbound process agent of a second process component; and

defining interactions between at least one inbound process agent of the second process component and at least one outbound process agent of the first process component;

wherein each of the process components characterizes software implementing a respective and distinct process, and each of the process components defines a respective at least one service interface for communicating and interacting with other process components, and all communication and interaction between process components takes place through the respective interfaces of the process components.

19. A method as in claim 18, wherein a first of the process components is associated with a first deployment unit and a second of the process components is associated with a second deployment unit, the deployment units characterizing independently operable software.

20. A method as in claim 19, further comprising:

defining types of messages to transfer between the first and second deployment units.