This secondary viewpoint describes which data and business objects are used within which processes and functions. This can easily be extended with, for example, the application where the data is used. However, this will usually not be within the scope of a data architect and should be cooperated with other architecture disciplines.

Different user types that have a relationship with business and data objects within the ArchiMate modeling domain

General understanding of a person or organization within or outside the modeling domain that influences the data, for example in the role of user, steward or owner.

Is an ArchiMate concept that is used to visualize the different links between the business objects at the business level. That is actually building a so-called business glossary. In addition, these entities can be used to visualize the links with other concepts within ArchiMate. For example, the links to business processes, functions and services are examples of this.

Data object is an ArchiMate concept that on the one hand can be linked to a number of ArchiMate concepts so that aspects such as quality, requirements. But also where is the dataset used and by whom, which application has a relation with this dataset etc. If necessary, you could link to the infrastructure from the data object. At this moment, this is not yet chosen in this example. As soon as there is a need in the community for this, this will be worked out further

Description of a logical application that has a relationship with a certain data object. Logical applications are independent of the implementation and are often modeled with verbs or with terms ending on system. For example collaborate or collaboration system.

Business process that uses a certain business object, roof can be both consult and mutation use