Skip to end of metadata
Go to start of metadata

Modeling in a process diagram

When modeling a process in a process diagram, two alternative ways of working can be followed: 

  • First you create one or more lanes, then you position tasks, events, gateways etc. within them.
  • Or you first model the tasks, events, gateways etc. in the process and subsequently drag a lane around them.

By placing the process elements you build the framework of the behavior that is modeled. The exact place and size of the process elements are not of direct importance. You can easily change them later. You can later also add or remove process elements.

By using the controls at the top of a lane you can create sub-lanes, add new lanes above or below an existing lane, or remove a lane.

Modeling in a collaboration diagram

There are two ways to include processes in a collaboration:

  • Add existing processes you have created separately at an earlier time, by dragging them from the model browser onto the collaboration diagram. For each process that is added in this way, a pool will automatically be created in the diagram, containing the contents of the process.
  • Create new pools in the collaboration diagram and subsequently add objects and relationships in them to form processes. Within a pool, lanes can be created and within them objects and relationships can be added to organize the objects that are part of the process. For every created pool in the collaboration, a separate process diagram will be created automatically, which can be found in the model browser, in the Processes folder below the model.

Whichever way of working is applied, processes will exist and can be edited as separate components within the model.

Modeling in a choreography diagram

A choreography uses a collaboration as a starting point. In the collaboration diagram, you look where the exchanges of information between the participants (pools) are located. Based on these exchanges you add choreography tasks to the choreography diagram. Each choreography task is a set of one or more information exchanges between two participants. The names of the participants are placed in the task: one at the top, the other one at the bottom.

Subsequently, you finalize the choreography diagram to form a process by adding events, gateways, and sequence flows.

Starting point and endpoint of a process

When modeling a process you start by drawing a start event (starting point) and an end event (endpoint). They delimit the process, they indicate the beginning of the process and the end or result. Between these events, you are modeling the process. Start events do not have incoming relationships, end events have no outgoing relationships. Intervening events can be set with intermediate events and boundary events. Boundary events are not available in a choreography.


A process consists of different activities. If all activities are executed in the correct order, they together form the process, leading to the result or product. Activities can be drawn by using tasks and choreography tasks. To properly express and consistently formulate actions, you usually name the activities in the form verb-noun, for example, "Submit claim" or "Create claim file".


Sequence flows, message flows, and associations can be added to a diagram by drawing lines between the objects. There are two ways of working to add flows and associations.

Method 1: In the Create window pane, click the Sequence flow, Association or Message flow relationship. Next, click the first of the two objects in the diagram that should be connected and draw the appearing line to the other object.

Method 2: Click the first of the two objects in the diagram that should be connected. Subsequently click the control in the lower right corner of the object for drawing a relationship and drag the line to the other object. Depending on the type of relationship that can be drawn from the object, the control represents a sequence flow , message flow or association .