Software model integration scenarios
First Claim
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, the operations comprising:
- processing at least one input defining a plurality of process components, each of the process components characterizing software implementing a respective and distinct process, and each of the process components defining at least one respective service interface for interacting with business objects associated with other process components, and all communication and interaction between process components taking place through the respective 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;
dividing the plurality of process components into multiple deployment units, wherein each deployment unit characterizes independently operable software, and each process component is entirely included in exactly one deployment unit; and
processing at least one input defining context independent pair-wise interactions among the plurality of process components to realize a business scenario, 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,wherein the interaction between the first process component and the third process component arranged in the same deployment unit takes place through business objects located in an application layer of the deployment unit.
2 Assignments
0 Petitions
Accused Products
Abstract
Methods and apparatus, including computer program products, to realize a business scenario are described. A plurality of process components and context independent interactions among the process components are defined. Each of the process components characterizes software implementing a respective and distinct process. In addition, each of the process components defines at least one respective service interface for interacting with business objects associated with other process components, and all communication and interaction between process components taking place through the respective interfaces of the process components.
-
Citations
22 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, the operations comprising:
-
processing at least one input defining a plurality of process components, each of the process components characterizing software implementing a respective and distinct process, and each of the process components defining at least one respective service interface for interacting with business objects associated with other process components, and all communication and interaction between process components taking place through the respective 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; dividing the plurality of process components into multiple deployment units, wherein each deployment unit characterizes independently operable software, and each process component is entirely included in exactly one deployment unit; and processing at least one input defining context independent pair-wise interactions among the plurality of process components to realize a business scenario, 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, wherein the interaction between the first process component and the third process component arranged in the same deployment unit takes place through business objects located in an application layer of the deployment unit. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17)
-
-
18. 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 in a software modeling environment, the operations comprising:
-
processing at least one input defining a plurality of process components, each of the process components characterizing software implementing a respective and distinct process, and each of the process components defining at least one respective service interface for interacting with other process components, and all communication and interaction between process components taking place through the respective 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; dividing the plurality of process components into multiple deployment units, wherein each deployment unit characterizes independently operable software, and each process component is entirely included in exactly one deployment unit; and processing at least one input defining context independent pair-wise interactions among the plurality of process components to realize a business scenario, 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, wherein the interaction between the first process component and the third process component arranged in the same deployment unit takes place through business objects located in an application layer of the deployment unit. - View Dependent Claims (19, 22)
-
-
20. A computer-implemented method for grouping process components in a software modeling environment, the method comprising:
-
processing, with a computing system, at least one input defining a plurality of process components, each of the process components characterizing software implementing a respective and distinct process, and each of the process components defining at least one respective service interface for interacting with other process components, and all communication and interaction between process components taking place through the respective 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; dividing, with the computing system, the plurality of process components into multiple deployment units, wherein each deployment unit characterizes independently operable software, and each process component is entirely included in exactly one deployment unit; and processing, with the computing system, at least one input defining context independent pair-wise interactions among the plurality of process components to realize a business scenario, 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, wherein the interaction between the first process component and the third process component arranged in the same deployment unit takes place through business objects located in an application layer of the deployment unit. - View Dependent Claims (21)
-
Specification