The BPMN activity is represented by the ARIS object type Function.
BPMN 2.0 differentiates three basic types of activities: task (atomic activity), subprocess (non-atomic activity) and call activity. The symbols depicting these activity types are provided in the ARIS Symbols bar.
When the modeler places an activity symbol, the software sets the corresponding value of the ARIS attribute type Activity type (AT_BPMN_ACTIVITY_TYPE). This activity type controls the correct behavior of the symbol. For example: A subprocess may have embedded flow elements, a task must not; a call activity may reference another task or process, tasks and subprocesses must not.
Mapping the attributes and model associations to ARIS
Class |
BPMN attribute name |
Implementation in ARIS |
---|---|---|
Activity |
inherits from FlowElement |
Object type: Function (OT_FUNC) |
|
Compensation activity:: boolean = false |
Attribute type Compensation activity: (AT_BPMN_COMPENSATION_ACTIVITY.TRM=Compensation activity) in the attribute type group BPMN 2.0 attributes of object type Function |
|
loopCharacteristics: LoopCharacteristics [0..1] |
see below: Loop characteristics |
|
resources: ActivityResource [0..*] |
Currently not implemented. |
|
default: SequenceFlow [0..1] |
Attribute type Sequence flow condition (AT_BPMN_SEQ_FLOW_CONDITION) in the attribute type group BPMN 2.0 attributes of the following conenction types: |
|
ioSpecification: InputOutputSpecification [0..1] |
Currently not implemented. |
|
properties: Property [0..*] |
Currently not implemented. |
|
boundaryEventRefs: BoundaryEvent [0..*] |
Connection type: Function can trigger event |
|
dataInputAssociations: DataInputAssociation [0..*] |
Currently not implemented. |
|
dataOutputAssociations: DataOutputAssociation [0..*] |
Currently not implemented. |
|
startQuantity: integer = 1 |
Currently not implemented. |
Class |
completionQuantity: integer = 1 |
Currently not implemented. |