Show TOC

Modeling Process Flow Variants of a Process Integration ScenarioLocate this document in the navigation structure

Use

The Process Integration scenario design environment in the Enterprise Services Builder does not permit the qualified representation of branches (AND, OR, XOR) or other complex process modeling constructs.

  • When representing different process flow variants you have to make a compromise between the comprehensibility of Process Integration scenarios on the one hand and the number of separately defined Process Integration scenarios on the other.

  • The following conventions apply:

    • If there are optional actions (and communication steps) that can be run through, or not, then these shoud not be included in the Process Integration scenario and are to be declared as optional in the documentation. The Process Integration scenario is understood in such a way that the optional steps do not necessarily have to be executed.

    • If there are different branches in the process logic (OR, XOR) where the branches are located in different application components, then both branches are to be included in the Process Integration scenario and explained in the documentation.

    • If there are different branches in the process logic (OR, XOR) where the branches are located in the same application component, then you should think about whether the branches really need to be modeled or not.

  • The Process Integration scenario design environment in the Enterprise Services Builder does not permit explicit variant management. Therefore we recommends that you included as many different variants as possible in a Process Integration scenario. However, should the complexity increase out of proportion, or if the comprehensibility is impaired, then we recommends thst you model the variants as separate Component Views of the same Process Integration scenario.