A person, organization, or system that has one or more roles that initiates or interacts with activities; for example, a sales representative who travels to visit customers. Actors may be internal or external to an organization.

Different roles in the organization that use the artifacts produced by the architects and taken from the architecture repository.

Team that will use the architecture tool in the architecture processes. They are therefore not only stakeholders but also play an important role in the processes.

It is possible, preferably, to activate and deactivate functionalities per authorization role. Use should be simple, especially for roles that occasionally use the architecture repository.

Description of the business architecture for a method with an architecture repository. A number of business processes and roles are being developed for this purpose. Because working with an architecture repository is a transition to a different working method within the architecture team, the business architecture is therefore an important part to work out in detail. The reason is that a successful enterprise architecture can determine the success or failure of the introduction of an architecture repository.

Description of the data management and governance organization, including the processes, roles and events known within it. Often based on an existing framework.

Those involved in data management, for example, the data owner, steward and other roles involved.

Which business roles are involved in the introduction of the architecture repository and its future use in the organization.

The working group should draw up catalogs for the various work areas, which will in fact create a taxonomy of xBB. Matters such as granularity and scope of an xBB play an important role

Role ultimately responsible for the overall architecture for the entire organization. So has both a global and an abstract scope on the architecture and the use of the architecture repository.

Description of the architecture of the IT management organization, including the processes, roles and events known within it. Often based on an existing framework.

When using an architecture repository, it is important to determine what and how the architecture is modeled. To this end, a metamodel is drawn up by this role. This includes the modeling conventions, cross-language conventions and design of the repository.

Responsible for the use and deployment of the models in the architecture repository. Has a coordinating and controlling task for all modeling roles involved in the architecture. Monitors the consistency of the architecture repository and provides modellers with information and training on the use of the architecture repository.

The content actually becomes the collective architectural product of the community. That is why quality requirements are imposed on this joint model. To this end, this responsibility must be known to everyone and there must be a role that monitors this responsibility.

The modeling community is responsible for making a number of working agreements, such as: ul> The modeling community does this by:

• Ensuring the design and conventions for the repository
• Developing architectural and modeling conventions
• Provides training regarding the repository design and the modeling method
• Review developments
• Stimulate communication and interaction within the community

Inside the modeling community should jointly introduce the above-mentioned working agreements. Depending on the structure and culture of the organization, different scenarios can be chosen to achieve this Intervision session The modeling community jointly determines what the conventions surrounding modeling are. Within intervision sessions, all participants can submit topics, examples and modeling problems that are discussed and based on discussion, a joint decision is made about the method to be followed and, if desired, the adapted modeling conventions Characteristic of the intervision session are

• On a regular basis a session organized for all modellers
• In these sessions the various participants bring in questions, solutions and suggestions
• Works well in small teams

Model manager Another scenario is that a model manager role plays a pioneering role in introducing a modeling community. The model manager is more active and the modeling community is more passive. Characteristics of the model manager are:

• Model manager determines bottlenecks and chooses a solution approach
• Sometimes a model core team is deployed for support
• Model manager coö ordinates describing the decisions in the repository or help pages
• Works well with large teams

Depending on the structure of the organization, (partial) models are developed by different teams with different roles in addition to the architects. For example, information analyst, data modeler, software development teams, etc.

Office automation is an application service that supports almost every role in an organization in their daily work. Namely offering functionalities such as word processing, creating presentations and the like.

Description of the structure of the organization based on business roles and/or actors. Often based on an existing enterprise architecture framework.

All data and information has an owner. - Rationale Structured and explicit ownership is necessary to be able to make decisions about the use and management of data and information and to set priorities. - Implication XXX-wide frameworks (policies, guidelines and standards) are necessary to deal adequately with data and information. A division of the XXX data and information landscape with recognizable boundaries is necessary to clearly organize ownership and responsibilities for data and information. Be clear about the roles (owner, user, editor) and associated tasks and authorities. Taking ownership and accepting someone else.

Participant in the specific data process. Later elaborated into activities and skills.

Visual representation of a RASCI matrix for relating data management roles to data domains and entities.

Recipient of data to a business role of data and information from this data process.

In addition to drawing up architectures, there are also roles that review and approve the architecture artifacts. For example, by testing for quality, feasibility, but also on the application of the modeling conventions and the organizational metamodel.

1. The usual or expected function of an actor, or the part somebody or something plays in a particular action or event. An actor may have a number of roles.
2. The part an individual plays in an organization and the contribution they make through the application of their skills, knowledge, experience, and abilities.

When working in an architecture repository you see that certain roles are necessary to introduce collaborative working. However, in the context of the organization, this role must be sufficiently embedded in the team.

Role within the organization responsible for supporting knowledge workers in the areas of communication and task management.

SIPOC is a simple modeling method for modeling business processes, objects and roles. A number of examples have been given. Copy one of the diagrams and adapt it to the new SIPOCs for a company-specific elaboration.

Supplier of data from a business role of data and information to this data process.

Same properties apply as the Table_A Naming Conventions. the referring key is special because in addition to the table name, a role name has also been added. For example, if there are duplicate associations or references to the table itself.

This summary is a presentation of the EA User group conference in Brussels with an overview of how an ArchiMate based repository can be introduced. This gives for example a description of the role of a repository custoduian

Work process for a repository-based architecture. This includes a number of general steps, such as developing a metamodel for the architecture. It also contains a number of specific matters such as the design of the tooling. This diagram only includes the business process description. Please note that in the example repository a link has been made with other components in the solution architecture. This includes assigning the business roles for these business processes. These are then developed into a number of more detailed diagrams.

Description of the roles within an architecture repository approach. This is therefore more detailed than the overview of stakeholders. In this model, the project members or roles will also be selected. A number of generically named roles. Roles do actively participate in the activities for the introduction of the AR. Please note that this is often organization specific in nature. Therefore, feel free to adapt this model to your own context. In this diagram, the roles are related to a number of stakeholders in the model.

Sub model for the data governance model containing the roles that stakeholders fulfill around a data domain or a data entity within a conceptual data model.

In the detail of the business process for architectural modeling, a number of connections are made clear. Which business objects are relevant to this process (in both reading and writing), which roles are involved in this detailed process.

The meta modeler plays a role in drawing up a metamodel for architecture, selecting modeling languages and drawing up organization-specific modeling conventions. This role is very important in carrying out a number of activities in the architectural work process. In addition, the meta modeler realizes a number of capabilities that are necessary for modeling in an architecture repository.

When introducing an architectural process based on an architecture repository, working with a modeling community becomes necessary. This community must ensure that a number of preconditions are introduced to ensure that the working method with an architecture repository realizes the goals and needs of the architecture team. When working with a repository, the metamodel and a collective view around the modeling techniques applied within the team are particularly necessary. In this view you can see that the modeling community is considered a collaboration of a number of architectural roles within the organization.

The model manager plays a central role in the operation of an architecture repository. This role is very important in carrying out a number of activities in the architectural work process. In addition, the model manager realizes a number of capabilities that are necessary when introducing and working with a work process based on an architecture repository.

Description of the business architecture for a method with an architecture repository. A number of business processes and roles are being developed for this purpose. Because working with an architecture repository is a transition to a different working method within the architecture team, the business architecture is therefore an important part to work out in detail. The reason is that a successful enterprise architecture can determine the success or failure of the introduction of an architecture repository.

SIPOC is a simple modeling method for modeling business processes, objects and roles. A number of examples have been given. Copy one of the diagrams and adapt it to the new SIPOCs for a company-specific elaboration.