Search for content

ArchiMate viewpoints

Here the viewpoints are described for solution architectures in particular, based on a different approach than the method with Viewpoints as described in the ArchiMate documentation. This is an elaboration of an organization that has determined a number of viewpoints for its own context. It is important that the viewpoints are related to each other. Within the viewpoints we work with:

Primary elements (green border), these are elements that in principle must be elaborated in these diagrams.

be used in these diagrams

It is important that we keep the number of concepts relatively limited and that the different viewpoints are related to the project package template for project or solution architectures.

Repository element

Demo Case Solution architecture {project}

Dit sjabloon is een package en diagram structuur voor een architectuurdocument, bijvoorbeeld een solution - of project start architectuur. Hierbij is in de diagrammen een koppeling gemaakt naar een viewpoint uitwerking zodat modelleurs ondersteuning krijgen bij het uitwerken van het model. Desgewenst kan dit package gekopieerd worden in EA om het projectspecifiek te maken. Vervolgens kan er een document van gegenereerd worden. Maak daarbij gebruik van de IDEA AddOn waarin je in de package helper een zoek en vervang actie kunt uitvoeren

Repository element

Modeller

Creates models in the architecture repository such as building blocks, solution architectures and base plates etc.

Repository element

Package structure

Example of a project structure based on the status of different submodels. What is characteristic of this is that the repository has a different layout for each phase. This approach indicates that the package structure does not have to be a limitation. When introducing an architecture repository, a discussion can arise about the package structure about what the correct format is. Keep the following suggestions as a starting point:

The package layout can change for each part of the architecture repository

The package structure can easily be changed if the working method is developed. changing insights

Determining the layout is often managed by the model manager or custodian for the generic architecture components

In work or project package structures, the modelers have more freedom in the design.

For solution architectures, use a template as a starting point.

Take into account the transfer of architectural concepts in a phasing and life cycle in the package layout.

The package structure should be aimed at the modelers who work with the architectural models. Users of these models must be supported in other ways, for example by navigation diagrams.

Repository element

Physical

A description of a real-world entity. Physical elements in an Enterprise Architecture may still be considerably abstracted from Solution Architecture, design, or implementation views.

Repository element

Provide 0.9 version to architecture board

Offering the 0.9 version of the solution architecture/PSA to the architecture board.

Repository element

Requirements overview

Overview in the form of a collection of the requirements of the various stakeholders within and outside the organization. Often elaborated on the basis of the motivation extension within ArchiMate. The summary can be done in the form of a list, a matrix or a number of graphical representations of the requirements. See also the elaboration of the solution architecture repository in a previous chapter for a number of examples.

Repository element

Solution Architecture

Solution architecture or project architecture describes a project that introduces a change in the enterprise. This architecture describes (a series of) the changes between the baseline and the target architecture.

Repository element

Solution Architecture

A description of a discrete and focused business operation or activity and how IS/IT supports that operation.

Repository element

Solution architecture example

This template is a package and diagram structure for an architecture document, for example a solution or project start architecture. A link has been made in the diagrams to a viewpoint elaboration so that modelers receive support with the viewpoint diagrams when developing the model. If desired, this package can be copied in EA to make it project specific. A document can then be generated from it. Use the IDEA AddOn in which you can perform a search and replace action in the package helper. This can easily be copied as a starting point for developing a new solution. The detailed example of such a template can be found as a resource in the existing example architecture repository.

Repository element

Solution Architecture Repository

Architecture model for an architecture repository approach. A number of generic architectural components have been developed in this model. On the one hand, this serves as an example for an architectural development. On the other hand, it can be expanded with organization-specific organizational components of the architecture. This makes it a starting point for an organization-wide architecture. This chapter has been elaborated on the basis of a number of architecture components that are relevant in a solution architecture. The same procedure was followed for the introduction of a method with an architecture repository. In fact, we apply an "eat your own dogfood" approach here.

Repository element

Solution architectures

These packages develop the solutions that currently implement the change of the organization from the baseline to the target architecture. Depending on the size of the organization, you will find several descriptions of solution architectures here.

Repository element

To enterprise architecture

If the project that delivers a solution is completed, the baseline architecture within the enterprise architecture will change, which is the final end result of a solution or project. Therefore, the concepts present in the models of the solution architecture will have to be elaborated in the baseline architecture after delivery. The models must be adapted accordingly to the new situation or the new baseline architecture. This must be carried out in a controlled process step in the architecture process in which the model manager or custion is often involved. This package is therefore a kind of conduit through which the solutions are placed, indicating that they can be integrated with the baseline architecture in the enterprise architecture packages.

Repository element

Towards Solution/Enterprise Architecture

As with the solution architectures, it is possible that sub-models developed in the personal packages become part of a solution architecture or the enterprise architecture. Here too, a folder to realize a controlled architectural process with which sub-architectures are transferred to the architectures with a different (determined) status under the responsibility of the model manager.

Repository element

Workareas and projects

Package in which modellers or teams can create their own elaborations of sub-models, or sub-elaborations of a solution. Within these packages, the modelers have a personal package in which they are free to choose their own layout and develop elements and diagrams. Please note: it is important that agreements are made about the reuse of elements that are present. It is often not allowed to reuse elements present in these personal packages, for example in solution architectures and not at all in enterprise architecture models.

Repository element

Business process with an architecture repository
Work process for a repository-based architecture. This includes a number of general steps, such as developing a metamodel for the architecture. It also contains a number of specific matters such as the design of the tooling. This diagram only includes the business process description. Please note that in the example repository a link has been made with other components in the solution architecture. This includes assigning the business roles for these business processes. These are then developed into a number of more detailed diagrams.
Repository diagram

ArchiMate viewpoints
Here the viewpoints are described for solution architectures in particular, based on a different approach than the method with Viewpoints as described in the ArchiMate documentation. This is an elaboration of an organization that has determined a number of viewpoints for its own context. It is important that the viewpoints are related to each other. Within the viewpoints we work with:

Primary elements (green border), these are elements that in principle must be elaborated in these diagrams.
< li>Secondary elements (orange border) are elements that may be used in these diagrams
It is important that we keep the number of concepts relatively limited and that the different viewpoints are related to the project package template for project or solution architectures.
Repository package
Demo Case Solution architecture {project}
Dit sjabloon is een package en diagram structuur voor een architectuurdocument, bijvoorbeeld een solution - of project start architectuur. Hierbij is in de diagrammen een koppeling gemaakt naar een viewpoint uitwerking zodat modelleurs ondersteuning krijgen bij het uitwerken van het model. Desgewenst kan dit package gekopieerd worden in EA om het projectspecifiek te maken. Vervolgens kan er een document van gegenereerd worden. Maak daarbij gebruik van de IDEA AddOn waarin je in de package helper een zoek en vervang actie kunt uitvoeren
Repository package
Package structure
Example of a project structure based on the status of different submodels. What is characteristic of this is that the repository has a different layout for each phase. This approach indicates that the package structure does not have to be a limitation. When introducing an architecture repository, a discussion can arise about the package structure about what the correct format is. Keep the following suggestions as a starting point:

The package layout can change for each part of the architecture repository

The package structure can easily be changed if the working method is developed. changing insights

Determining the layout is often managed by the model manager or custodian for the generic architecture components

In work or project package structures, the modelers have more freedom in the design.

For solution architectures, use a template as a starting point.

Take into account the transfer of architectural concepts in a phasing and life cycle in the package layout.

The package structure should be aimed at the modelers who work with the architectural models. Users of these models must be supported in other ways, for example by navigation diagrams.
Repository package
Requirements overview
Overview in the form of a collection of the requirements of the various stakeholders within and outside the organization. Often elaborated on the basis of the motivation extension within ArchiMate. The summary can be done in the form of a list, a matrix or a number of graphical representations of the requirements. See also the elaboration of the solution architecture repository in a previous chapter for a number of examples.
Repository package
Solution architecture example
This template is a package and diagram structure for an architecture document, for example a solution or project start architecture. A link has been made in the diagrams to a viewpoint elaboration so that modelers receive support with the viewpoint diagrams when developing the model. If desired, this package can be copied in EA to make it project specific. A document can then be generated from it. Use the IDEA AddOn in which you can perform a search and replace action in the package helper. This can easily be copied as a starting point for developing a new solution. The detailed example of such a template can be found as a resource in the existing example architecture repository.
Repository package
Solution Architecture Repository
Architecture model for an architecture repository approach. A number of generic architectural components have been developed in this model. On the one hand, this serves as an example for an architectural development. On the other hand, it can be expanded with organization-specific organizational components of the architecture. This makes it a starting point for an organization-wide architecture. This chapter has been elaborated on the basis of a number of architecture components that are relevant in a solution architecture. The same procedure was followed for the introduction of a method with an architecture repository. In fact, we apply an "eat your own dogfood" approach here.
Repository package
Solution architectures
These packages develop the solutions that currently implement the change of the organization from the baseline to the target architecture. Depending on the size of the organization, you will find several descriptions of solution architectures here.
Repository package
To enterprise architecture
If the project that delivers a solution is completed, the baseline architecture within the enterprise architecture will change, which is the final end result of a solution or project. Therefore, the concepts present in the models of the solution architecture will have to be elaborated in the baseline architecture after delivery. The models must be adapted accordingly to the new situation or the new baseline architecture. This must be carried out in a controlled process step in the architecture process in which the model manager or custion is often involved. This package is therefore a kind of conduit through which the solutions are placed, indicating that they can be integrated with the baseline architecture in the enterprise architecture packages.
Repository package
Towards Solution/Enterprise Architecture
As with the solution architectures, it is possible that sub-models developed in the personal packages become part of a solution architecture or the enterprise architecture. Here too, a folder to realize a controlled architectural process with which sub-architectures are transferred to the architectures with a different (determined) status under the responsibility of the model manager.
Repository package
Workareas and projects
Package in which modellers or teams can create their own elaborations of sub-models, or sub-elaborations of a solution. Within these packages, the modelers have a personal package in which they are free to choose their own layout and develop elements and diagrams. Please note: it is important that agreements are made about the reuse of elements that are present. It is often not allowed to reuse elements present in these personal packages, for example in solution architectures and not at all in enterprise architecture models.
Repository package

Links 2 Tags