What verifications are defined for hierarchy structures?
This description relates to the default definition of the configuration file and reports.
Report name
Verify semantics of hierarchy structures
Context
According to the default definition, the verification uses the hierarchy structures with the following models:
Process
EPC, Value-added chain diagram, and Function allocation diagram
Organizational unit
Organizational chart
Regulations
Technical terms model
Special for Regulatory Change Management
The report verifies whether:
the Review-relevant attribute is selected. If so, the following mandatory attributes and conditions are checked:
Review frequency
Time limit for the execution of the review in days
Start date of review
The technical term must be connected to precisely one hierarchy owner group.
Tester
No models can be specified for the tester hierarchy. The models that were specified for the organizational unit are used.
Application system type
Application system type diagram
Risk category
Risk diagram
Verifications to be performed
The report verifies whether:
the required attributes are specified for all hierarchy structures:
Name
each element of the hierarchy has a maximum of one parent node.
a hierarchy element is connected to no more than one sign-off owner group (not relevant for application system type and risk category hierarchy).
there are overlaps between tester hierarchy and organizational hierarchy. An organizational unit must not belong to the tester hierarchy and the organizational hierarchy at the same time.
Only trees are permitted for structuring the hierarchy in ARIS Risk & Compliance Manager, no net structures.