Chapter 14 Generating Other Models from a BPM
You can wish to generate an executable BPM from an analysis BPM, in order to implement the analysis BPM you have defined.
The executable BPM is more constrained than the analysis BPM. Transformations globally consist in ensuring that the validity of the executable BPM is preserved.
Objects that are not supported in the executable language are automatically removed: resources and resource flows. However, data are transformed into variables.
The following transformations are executed when you generate an executable BPM from an analysis BPM:
The executable BPM requires a top-level process container.
When a graph of activities is defined under a package or a model, a top-level process is automatically created and the whole graph of activities is moved under it.
For each unrelated set of activities, a top-level process is created. An activity (start, end, process, decision, and synchronization) is related to another one if a flow exists between them or if they are displayed in the same diagram. The diagrams are also moved under the composite process and their contents are preserved.
The executable BPM does not support multiple start objects in the composite process.
All start objects that appear under composite processes and all start objects that appear simultaneously in the same top-level diagram are merged to become one.
A shortcut of process can be used in analysis models to reuse an existing process inside a graph. This is a fast way to reuse a process.
In the executable BPM, the shortcut of a process in a graph is automatically replaced with a duplication of the target object of the shortcut, as the executable BPM does not support a process to be implemented by another process.
For executable languages that do not support process reusability, the call of a reusable process is replaced with a duplication of the process. If the reusable process is an unloaded external shortcut, the activity process that calls the shortcut is preserved and detached from the shortcut.
The executable BPM does not support the association of a message format with a flow, as the exchange of information is no longer managed by flows in this type of BPM view.
All message formats are automatically detached from flows.
In the analysis model, a flow can have one of the following flow types: Success, Timeout, Technical Error and Business Error.
The Timeout, Technical Error and Business Error flow types are automatically replaced with event objects with Timer or Fault stereotype. Event objects are associated with the flow to define event handlers.
Data objects are automatically replaced with variables. The data attachment to flow or message format is lost.
| Copyright (C) 2007. Sybase Inc. All rights reserved. |
| |