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.

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.

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.

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.

Architectures are developed at various levels, where sub-models are selected and combined into an architecture. This can be a project, domain or reference architecture.

For the metamodel of the architecture, a number of modeling languages are often chosen in which a metamodel and modeling conventions have already been developed.

The metamodel describes the model of the architectures. This is often based on an architectural modeling language such as ArchiMate. These architectural modeling languages have also been developed in a metamodel

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.

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.