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.

A metamodel is important for an architecture in general and essential for an architecture in a repository. Because the metamodel forms the framework for the architecture, it must be developed and maintained in a work process.

Drawing up architectures is usually done by several different stakeholders. In addition, work in architecture is not always project-based. This can cause the architectural model to become inconsistent. Reason to prevent these inconsistencies by monitoring the architectural model in a process.

Reviewing architecture is mainly about the content of the architecture and in this process it is mainly about handling the metamodel and applying the modeling conventions.

Parts of specific architectures such as project or domain architectures may have a generic character, making reuse desirable. This means that parts of these project architectures will propagate to a more generic architecture such as a reference architecture or architecture building block. Demotion from generic to specific is also possible.

Modelers must be trained, on the one hand in the use of the tooling and on the other hand in the metamodel and the conventions and conditions that apply within it.

Viewpoints are constraints in the architectural models based on the modeling languages. If you want to use simple architectural models, you should develop this as part of the metamodel.

Despite the fact that architectural modeling is a very creative process, this does not alter the fact that repetitive tasks such as model validation but also the use of templates can be automated. What and how this automation is introduced is a work process.

When introducing an architecture, the implementation must be guided on several levels. This includes the introduction of a metamodel, the modeling methods and the use, configuration and selection of the tools.

In addition to the use of a modeling language, additional requirements and definitions are drawn up around the Architecture models and products. They are frameworks for architects who develop different types of architectures.

A list of proposals, in the form of requirements and requirements for the architecture to be drawn up. But also for the metamodel or the modeling conventions of the architectures to be developed.

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.

Working in an architecture repository requires different skills than working with architecture documents. Architectural documents are often realized with office automation. Working in an architecture repository often requires specific tooling and a new working method. In addition, there must be awareness of the characteristics of a repository. Consider, for example, duplicates and the reuse of architectural (partial) models and concepts.

The metamodel of the Architecture models and the resulting architecture products must match the context of the organization. This will often be based on one or more modeling languages. Within these modeling languages, a subset will often be developed for the context of the organization. In addition, it must be worked out how a combination of modeling languages is realized. This forms the basis for the metamodel of the architecture repository.

When applying modeling languages and working in a repository, it is very important that there is agreement on the modeling languages and the modeling and naming conventions. This can be achieved by developing a community where this capability is jointly developed and maintained.

The architectural processes are often designed to produce, review and deploy architectural documents. By using an architecture repository, the architecture products will change and therefore the architecture process must also be designed differently.