Software modeling
First Claim
1. A method comprising:
- defining a plurality of process components, each of the process components characterizing software implementing a respective and distinct business process, and each of the process components defining a respective service interface for interacting with other process components;
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
defining context independent interactions among the plurality of process components;
wherein all communication and interaction between a process component in one deployment unit and any process component in any other deployment unit takes place through the respective service interfaces of the process components.
2 Assignments
0 Petitions
Accused Products
Abstract
Methods and apparatus, including computer program products, to realize a software model are described. A plurality of process components characterizing software implementing a respective and distinct business process is defined, and each of the process components defining a respective service interface for interacting with other process components. The plurality of process components is divided into multiple deployment units, wherein each deployment unit characterizes independently operable software, and each process component is entirely included in exactly one deployment unit. Context independent interactions are defined among the plurality of process components.
-
Citations
20 Claims
-
1. A method comprising:
-
defining a plurality of process components, each of the process components characterizing software implementing a respective and distinct business process, and each of the process components defining a respective service interface for interacting with other process components;
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
defining context independent interactions among the plurality of process components;
wherein all communication and interaction between a process component in one deployment unit and any process component in any other deployment unit takes place through the respective service interfaces of the process components. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. A method comprising:
-
defining at least two process components, each process component associated with software defining;
an inbound operation to modify or read data encapsulated in a business object solely associated with the process component; and
an outbound operation to modify or read data encapsulated in a business object solely associated with an external process component; and
defining interactions among the at least two process components to be handled by the inbound operations and the outbound operations.
-
-
15. A method comprising:
-
displaying, in a first view, a process interaction map illustrating interactions among a plurality of process components, each of the process components characterizing software implementing a respective and distinct business process, and each of the process components defining a respective service interface for interacting with other process components;
displaying, in a second view, a process component architectural design illustrating an inbound part, a business object part, and an outbound part for a selected process component, the inbound part identifying all external process components that use one or more inbound operations of the selected process component, the business object part identifying all business objects associated with the selected process component, the outbound part identifying all external process components utilized by one or more outbound operations of the selected component; and
displaying, in a third view, a process component interaction architectural design illustrating message transfer between exactly two process components to modify or read business objects associated with each business object, each process component illustrating a plurality of process agents, each process agent being either an inbound process agent or an outbound process agent, the inbound process agent being operable to receive a message from an inbound operation, the outbound process agent being operable to cause an outbound operation to send a message. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification