Software modeling
First Claim
Patent Images
1. A computer-implemented 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 comprising at least one semantically related business object, 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, such that all communication and interaction between a particular 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.
390 Citations
20 Claims
-
1. A computer-implemented 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 comprising at least one semantically related business object, 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, such that all communication and interaction between a particular 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 computer-implemented method comprising:
-
defining at least two process components, each process component characterizing software implementing a respective and distinct business process and defining a respective service interface for interacting with the other process component, each process component comprising at least one semantically related business object, 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, the interactions comprising context independent interactions among the at least two process components, such that communication and the interactions between the at least two process components take place through the respective service interfaces of the at least two process components.
-
-
15. A computer-implemented method comprising:
-
displaying, in a first view, a process interaction map illustrating interactions among a plurality of process components, each of the process components comprising at least one semantically related business object and 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 at least one inbound operation of the selected process component, the business object part identifying all of the semantically related business objects associated with the selected process component, the outbound part identifying all external process components utilized by at least one outbound operation 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 process component, 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 the inbound operation, the outbound process agent being operable to cause the outbound operation to send a message. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification