Author: vpadmin

The ArchiMate example relate programs and projects to the parts of the architecture that they implement. This view allows modeling of the scope of programs, projects, project activities in terms of the plateaus that are realized or the individual architecture elements that are affected. In addition, the way the elements are affected may be indicated by annotating the relationships.

This ArchiMate example models and concepts that can be used for specifying the transition from an existing architecture to a desired architecture.

This ArchiMate example models the management of architecture change. The “architecture” of the migration process from an old situation (current state enterprise architecture) to a new desired situation (target state enterprise architecture) has significant consequences on the medium and long-term growth strategy and the subsequent decision making process. Some of the issues that should be taken into account by the models designed in this example are:

(1) Developing fully-fledged organization-wide enterprise architecture is a task that may require several years.
(2) All systems and services must remain operational regardless all the presumable modifications and changes of the enterprise architecture during the change process.
(3) The change process may have to deal with immature technology standards (e.g., messaging, security, data, etc.).
(4) The change has serious consequences for the personnel, the culture, the way of working, and the organization.

This ArchiMate example illustrates the gap between the Baseline and Target infrastructure, showing which of the elements of the infrastructure are added to or removed from the Baseline.

This example illustrates the use of the plateau concept to model the migration from Baseline to Target Architecture, defining a number of intermediate (possibly alternative) Transition Architectures.

In project management area, the deliverables (products) of a project are leading. The overall result of a project is described in a “project product description”; the hierarchical decomposition of this product in sub-products is shown in a Product Breakdown Structure, an ArchiMate diagram example of which is shown in the model here.

This ArchiMate diagram example illustrates a model of a work package that models a program to rationalize the application portfolio. This program consists of two projects that are executed sequentially, each of them also modeled as a work package. First, a project is carried out to integrate the backoffice systems (except for the CRM systems) into a single back-office system. Next, a project is carried out to integrate the CRM systems.

This ArchiMate diagram example models the motivation aspect, without focusing on certain elements within this aspect. For example, this viewpoint can be used to present a complete or partial overview of the motivation aspect by relating stakeholders, their primary goals, the principles that are applied, and the main requirements on services, processes, applications, and objects.

This ArchiMate diagram example models the realization of requirements by the core elements, such as business actors, business services, business processes, application services, application components, etc. Typically, the requirements result from the goal refinement viewpoint.

This ArchiMate example allows the analyst or designer to model the principles that are relevant to the design problem at hand, including the goals that motivate these principles. In addition, relationships between principles, and their goals, can be modeled. For example, principles may influence each other positively or negatively.