Relevance of the model and its diagrams in terms of semantics
There is a fundamental difference between the classic ARIS Method and UML that has major effects on how you use ARIS Architect/ARIS Designer and ARIS UML Designer.
In UML, the semantics of a model (not a diagram) are completely contained in its elements and their properties and relationships. Diagrams merely represent a graphical view of the model. If you were to delete all UML 2 diagrams in an ARIS database, the semantics of the UML model would be fully retained. In addition, many UML elements are not represented graphically in diagrams and appear there in text form at most within the graphical presentation of a superior element.
In ARIS Method, diagrams have a much greater significance. For some ARIS objects, the symbol by which they are represented graphically in a diagram actually determines their semantics. One example is the Rule object. It is the graphical representation in a diagram with a XOR, AND, XOR/AND, OR/XOR symbol etc. that specifies the exact meaning. As a consequence, the diagrams in ARIS Method make a significant contribution to the semantics of the model. Conversely, objects and relationships that are not represented graphically in a diagram are irrelevant in ARIS Method.
During database reorganization all ARIS objects and ARIS relationships with no occurrence in a diagram are therefore deleted. By contrast, UML 2 elements are retained after database reorganization, as merely the fact that a UML element is not represented in any diagram does not reveal whether or not it is still required.