What are the relevant application functions to support the stated work processes. These can then be linked to modules in the architecture tool or to requirements (during a selection process).

This is a process that consists of a number of sub-steps to organize the chosen tool in such a way that modelers can easily work in it and other stakeholders can easily find the material relevant to them.

There are several modeling languages and frameworks available for setting up an enterprise. Think of Archimate, Togaf, UML and BPMN. The search is often for a subset of these languages. To this end, a weighed choice must be made.

After choosing the modeling languages, it is possible to impose further restrictions on the modeling forms. Modeling languages are often so extensive that not all concepts are relevant to the organization. This can simplify use. That is why many organizations opt for further restrictions within the languages. This is done by introducing ViewPoints and Perspectives.

Despite the many navigation and search options available in an architecture repository, a logical layout is a good way to provide modelers and reviewers with structure. Packages are used for this in Sparx Enterprise Architect. The (tree) structure of the packages in a repository is therefore an important part of setting up an architecture repository.

Based on the relevant application functions, determine which parts of the tool need to be configured in order to effectively use the tool as an architecture repository.

The first step in designing a tool as an architecture is which tool or combination of tools are we going to use. In this example, Sparx Enterprise Architect is further developed and explained as a tool.

Ensure adequate training of those involved so that they have knowledge of the chosen modeling methods, the possibilities of the architecture repository and the functionalities in the chosen tool.