Lanes

A lane is a subdivision of a process or a pool. Lanes have no semantics in BPMN. BPMN 2.0 uses lanes as a way to categorizes Flow Elements. Most often lanes represent organizational elements, but in principle any categorization may be used for lanes. Lanes may contain nested sub-lanes. A lane set specifies the categorization represented by the lanes.

See: Business Process Model and Notation (BPMN), version 2.0.

Like a pool a lane is drawn as a rectangular box, its label is not boxed off.

Nested lanes

Mapping the attributes and model associations to ARIS:

Class

BPMN attribute name

Implementation in ARIS

LaneSet

inherits from BaseElement

Object type: Lane (OT_BPMN_LANE)
Symbol: Lane (ST_BPMN_LANE_1)

 

process: Process

The BPMN process model that contains the lane(s).

 

lanes: Lane [0..*]

Object type: Lane (OT_BPMN_LANE)
Symbol: Lane (ST_BPMN_LANE_1)
The source objects in the connection type: Lane belongs to (CT_BELONGS_TO_1) lane

 

parentLane: Lane [0..1]

The target object in the connection type: Lane belongs to (CT_BELONGS_TO_1) lane CT: Lane belongs to lane

Lane

inherits from BaseElement

Object type: Lane (OT_BPMN_LANE)
Symbol: Lane (ST_BPMN_LANE_1)

 

name: string

Attribute type Name (AT_NAME) of object type Lane (OT_BPMN_LANE)

 

partitionElement:
BaseElement [0..1]

Currently not implemented.

 

partitionElementRef:
BaseElement [0..1]

Currently not implemented.

 

childLaneSet: LaneSet
[0..1]

The source objects in the connection type: Lane belongs to (CT_BELONGS_TO_1) lane

 

flowElementRefs:
FlowElement [0..*]

The source objects in the following belongs to (CT_BELONGS_TO_1) connection types:
* Function belongs to lane
* Event belongs to lane
* Rule belongs to lane
* Cluster/data model belongs to lane
* Information carrier belongs to lane