Overview of Application Migration Diagrams and UML/BPMN EAP Profile

UML/BPMN EAP profile

The application migration diagram identifies the migration of application components from the baseline to the target application. By precisely showing which applications and interfaces need to be mapped between migration phases, it enables a more accurate estimation of migration costs.

The goal is to define the trajectory between the current version of the IS and the desired version across several stages. Component deployment techniques allow you to represent the same components deployed across multiple IS versions and interconnect them in context‑specific ways.

System: Typically, all application components are directly or recursively embedded within a system, usually representing the enterprise IS.

Application: This component corresponds to legacy applications, off‑the‑shelf products, or can be an assembly of application components.

Entity Application Component: Entity components are usually derived from business entities and are responsible for managing access to and integrity of those entities.

Process Application Component: Process components are responsible for executing business processes and orchestrating their tasks.

Migration Link: Elements linking two versions of the IS during migration, typically used between business entities or application components.

Archimate

The migration strategy is divided into three steps.

In this diagram, we see the "Travel" application component being developed into three versions. The first version remains based on the TravelPortfolioManagement (legacy) application, while the second version works independently and can directly access the repository.

Each IS version is represented by a distinct "system element" in which the application component instances are deployed. This allows you to show the same component used across multiple versions, or an application component in version N migrating to one or more components in version N+1.