Skip to main content

Get help for ARIS Risk and Compliance

Modeling conventions

ARIS Risk and Compliance generates workflows based on master data, for example, a risk assessment workflow based on a risk. The modeling conventions explain the standards relating to the usage of descriptive views, model types, object types, relationship and connection types, and attributes. You can find overviews of the relevant models, objects, relations, and attributes as well as the mapping of objects and attributes between the ARIS modeling environment and ARIS Risk and Compliance.

Content

For some ARIS Risk and Compliance components, specific objects are used to generate a workflow, such as a survey scheduler to generate a survey. The modeling conventions for the components can be found in the chapter of the respective component or with the links above.

Master data

Master data can be specified in ARIS Risk and Compliance or in an ARIS modeling environment. If the master data is not specified in ARIS Risk and Compliance, the data must be transferred to ARIS Risk and Compliance. The documentation of master data (models and objects) in an ARIS modeling environment has a variety of advantages, such as consistency, reduction of complexity, reusability, potential for evaluation, integrity. However, this is only possible if the methodological and functional rules and conventions for modeling are adhered to. We recommend observing the modeling conventions to properly specify the relevant objects in an ARIS modeling environment. Only then all modeled data can be transferred to ARIS Risk and Compliance and reused there.

Transfer user data

Objects and models are transferred to ARIS Risk and Compliance only if the Transfer to ARIS Risk and Compliance attribute (AT_AAM_EXPORT_RELEVANT) is set to true.

API names

For API names refer to the ARIS Method Reference help in the online help of ARIS.

User-defined items

Note that the transfer of data from ARIS to ARIS Risk and Compliance is based on the default ARIS Method. Method enhancements or changes, such as using a user-defined symbol for a function object type, can require the algorithm to be adapted. In this case, ask support.