User organization indicates which requirements, wishes and limitations exist regarding the artifacts to be developed within the architecture and the resulting implementations to the target architecture.

Depending on the project and domain classification of the organization, a project or solution architect will be responsible for the architectural development of one or more projects that achieve a conversion from the baseline to the target architecture.

Depending on the domain classification of the organization, a domain architect will be ultimately responsible for the architectural development of the relevant domain.

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.

An ambassador (preferably at management) level is needed for the architecture and the use of architecture repositories. For example, for safeguarding interests, making and keeping resources available and involvement in the planning of activities

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.

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.

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

Producer of artifacts, data and information that serve as input for preparing architect artifacts (in 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.