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.

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

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

Drawing up architectural models is on the one hand a creative activity, on the other hand it is a relatively error-prone process. This means that the tooling must optimally support the modeler when drawing up models.

Especially in large Architecture Repositories, a simple search based on various parameters and combinations is necessary. This also has added value in smaller repositories.

Drawing diagrams is a creative process very similar to drawing. Drawing up diagrams is not always intuitive, and various supporting functions are also required for drawing up models. Such as establishing relationships, adjusting layout or searching for connections, etc.

An architecture repository needs some form of classification. The form of classification used is different for every organization. To this end, there must be an option to choose a particular format for the repository AND be able to easily change it at a later stage if desired.

Architecture Repositories quickly become extensive (many elements, diagrams and connections). That is why there must be functionalities that make it possible to easily find relevant sub-models. This is relevant for all stakeholders.

Generic functionalities that are often relevant to all stakeholders for the architecture repository,

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.

An inventory document describes the aspects that are relevant when mapping a complex architecture, for example the baseline or target architecture. It is part of the analysis and modeling to establish an architecture.

A reference architecture is an abstract architecture in which a number of generic frameworks or building blocks are described. Organization-specific (domain and solution) architectures are drawn up based on reference architectures.

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.

A model is a schematic and simplified representation of part of the (architectural) system. It is often developed in modeling languages such as ArchiMate or BABoK.