Hi, this is a call for a change in how ARIS handles ArchiMate models, and also BPMN models regarding persistency in the database.

Below you can find a citation from the documentation, related to how ARIS handles UML models.

This is a crucial feature for UML, however I would like to argue that it is as crucial for ArchiMate, but (somewhat less so) also for BPMN.

Why? For UML the argumentation can be applied without changes to ArchiMate. ArchiMate is inspired by UML, and architects creating ArchiMate models usually have the same approach: you design your objects, and the views are created for the stakeholder communications, not to create your architecture. ArchiMate elements are not defined by the views they are in, as in UML they are completely independent from those views.

For BPMN this is less so, because Pools are the containers of a process, but a Pool must still be reusable across views/diagrams. This goes for black-box pools as well as white-box pools. This is about reusability of Actors (Participants). Reusability of Lanes (related to Roles) is also valid, however only in the context of one containing top-level pool: we want to reuse a lane from a parent level in any child level. There are additional semantics such as a flow element cannot be in another lane in a child-level process than in a parent-level (unless that lane is a sub-lane).

From the documentation site:

"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. 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."