Software model process component

• US 8,370,794 B2
• Filed: 12/30/2005
• Issued: 02/05/2013
• Est. Priority Date: 12/30/2005
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Moosmann, Gerd, Freund, Jens, Latocha, Peter, Kaetker, Stefan
• Primary Examiner(s): Puente, Emerson
• Assistant Examiner(s): Labud, Jonathan R
• Application Number:
  US11/322,851
• Publication Number:
  US 20070162893A1
• Time in Patent Office: 2,594 Days
• Field of Search: None
• US Class Current: 717/104
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques

Abstract

Methods and apparatus, including computer program products, for defining one of a plurality of process components. At least one inbound operation initiated by an external process component to read or modify data encapsulated in a business object solely associated with the process component is defined. Additionally at least one outbound operation to read or modify data encapsulated in a business object solely associated with an external process component is defined. 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 software modeling system comprising at least one memory storing a software modeling tool and at least one processor executing the software modeling tool to perform operations of defining one of a plurality of process components, the operations comprising:

processing at least one input defining at least one inbound operation initiated by an external process component to read or modify data encapsulated in a business object solely associated with the process component; and

processing at least one input defining at least one outbound operation to read or modify data encapsulated in a business object solely associated with an external process component;

wherein each of the process components characterizes software implementing a respective and distinct process, each process component entirely included in exactly one deployment unit, each deployment unit characterizing independently operable software, 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 service interfaces of the process components, each service interface comprising at least one service operation, and each service operation belonging to exactly one process component and comprising a separately-callable function, wherein interaction between a first process component in a first deployment unit and a second process component in a second deployment unit external to the first deployment unit takes place through an incoming message to the first process component from the second process component in the second deployment unit through the respective service interfaces of the first and second process components, and interaction between the first process component and a third process component arranged in the same deployment unit takes place through business objects accessible to the first and third process components in the same deployment unit.

2. A system 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 system as in claim 2, wherein the at least one outbound operation sends a message after it is called.

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

5. A system as in claim 1, wherein at least one of the outbound operations is an asynchronous outbound operation operable to generate an asynchronous message for receipt by an asynchronous inbound operation defined by an external process component.

6. A system as in claim 1, the operations further comprising processing at least one input defining, for each process component, at least one inbound process agent characterizing the at least one inbound operation.

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

8. A system as in claim 1, the operations further comprising processing at least one input defining at least one inbound interface comprising at least two inbound operations.

9. A system as in claim 1, the operations further comprising processing at least one input defining, for each process component, at least one outbound process agent characterizing the at least one outbound operation.

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

11. A system as in claim 1, the operations further comprising processing at least one input defining at least one outbound interface comprising at least two outbound operations.

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

13. A system as in claim 1, wherein at least one 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 system 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 system as in claim 14, the operations further comprising processing at least one input defining communications between the first process component and at least one other process component within the first deployment unit that occur without service operations.

16. Apparatus comprising at least one non-transitory, computer-readable storage medium storing instructions, the instructions operable, when executed by at least one processor, to perform operations of defining one of a plurality of process components in a software modeling environment, the operations comprising:

processing at least one input defining at least one inbound operation initiated by an external process component to read or modify data encapsulated in a business object solely associated with the process component; and

processing at least one input defining at least one outbound operation to read or modify data encapsulated in a business object solely associated with an external process component;

wherein the process component characterizing software implementing a respective and distinct process, the process component entirely included in exactly one deployment unit, each deployment unit characterizing independently operable software, and the process component defining 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 service interfaces of the process components, each service interface comprising at least one service operation, and each service operation belonging to exactly one process component and comprising a separately-callable function, wherein interaction between a first process component in a first deployment unit and a second process component in a second deployment unit external to the first deployment unit takes place through an incoming message to the first process component from the second process component in the second deployment unit through the respective service interfaces of the first and second process components, and interaction between the first process component and a third process component arranged in the same deployment unit takes place through messages passed between the first and third process components in the same deployment unit.

17. The apparatus of claim 16, wherein the process components are associated with a first deployment unit and at least one external process component is associated with a second deployment unit, the deployment units characterizing independently operable software.

18. The apparatus of claim 17, the operations further comprising processing at least one input defining types of messages to transfer between the first and second deployment units.

19. The apparatus of claim 16, the operations further comprising processing at least one input defining at least one business object for the process component.

20. A method for defining one of a plurality of process components in a software modeling environment, the method comprising:

processing at least one input defining at least one inbound operation initiated by an external process component to read or modify data encapsulated in a business object solely associated with the process component; and

processing at least one input defining at least one outbound operation to read or modify data encapsulated in a business object solely associated with an external process component;

wherein each of the process components characterizes software implementing a respective and distinct process, each process component entirely included in exactly one deployment unit, each deployment unit characterizing independently operable software, 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 service interfaces of the process components, each service interface comprising at least one service operation, and each service operation belonging to exactly one process component and comprising a separately-callable function, wherein interaction between a first process component in a first deployment unit and a second process component in a second deployment unit external to the first deployment unit takes place through an incoming message to the first process component from the second process component in the second deployment unit through the respective service interfaces of the first and second process components, and interaction between the first process component and a third process component arranged in the same deployment unit takes place through at least one of business objects accessible to the first and third process components in the same deployment unit or messages passed between the first and third process components in the same deployment unit.

21. The method of claim 20, wherein the process components are associated with a first deployment unit and at least one external process component is associated with a second deployment unit, the deployment units characterizing independently operable software.

22. The method of claim 20, wherein the operation further include:

processing at least one input defining at least one process agent, 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;

processing at least one input defining interactions between at least one inbound process agent of the process component and at least one outbound process agent of an external component; and

processing at least one input defining interactions between at least one inbound process agent of an external process component and at least one outbound process agent of the process component.