A succinct description of the Target Architecture that describes its business value and the changes to the enterprise that will result from its successful deployment. It serves as an aspirational vision and a boundary for detailed architecture development.

The baseline is an architecture that describes the current architecture of the system. It is often drawn up together with the target architecture, which is the desired architecture. In this way it is possible to gain insight into the differences between the desired and current architecture.

The descriptive architecture as the name suggests describes the architecture. This is based on the target architecture and the baseline architecture. Within this package you often see an elaboration of the various dimensions of the organization based on subpackages to structure the descriptive architecture according to domain, layers and other organization-specific divisions. In this book a division based on a layer division for the organization

This is the established architecture of organization. It often includes the elaboration of the baseline architecture and sometimes also of the target architecture. It is important that the classification should be based on a consultation function. Architects use this as a register of the architecture for requirements inventories, but also for consulting the architectural landscapes and the frameworks within the architecture.

A statement of difference between two states. Used in the context of gap analysis, where the difference between the Baseline and Target Architecture is identified.

An inventory document describes the aspects that are relevant when mapping a complex architecture, for example the baseline or target architecture. It is part of the analysis and modeling to establish an architecture.

In many architectures, building blocks are an important part of the introduction of standardization and reuse. Here too, a design in the enterprise architecture in the form of a number of collections of building blocks that an architect can use when developing solutions to ensure that a solution contributes to the path to the target architecture. This package will also have a classification in the form of subpackages and/or the use of diagrams for the building blocks present within the organization. Navigation and overview diagrams will often be used for this. See also the section on applying building blocks within an architecture.

Naming Conventions Usage: Noun For example: Baseline, Transition, Target Architecture

The framework-setting architecture is of great importance for steering the change in an organization to transform from the baseline architecture to the target architecture. Setting frameworks is often developed on the basis of architectural principles or nowadays also called binding architecture agreements. You can also find the description of the viewpoints because they can also be considered as setting the framework.

A specialization of an inventory within the architecture is drawing up the requirements for the target architecture for the various stakeholders within and outside the organization within which the architecture is drawn up.

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.

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.

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.

The Solutions Landscape presents an architectural representation of the Projects and SBBs that support the Architectural Landscape and that are planned or implemented by the enterprise. They therefore form the connection between the Baseline and Target architecture.

The target is an architecture that describes the desired and future architecture of the system. It is often drawn up together with the baseline architecture, which is the desired architecture. In this way it is possible to gain insight into the differences between the desired and current architecture.

The description of a future state of the architecture being developed for an organization.

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.

Model from the baseline architecture (document driven) to the target (repository based) with a list of the required deliverables. This is based on a number of ArchiMate concepts in the implementation and migration modeling layer.

Around an architecture repository, an organization can define a number of capabilities and goals to determine a starting point for introducing this change in the architecture capability within the organization. This defines a point on the horizon for the target architecture.

Create a model for the baseline and target architecture for introducing a standardized application landscape Define one plateau in the middle Give these architecture relevant names Describe how to get from the baseline to the target Create an ArchiMate diagram of this implementation layer

Create a model for the baseline and target architecture for introducing a standardized application landscape Define one plateau in the middle Give these architecture relevant names Describe how to get from the baseline to the target Create an ArchiMate diagram of this implementation layer

The descriptive architecture as the name suggests describes the architecture. This is based on the target architecture and the baseline architecture. Within this package you often see an elaboration of the various dimensions of the organization based on subpackages to structure the descriptive architecture according to domain, layers and other organization-specific divisions. In this book a division based on a layer division for the organization

This is the established architecture of organization. It often includes the elaboration of the baseline architecture and sometimes also of the target architecture. It is important that the classification should be based on a consultation function. Architects use this as a register of the architecture for requirements inventories, but also for consulting the architectural landscapes and the frameworks within the architecture.

In many architectures, building blocks are an important part of the introduction of standardization and reuse. Here too, a design in the enterprise architecture in the form of a number of collections of building blocks that an architect can use when developing solutions to ensure that a solution contributes to the path to the target architecture. This package will also have a classification in the form of subpackages and/or the use of diagrams for the building blocks present within the organization. Navigation and overview diagrams will often be used for this. See also the section on applying building blocks within an architecture.

The framework-setting architecture is of great importance for steering the change in an organization to transform from the baseline architecture to the target architecture. Setting frameworks is often developed on the basis of architectural principles or nowadays also called binding architecture agreements. You can also find the description of the viewpoints because they can also be considered as setting the framework.

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.