The ArchiMate 3.2 specification was explicitly designed to complement the TOGAF® Architecture Development Method (ADM) by providing a vendor-independent set of concepts and graphical representations for its various architecture domains. While the TOGAF ADM describes the process for developing and managing the lifecycle of an enterprise architecture, ArchiMate provides the visual language to describe the content of those architectures. The mapping between the two standards ensures that models remain consistent and integrated throughout the entire transformation cycle.
Preliminary, Phase A (Architecture Vision), and Requirements Management
During the initial phases of the ADM, architects focus on defining the scope, goals, and high-level requirements of the architecture. Strategy and Motivation elements are primarily used here to capture the vision, architecture principles, and initial business requirements. These elements help stakeholders understand “why” a change is necessary and “what” high-level capabilities are needed to achieve the desired outcomes.
- Practical Example: In Phase A, an architect can use an AI prompt to generate a Strategy viewpoint for a “Retail Digital Transformation,” illustrating how the goal of “Increased Market Share” is realized by the capability of “Omnichannel Fulfillment”.
Phase B (Business Architecture)
Phase B focuses on describing the current and target states of the business domain. The ArchiMate Business Layer directly supports this phase by modeling business processes, actors, roles, and services. It allows architects to visualize how the organization creates value for its customers through its internal behavior and structure.
- Practical Example: In Phase B, an architect might model an “Order Fulfillment” Business Process assigned to a “Sales Representative” Business Role to define the operational baseline for a new e-commerce system.
Phase C (Information Systems Architectures)
This phase is divided into Data Architecture and Application Architecture. The ArchiMate Application Layer supports Phase C by describing the structure and interaction of application components, services, and data objects. This ensures that the software landscape is explicitly linked to the business needs defined in the previous phase.
- Practical Example: In Phase C, an architect can generate an Application Cooperation viewpoint showing how a “CRM System” and a “Billing Application” exchange “Customer Data” objects via a shared interface.
Phase D (Technology Architecture)
Phase D involves modeling the hardware and software infrastructure that supports the applications. The ArchiMate Technology Layer (and its physical extensions) is used to describe nodes, devices, system software, and networks. This layer provides the technical foundation required to realize the higher-level application and business services.
- Practical Example: In Phase D, a user might prompt the AI to create a Technology Usage viewpoint illustrating how a mobile banking app is hosted on “AWS Cloud Nodes” and uses a “PostgreSQL Database” for storage.
Phases E, F, and G (Implementation and Migration)
These phases deal with Opportunities and Solutions, Migration Planning, and Implementation Governance. ArchiMate’s Implementation and Migration Layer provides specialized elements such as Work Packages, Deliverables, Plateaus, and Gaps to model these transformation activities. These concepts allow project managers to visualize the transition from the Baseline Architecture to the Target Architecture through various Transition states.
- Practical Example: In Phase F, an architect can generate a Migration viewpoint depicting the “Plateaus” (milestones) and “Gaps” (missing features) involved in transitioning from a legacy on-premise server environment to a modern cloud-native architecture.
Phase H (Architecture Change Management)
Phase H focuses on ensuring the architecture continues to meet the needs of the business as they evolve. Motivation and Strategy elements are once again highly relevant here, as they allow architects to model changing Drivers and assess how new Requirements will impact the existing core layers.
- Practical Example: If a new regulation like GDPR is introduced, the architect can use a Requirements Realization viewpoint in Phase H to trace the impact of the new legal “Constraint” down to specific “Data Objects” and “Business Processes” that must be modified for compliance.
