MGP-011: BPMN Guidelines

modeling_guideline
Tags: #<Tag:0x00007f4ebd681038>

#1

MGP-011 | 2017-02-16 | v1.0

BPMN Guidelines

This document describes a number of guidelines you should follow when working with BPMN in edoras one.


Explicit Modeling

Within the BPMN models, you should follow the approach of “explicit modeling”. All elements serve a clear purpose and there should not be any ambiguity. For that reason, we defined a number of rules to follow.

Exclusive Gateways

When you model an explicit decision, always use an exclusive gateway. Make sure that there is one and only one “Default flow”. The branched decision should be joined by an exclusive gateway. Label the gateway with a question and each condition and default flow with the corresponding answer to the question.

GOOD: Exclusive decision modeled with a gateway, one default flow, a joining gateway and proper labeling.

BAD: No exclusive gateway.

BAD: No joining gateway.

BAD: No default flow.

BAD: No labels.

Inclusive Gateways

Most of the above rules also apply for inclusive gateways. The only difference is that they can take more than one path, hence they allow for more than one default flow or empty sequence flow. However, try to avoid unnecessary branches whenever possible.

GOOD: Inclusive Gateway, more than one default flow (optional).

Parallel Gateways

To model concurrency, use parallel gateways. Merge them into another parallel gateways. Unlike other gateways, conditions and default flows will not have any effect on parallel gateways. Do not name their sequence flows or the gateway.

GOOD: Parallel gateway, three sequence and no labeled lines.

Text Annotations

Use Text Annotations to describe what your models do. They are especially useful to describe conditions, events and user tasks. You can also use them to describe the inputs and outputs of processes that are created from the backend.


#2