FA-0641Mainframe & Enterprise Systems

ArchiMate 3.2 Enterprise Architecture Modelling

Concepts, viewpoints and a practical cross-layer model

Create and review a small enterprise architecture model using ArchiMate 3.2 concepts, stakeholder viewpoints and a compatible modelling tool.

Introduction

Why this course

This two-day course introduces practical enterprise architecture modelling using the source’s ArchiMate 3.2 basis. Participants model relationships across business processes, applications and technology infrastructure and communicate selected stakeholder concerns.

Exercises use a fictional enterprise scenario and a compatible Archi installation; other tools are compared rather than required. ArchiMate 4 is a newer published specification, so this course is explicitly 3.2-based and does not claim 4.0 coverage, accreditation or certification. It develops modelling practice rather than guaranteeing architectural or business outcomes.

Learning outcomes

The course teaches participants to:

Explain the purpose and scope of ArchiMate 3.2 and its relationship to enterprise architecture practices such as TOGAF.
Distinguish core layers/aspects and related motivation, strategy, physical and implementation/migration concepts.
Use appropriate elements and relationships in a small model.
Choose a viewpoint for a stakeholder’s concern.
Create linked business, application and technology views in a compatible tool.
Inspect model-exchange interoperability and its version/tool limitations.
Review consistency, scope and maintainability and explain a simple migration view.

Prerequisites

Basic knowledge of enterprise architecture concepts (e.g., layers, domains).
Familiarity with business process mapping or system modeling (UML or BPMN is a plus).
Comfortable working with diagramming tools (experience with Archi or Enterprise Architect beneficial but not mandatory).

A prepared tool/environment compatible with ArchiMate 3.2; any required specification materials must be available under appropriate use terms.

Training outline

2 modules

01Day 1 — Language Foundations and Viewpoints1 topics

Enterprise Architecture Context

Architecture-description context and evolution of the language to the 3.2 basis used here; distinguish newer specification releases.
A common modelling vocabulary and relationship to TOGAF practices; a language is not a complete architecture method.
Use an Archi release documented to support 3.2; compare Sparx Enterprise Architect or other tools at overview level and check exchange compatibility.

Layers and Aspects

Overview of Business, Application, Technology
Related motivation, strategy, physical and implementation/migration concepts; do not describe all framework areas as equivalent core layers.
Core active-structure, behaviour and passive-structure aspects, with motivation concepts considered separately.

Elements and Relationships

Behavioral, structural, motivational, composite elements
Key relationship types (structural, dynamic, dependency)
Notation, visual conventions and viewpoint choices; colour alone does not define semantics.

Stakeholder Viewpoints

Purpose and value of viewpoints; specificity per stakeholder
Common viewpoints: Business Process Cooperation, Application Structure, Technology Usage, Stakeholder, Strategy, Implementation & Migration
How to tailor the right viewpoint based on audience and concern

02Day 2 — Practical Modelling and Review1 topics

Tool Setup and Workflow

Inspect the prepared Archi installation and its 3.2 support; distinguish tool version from language version.
Import/export a small model using a compatible exchange format and inspect what is preserved.
Palette use, magic connectors, quick linking

Incremental Modelling Exercises

Business Layer: Model actors, processes, services, objects
Application Layer: Illustrate application components, services, data flows
Technology Layer: Map nodes, devices, system software, infrastructure
Motivation and strategy example: drivers, goals, outcomes and capabilities linked to an illustrative initiative.
Implementation and migration: plateaus, gaps, work packages and a simple roadmap.
Overview of layered, product and physical views; select only relevant views for the small exercise.

Integration Scenario

Build one fictional cross-layer enterprise model from business needs to application systems and technology infrastructure.
Highlight capabilities, services, and migration roadmap

Modelling Review

Aligning EA diagrams with stakeholder concerns; scoping per viewpoint
Balancing model detail vs. simplicity
Common element/relationship misuse and consistent representation of responsibilities.
Ensuring model reuse, consistency, and maintainability

A programme built around your team.

Share your training goals and requirements.