EPC in ARIS and Prime Arch

Data, risks and rules in EPC

Läs på svenska

A workflow can be supplemented with information about what the work uses, what might go wrong and which requirements need to be considered. This mapping brings several such aspects into the EPC diagram.

Here, information carrier maps to Data Object (D41), cluster to Information Object (I31), and KPI instance to Indicator (S33). Risk maps to Risk (R32), business policy to Rule (R31), and requirement to Non-functional Requirement (X01).

Check what the source object describes

Read these mappings together with the source object’s content. An information carrier may describe a carrier, for example; review that meaning before treating it as a data object. Similarly, analyse a cluster’s content before classifying it as an information object.

ARIS requirement covers requirements more broadly. X01 concerns non-functional requirements. Use this mapping for requirements with that meaning, not as a rule that every requirement is X01.

Metaobjects in the illustration

The linked metaobject pages are currently in Swedish.

• D41 Data Object
• I31 Information Object
• S33 Indicator
• R32 Risk
• R31 Rule
• X01 Non-functional Requirement

The mapping illustrated

Open the image to enlarge it.

Source

The mapping is based on EPC in ARIS mapped to Prime Arch (A). ARIS symbols and descriptions are reproduced from EPC in ARIS, Software AG, 2024. The lines show the mapping between the notations.