In the secondary conceptual model it is modeled where, how and by which business or application entities these information entities are used or more precisely which entities have access to the information entities. For this, use is made of the behavioral tendencies in the application and the business layer of ArchiMate depending on the modeling level. Optionally, you can extend the model even further with active structure elements, however the question is whether this is the domain of the data modeller. For the link between the information entities and the behavioral entities, the access association (access) is used. Please note that this association can go two ways (or both).

Physical implementation or component within the ArchiMate domain that is used to describe applications that implement certain logical applications or application functions. For example the application process collaborate is implemented in the component SharePoint. Note that this can be a relatively complex elaboration in organizations with a fragmented application landscape.

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.

ArchiMate concept for describing (logical) actors) in a business layer that are involved in, for example, business processes and functions. Please keep in mind that roles can be performed by multiple persons an a person can perform multiple roles.

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