Architecture largely consists of drawing up models of the domain in question, often using a standardized (meta) model.

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.

Established architectures must be reviewed by a number of stakeholders for feasibility, content and elaboration of the architecture.

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.

Standardization of architectural models simplifies the creation, use and evaluation of these architectures. The use of templates makes this standardization possible. Introducing and maintaining templates is therefore a work process.

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.

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.

With project architectures in particular, the inventory of the baseline, impact of the project, the requirements of the various stakeholders and the solution directions to be selected is an important 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.

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.