When introducing an architecture repository, the architecture products will often be published in documents. Documents are characterized by the lack of connections to other documents and the architectural elements described therein. As a result, a joint, reusable and shared architecture description is lacking. This is often a reason to introduce a repository architecture

The aim of architecture when introducing a repository-based architecture is to create an environment where the architecture model and the various architecture products are jointly worked on to address the imperfections of the document-driven architecture. This shared environment is called an architecture repository.

the limitations in a document-driven architecture method are chosen by the organization to introduce a repository-based method.

The modellers who jointly draw up the architectural model are trained in the use of the tool and are familiar with the established metamodel

The architecture repository works with a shared and established metamodel, including the modeling conventions. This prevents dialects and differences in the models within the repository.

the introduction of an architecture repository, the associated (modeling) tool will need to be configured and set up so that the modelers can effectively work together on the architecture model and the products.