A specification that has been formally reviewed and agreed upon, that thereafter serves as the basis for further development or change and that can be changed only through formal change control procedures or a type of procedure such as configuration management.

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.

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

Create a baseline for the package with the date as version number and duplication as description. A baseline is a copy of the package contents in XML format.

What is the baseline (document-oriented architecture) and the target (architecture repository).

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

Move duplicates to the Trash, then create a baseline, then delete the elements from the Trash. Due to the baseline, they are still present (in XML format) but no longer visible in the repository.

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.

The solution architect must offer the solution material to the model manager so that it can be determined what will be part of the baseline architecture. If this occurs after a number of requests to supply the material, it will be escalated to the team manager.

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.

With project architectures in particular, the inventory of the baseline, impact of the project, the requirements of the various stakeholders and the solution directions to be selected is an important work process.

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.

The modeler places the diagrams, packages and entities that he/she considers relevant for use as generic entities in the production package. This means that the entities can be used by other modelers in their own solutions and diagrams. This makes the elements part of the baseline 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.

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.

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.

Webvideo about baseline and target modeling

Webvideo over baselines in Sparx Enterprise Architect. Kan gebruikt worden als een eenvoudige werkwijze van release management

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.

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.

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.

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.