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.

Details van Solution architect

Depending on the domain classification of the organization, a domain architect will be ultimately responsible for the architectural development of the relevant domain.

Details van Domain architect

Role ultimately responsible for the overall architecture for the entire organization. So has both a global and an abstract scope on the architecture and the use of the architecture repository.

Details van Enterprise architect

When using an architecture repository, it is important to determine what and how the architecture is modeled. To this end, a metamodel is drawn up by this role. This includes the modeling conventions, cross-language conventions and design of the repository.

Details van Meta modeler

Responsible for the use and deployment of the models in the architecture repository. Has a coordinating and controlling task for all modeling roles involved in the architecture. Monitors the consistency of the architecture repository and provides modellers with information and training on the use of the architecture repository.

Details van Model manager

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.

Details van Reviewer

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

Details van Modeling architecture

The modeling community is responsible for making a number of working agreements, such as: ul> The modeling community does this by:

• Ensuring the design and conventions for the repository
• Developing architectural and modeling conventions
• Provides training regarding the repository design and the modeling method
• Review developments
• Stimulate communication and interaction within the community

Inside the modeling community should jointly introduce the above-mentioned working agreements. Depending on the structure and culture of the organization, different scenarios can be chosen to achieve this Intervision session The modeling community jointly determines what the conventions surrounding modeling are. Within intervision sessions, all participants can submit topics, examples and modeling problems that are discussed and based on discussion, a joint decision is made about the method to be followed and, if desired, the adapted modeling conventions Characteristic of the intervision session are

• On a regular basis a session organized for all modellers
• In these sessions the various participants bring in questions, solutions and suggestions
• Works well in small teams

Model manager Another scenario is that a model manager role plays a pioneering role in introducing a modeling community. The model manager is more active and the modeling community is more passive. Characteristics of the model manager are:

• Model manager determines bottlenecks and chooses a solution approach
• Sometimes a model core team is deployed for support
• Model manager coö ordinates describing the decisions in the repository or help pages
• Works well with large teams

Details van Modeling community