v1.x.y
Modeling Conventions and Guidelines
Semantic Check Rule Catalogue
Semantic Checks help ensure that models created within the One Standard Foundation are not only structured consistently, but also comply with defined modelling conventions and quality requirements. This page provides an overview of the individual validation rules, including their purpose, rule code, validation logic, and guidance on how to resolve identified issues.
Process Landscape L1-L3
-
[PM0] - Level identification
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: ModelsRule:
• Validation: Checks the represented model level based on the symbols used
• Severity: Note or Error
• Issue description: Attribute(s) missing: [name of attribute type and the respective value] -
[PM1] - Required model attribute is missing or not correct
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: ModelsRule:
• Validation: Checks whether the Process Landscape Model has all required attributes correctly maintained. Please note that this rule also validates all other languages defined by the administrator.
• Severity: Error
• Issue description: [Attribute is]/[Attributes are] missing: [List of missing attributes] or [Attribute Type NAME] has an incorrect value -
[PM5] - Superior object is not correct
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: ModelsRule:
• Validation: Checks whether the Process Landscape Model has the correct superior object
• Severity: Error
• Issue description: This Level [2/3] model must have exactly one superior object, which is a [Process Area/Process Chain] element that occurs one level above and in this model. A Level 1 model must not have a superior object, except for structuring items. -
[PM6] - Model is located in the wrong group
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: ModelsRule:
• Validation: Checks whether the Process Landscape Model is located in the correct group
• Severity: Error
• Issue description: Case: A wrong group was used, but the correct group exists: Move the model to the correct group under Process Landscape at the appropriate level node. // Case: The correct group no longer exists: Contact your ARIS Admin because the correct group is missing (Name / GUID) -
[PM9] - Model name and group name are not the same
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: ModelsRule:
• Validation: Checks whether the Process Landscape Model name is equal to the group name
• Severity: Warning
• Issue description: Model name and group name must be identical -
[PM10] - Model name and superior function are not the same
Context:
• Architecture: Process Landscape L2-L3
• ARIS type: ModelsRule:
• Validation: Checks whether the Process Landscape Model name is equal to the superior object name
• Severity: Warning
• Issue description: Model name and superior function name must be identical -
[PO1] - Required object attribute is missing or not correct
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the occurred function in the Process Landscape Model has all required attributes correctly maintained. Please note that this rule also validates all other languages defined by the administrator.
• Severity: Error
• Issue description: Attribute(s) missing: [name of attribute type and the respective value] -
[PO6] - Wrong assignment(s)
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the occurred function in the Process Landscape Model has the correct assigned model type and assignment count
• Severity: Error
• Issue description: Too many models are assigned, the wrong model is assigned, or wrong models are assigned. Correct convention: Only one assignment of type [model type] is allowed. -
[PO7] - Object definition is in the wrong group
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the definition of the occurred function in the Process Landscape Model is stored in the correct group
• Severity: Error
• Issue description: The correct group should be: [Group path] -
[PO8.a] - The mapped document does not yet occur in the library model
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the document mapped to the occurred function in the Process Landscape Model has further occurrences in the required library model(s)
• Severity: Warning
• Issue description: You must also add this document to the Document Library model via occurrence copy. -
[PO8.b] - The mapped metric does not yet occur in the library model
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the metric mapped to the occurred function in the Process Landscape Model has further occurrences in the required library model(s)
• Severity: Warning
• Issue description: You must also add this metric to the Metric Library model via occurrence copy. -
[PO9] - Object has occurrences which are not allowed
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the occurred function in the Process Landscape Model has incorrect occurrence copies in other models
• Severity: Error
• Issue description: The object already has occurrences in other models, which conflict with the current occurrence. Rules by symbol type: Process Category: Only one occurrence is allowed on Level 1 across the entire Process Landscape. Process Area: Only one occurrence is allowed on Level 1. One additional occurrence is allowed in the Level 2 model assigned to the current object. Process Group: Only one occurrence is allowed on Level 2. One additional occurrence is allowed in the Level 3 model assigned to the current object. Process: Only one occurrence is allowed across the Process Landscape level. Additional occurrence copies are allowed in E2E Level 2 models. -
[PO10] - The object relationships are not correct
Context:
• Architecture: Process Landscape L1-L3
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the occurred function in the Process Landscape Model has the required connection in this model
• Severity: Error
• Issue description: There is a connection missing between this object and another [Process Category/Process Area/Process] object
E2E Business Scenario (L1-L2)
-
[EM0] - Level identification
Context:
• Architecture: E2E Business Scenario L1-L2
• ARIS type: ModelsRule:
• Validation: Checks the represented model level based on the symbols used and superior object occurrences
• Severity: Note or Error
• Issue description: Identified and checked as Level [1/2] model. -
[EM1] - Required model attribute is missing or not correct
Context:
• Architecture: E2E Business Scenario L1-L2
• ARIS type: ModelsRule:
• Validation: Checks whether the E2E Model has all required attributes correctly maintained. Please note that this rule also validates all other languages defined by the administrator.
• Severity: Error
• Issue description: Attribute(s) missing: [name of attribute type and the respective value] -
[EM5] - Superior object is not correct
Context:
• Architecture: E2E Business Scenario L1-L2
• ARIS type: ModelsRule:
• Validation: Checks whether the E2E Model has the correct superior object
• Severity: Error
• Issue description: This Level 2 model must have exactly one superior object, which is an E2E Business Scenario element that occurs on the End-to-End Business Scenario Map (Level 1). -
[EM6] - Model is located in the wrong group
Context:
• Architecture: E2E Business Scenario L1-L2
• ARIS type: ModelsRule:
• Validation: Checks whether the E2E Model is located in the correct group
• Severity: Error
• Issue description: The correct group should be: [Group path] -
[EM10] - Model name and superior function are not the same
Context:
• Architecture: E2E Business Scenario L2
• ARIS type: ModelsRule:
• Validation: Checks whether the E2E Model name is equal to the superior object name
• Severity: Warning
• Issue description: Model name and superior function name must be identical -
[EO1] - Required object attribute is missing or not correct
Context:
• Architecture: E2E Business Scenario L1-L2
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the occurred function in E2E has all required attributes correctly maintained. Please note that this rule also validates all other languages defined by the administrator.
• Severity: Error
• Issue description: Attribute(s) missing: [name of attribute type and the respective value] -
[EO6] - Wrong assignment(s)
Context:
• Architecture: E2E Business Scenario L1-L2
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the occurred function in E2E has the correct assigned model type and assignment count
• Severity: Error
• Issue description: Too many models are assigned, the wrong model is assigned, or wrong models are assigned. Correct convention: Only one assignment of type [model type] is allowed. -
[EO7a] - Object definition is in the wrong group
Context:
• Architecture: E2E Business Scenario L1
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the definition of the occurred function in E2E Level 1 is stored in the correct group
• Severity: Warning
• Issue description: Move the object to the correct group under the End-to-End Business Scenario group. -
[EO7b] - Object definition is in the wrong group
Context:
• Architecture: E2E Business Scenario L2
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the definition of the occurred function in E2E Level 2 is stored in the correct group
• Severity: Warning
• Issue description: Move the object to the correct group under Process Landscape on Level 3. -
[EO8.a] - The mapped document does not yet occur in the library model
Context:
• Architecture: E2E Business Scenario L1-L2
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the document mapped to the occurred function in E2E has further occurrences in the required library model(s)
• Severity: Warning
• Issue description: You must also add this document to the Document Library model via occurrence copy. -
[EO8.b] - The mapped metric does not yet occur in the library model
Context:
• Architecture: E2E Business Scenario L1-L2
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the metric mapped to the occurred function in E2E has further occurrences in the required library model(s)
• Severity: Warning
• Issue description: You must also add this metric to the Metric Library model via occurrence copy. -
[EO9] - Wrong object or symbol reused
Context:
• Architecture: E2E Business Scenario L1-L2
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the occurred function in E2E has incorrect occurrence copies in other models
• Severity: Error
• Issue description: For Level 1: No occurrence copies are allowed for objects on this E2E level, or the wrong symbol is used for this E2E Level 1 model. For Level 2: In this E2E Business Scenario Level 2 model, only occurrence copies of Process objects from Process Landscape Level 3 are allowed. Objects from other levels are not allowed.
Library Models
-
[LM1] - Required model attribute is missing or not correct
Context:
• Architecture: Library Models
• ARIS type: ModelsRule:
• Validation: Checks whether the Library Model has all required attributes correctly maintained. Please note that this rule also validates all other languages defined by the administrator.
• Severity: Error
• Issue description: Attribute(s) missing: [name of attribute type and the respective value] -
[LM5] - Superior object is not correct
Context:
• Architecture: Library Models
• ARIS type: ModelsRule:
• Validation: Checks whether the Library Model has the correct superior object structure
• Severity: Error
• Issue description: This library model has too many superior objects -
[LM6] - Model is located in the wrong group
Context:
• Architecture: Library Models
• ARIS type: ModelsRule:
• Validation: Checks whether the Library Model is located in the correct group
• Severity: Error
• Issue description: The correct group should be: [Group path] -
[LO1] - Required object attribute is missing or not correct
Context:
• Architecture: Library Models
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the occurred object in the Library Model has all required attributes correctly maintained. Please note that this rule also validates all other languages defined by the administrator.
• Severity: Error
• Issue description: Attribute(s) missing: [name of attribute type and the respective value] -
[LO7] - Object definition is in the wrong group
Context:
• Architecture: Library Models
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the definition of the occurred object in the Library Model is stored in the correct group
• Severity: Warning
• Issue description: The correct group should be: [Group path]
BPMN Models
-
[BM5] - Model name and group name are not the same
Context:
• Architecture: BPMN L4 + L5
• ARIS type: ModelsRule:
• Validation: Checks whether the E-BPMN model name is equal to the group name
• Severity: Warning
• Issue description: Model name and group name must be identical -
[BM6] - Model name and superior function are not the same
Context:
• Architecture: BPMN L4 + L5
• ARIS type: ModelsRule:
• Validation: Checks whether the E-BPMN model name is equal to the superior object name
• Severity: Warning
• Issue description: Model name and superior function name must be identical -
[BM8] - Required model attribute is missing or not correct
Context:
• Architecture: BPMN L4 + L5
• ARIS type: ModelsRule:
• Validation: Checks whether the E-BPMN model has all required attributes correctly maintained
• Severity: Error
• Issue description: [Attribute is]/[Attributes are] missing: [List of missing attributes] or [Attribute Type NAME] has an incorrect value
Document Attachments
-
[GM1] - Document files have been linked incorrectly
Context:
• Architecture: all
• ARIS type: ModelsRule:
• Validation: Checks whether the model has documents linked via attributes to ADS or any other file location
• Severity: Error
• Issue description: Documents can only be attached to functions of each level via Satellite Modeling. -
[GO1] - Document files have been attached incorrectly
Context:
• Architecture: all
• ARIS type: Object OccurrenceRule:
• Validation: Checks whether the occurred function has documents linked via attributes to ADS or any other file location
• Severity: Error
• Issue description: Documents can only be attached to functions of each level via Satellite Modeling. -
[DO1] - Document file is not correctly mapped
Context:
• Architecture: all
• ARIS type: FunctionRule:
• Validation: Checks whether the mapped document object has the file link attributes correctly maintained
• Severity: Error
• Issue description: The document file must be mapped to [InfoCarrierObj.Name] either via the attribute [ARIS Document storage Link 1] for ADS or [Link 1] for other systems. In this case, the link is missing or both attributes are maintained, which is incorrect.
Need Help?
If you have questions about any Accelerator or want to exchange experiences with others, visit our community forum. There you can ask questions, share insights, and support each other.