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

Producer of artifacts, data and information that serve as input for preparing architect artifacts (in the architecture repository).

The Architecture Repository is a software tool that stores key architectural inputs and outputs, including Architectures themselves, their constituent elements, standards, references, principles and the Governance Register. Regardless of the Architecture Framework or Architecture Language selected. An enterprise architecture repository is therefore a collection of artifacts that describes the current and intended enterprise landscape of an organization. The purpose of the enterprise architecture repository is to represent the organization's inventory of technology, data, applications, and business artifacts and to show the relationships among these components. This is achieved by creating diagrams and visualizations based on the contents of the architecture repository.

Usage: noun based on the organization naming the organization of tables in databases, XML files, etc.

An architectural work product that describes an aspect of the architecture.

If architectures are implemented in custom solutions, the developers of these custom solutions will, on the one hand, provide frameworks and guidelines for the architecture and, on the other hand, they will be consumers of the architecture artifacts and implement them in functioning solutions.

A categorization mechanism useful for classifying architecture and solution artifacts, both internal and external to the Architecture Repository, as they evolve from generic Foundation Architectures to Organization-Specific Architectures.

From an architectural perspective, management organization is important for providing frameworks and guidelines regarding the management of the various artifacts and described in the various architectures.

The metamodel and the chosen modeling languages are also joint in a shared environment. Therefore, there needs to be agreement on these artifacts within the modeling community. To this end, consultation forms must be set up to obtain and safeguard this agreement. In addition, the metamodel must be consultable by the entire community.

The architectural process and products are also joint in a joint environment. Therefore, there needs to be agreement on these artifacts within the modeling community. To this end, consultation forms must be set up to obtain and safeguard this agreement.

Changes in the organization are often introduced into the organization on a project-by-project basis. Projects determine the planning and execution of the architecture work and make use of the architecture artifacts. The projects set requirements for the support from architecture and the products to be delivered by the architecture.

In addition to drawing up architectures, there are also roles that review and approve the architecture artifacts. For example, by testing for quality, feasibility, but also on the application of the modeling conventions and the organizational metamodel.

More and more organizations are opting for standard solutions for the design of the various architectures. In this case, the supplier of these solutions involved is a stakeholder from the perspective of supplying certain solutions and a customer of the architectural artifacts.

User organization indicates which requirements, wishes and limitations exist regarding the artifacts to be developed within the architecture and the resulting implementations to the target architecture.