
Set up the Archi environment using the open source ArchiMate tool, and configure the default view, labels, and view properties for the ArchiSurance case study.
Create a fragment of a stakeholder view in ArchiMate for ArchiSurance, organizing stakeholders and drivers in folders, linking them by association or influencer, and illustrating driver hierarchy.
explore ArchiMate motivation modeling by linking stakeholders' concerns to drivers, goals, and assessments, using influence relationships and aggregate versus composition to map profitability and cost reduction to outcomes.
Build a principles view by linking two business goals to two principles, map data elements to their realizations, and export the diagram as an image, aligning with ArchiMate 3.2 practices.
Introduce the ArchiMate open exchange file format for exporting and importing models. Demonstrate downloading, importing, and viewing a complete model in xml, and outline version 3.1 updates and value stream.
Examine version 3.1 of the ArchiSurance case study to model stakeholders, drivers, outcomes, and layered goals, linking assessments to profitability, costs, and customer experience.
Explore the goal refinement view in ArchiMate modeling, linking strategic goals to principles and requirements, and practicing reflection on costs, aggregation, and cross-layer requirements.
Learn how to build a phase A meta model for ArchiMate, focusing on a motivation layer with stakeholders, drivers, assessments, goals, and outcomes and their relationships.
Build the strategy view for a digital customer intimacy initiative by linking motivation, stakeholders, drivers, goals, and outcomes with cross-layer mapping to capabilities and realization.
Learn how Archi junctions combine two relationships to realize a common action, compare junction use with direct links for clarity, and follow RC user guide for visualization best practices.
Describe the target architecture with the motivation and strategy layers in the solution concept view, detailing CRM automation, back office automation, and data flows from front to back end.
Finalize the phase a meta model patterns and separate them from the working model, then build cross‑layer patterns—goal, influence, driver, capability, course of action, and resource—for reuse in phase b.
Explore creating the organization view and organization decomposition (nested), detailing actors, locations, aggregations, and compositions across the merged company structure.
Draw and explain figure 11 value stream within the ArchiMate practice, linking organization and location patterns to a two-layer value stream with stages, an outcome, triggers, and a stakeholder.
Build a capability map as the central element of business architecture, linking capabilities to value streams, processes, information, and applications, using CSV export/import to populate the baseline ArchiSurance model.
Explore value stream capability cross-mapping in ArchiMate, linking upper-level capabilities to value stages via cross-layer relationships, aided by structured folders and naming for easy searching.
Explore the Archimate business function view and how functions map to value streams via business capabilities, using actor-to-function assignments for validation and HTML report export and CSV import.
Explore ArchiMate capability realization by linking business functions to capabilities, using patterns and a metamodel to document relationships, and refining views from business to strategy layers.
Advance phase b by modeling the business process with triggers, events, and composition patterns. Clone the latest model and pattern from the GitHub repository for reference.
Learn to build a baseline business process view in ArchiMate for ArchiSurance by creating business events and processes, organizing level folders, using composition relations, and junctions for decisions.
Learn how value streams are realized by business processes through cross-layer mapping in ArchiMate, using realization relationships, business capabilities, and search strategies to model policies and claims.
Explore the requirements realization view in ArchiMate, linking motivation, strategy, business, application, and technology layers through realization and serving relationships, with practical guidance on artifacts and implementation.
Perform a capability gap analysis in ArchiMate using figure 19. Color-code baseline and target states, build a three-layer capability tree, and automate layout with a heat-map script.
Create the figure 20 resource map view by mapping business capabilities to resources across strategy layers, including digital customer intimacy, while refining repository elements, data sources, and collaborative naming practices.
Explore figure 21, the resource realization view, mapping strategy layer resources to applications, business resources, and technology, with cross-layer linkage and html report navigation in ArchiMate.
Review phase b modeling meta-model patterns in ArchiMate using ArchiSurance; analyze organization view, value stream, capabilities, and realization to build consistent patterns across figures and repository exports.
Define the application cooperation baseline in phase c by mapping information flow between applications. Reuse catalog elements to connect data architecture and visualize relationships across front office and back office.
Figure 23 presents the target application cooperation, consolidating three legacy back-office systems into a single back-office suite while simplifying the front-office CRM, using reuse and component patterns.
Define the application usage view to map how applications support business processes through an application service layer, aligning business and application layers.
Demonstrates the application behavior view, showing cross-layer flows from technology function and artifacts through application and business processes to automate underwriting and insurance premium calculations.
This lecture guides the gap analysis of the information system application architecture, comparing baseline and target views to identify decommissioned legacy and new back office data warehousing components.
Apply the Phase C1 modeling meta-model to map application components, flows, and composition, keeping cross-layer use cases clear and capturing gap analyses for ArchiMate patterns.
Explore the information structure view of data architecture, mapping conceptual business objects to logical data objects within Archimate, using customer data and insurance policies as examples.
Analyze the data dissemination diagram in ArchiMate, showing how data objects in the data layer realize business objects through application components and access relationships.
Document the data architecture modeling pattern in phase C2 by mapping two diagrams to an ArchiMate metamodel, showing business objects, application layer, data objects, and realizations, with access controls.
Develop the phase d technology view baseline in ArchiMate by modeling infrastructure, offices, locations, servers, and networks. Link data acquisition and technology services through gap analysis and target views.
This figure 30 presents the target technology view and delta changes from the baseline, detailing removal of headquarter elements, server reconfiguration, and a new data acquisition gateway with backups.
Model data acquisition gateway linking IoT devices and equipment across smart home and external facility, using ArchiMate relationships to show data flow to energy and distribution networks.
Model the IoT device services target by detailing the data flow from device to gateway, including device registration, operations, and notification services exposed via a RESTful API.
Explore technology architecture gap analysis by comparing baseline and target models, applying color-coded heat maps, and managing decommissioned components in ArchiMate with ArchiSurance.
Review phase d presents a technology layer pattern, reuses phase c patterns, and consolidates artifacts, devices, and locations while introducing a data acquisition gateway and node interfaces.
Explore the migration view in ArchiMate modeling to depict migration and transformation management, using baseline states, junctions for A or B decisions, and mapping cross-layer assets to the project context.
Create a TOGAF project context diagram in ArchiMate, organizing work packages, server components, data warehousing, and CRM integrations to visualize project impact and architecture context.
Review the modeling meta-model pattern in phase e and f using ArchiMate language, illustrating a two-view architecture with work packages, nodes, data layers, and application components, plus collaboration tips.
Develop a complete archimate modeling pattern summary by consolidating phase-focused patterns, notations, and relationships into an end-to-end view across strategy, motivation, business, application, and technology layers.
Install Archi by downloading the latest stable version for Windows, macOS, or Linux from the user guide, then launch to explore its interface, plugins, and repositories.
Explore the Archi archimate tool's file structure, diagrams and views, including the archimate.archimate XML model, blank models, and unique IDs; learn how diagrams define relationships and impact the model.
Explore how to structure ArchiMate models in Archi, create capabilities like sales management under folders, add properties and documentation, and define diagram-based relations such as composition and aggregation in views.
Learn how to model ArchiMate 3.2 relationships as an ontology using Prodigy and RDF, visualize graphs, and run SPARQL queries to explore architecture elements.
Learn to efficiently load thousands of elements and their composition relationships into an Archi model via CSV export and import, demonstrated with a 1000-element, ten groups example.
Explains the CSV export file structure for ArchiMate elements, relations, and properties in Archi, detailing what is exported, what is not, and how to relate files during import.
Learn how to create and import CSV files for ArchiMate elements, relations, and properties in Archi, including preparing a test model, mapping IDs, and handling import errors.
Learn to export and import csv data in Archi, load diagram contents via csv, and build a working model with elements, relationships, compositions, and properties using a csv sample tool.
Explore Archi 5.2 ArchiMate modeling features, including multiple selection for user properties, per-figure line width, and the HTML report analysis tab with an enhanced appearance tab.
Explore Archi 5.5 early adopter features for ArchiMate modeling, including diagram line styles, delete container while keeping children, model tree view search, and nested connection hiding, plus Java runtime updates.
Discover Archi 5.7 features, including highlight primary selection for connections, select objects of the same type, model tree improvements, and new key bindings, plus CSV export/import guidance.
Explore Archi 5.8.0 features and their impact on ArchiMate modeling practices within ArchiSurance projects today.
Explore Archi 5.9.0 features and their impact on ArchiMate modeling practices with ArchiSurance. See how the new features support ArchiMate modeling workflows within ArchiSurance.
[Note]: this course was my first packaged course and recorded in 2023, to respond comments and questions from students, and also to improve certain audio quality, I've re-record this ArchiSurance in 2025, you may search "ArchiMate - ArchiSurance 3.2 - Modeling Practice (2025)" to get the refreshed contents. Enjoy.
ArchiMate is open and independent enterprise architecture modeling language, from The Open Group, to support the description, analysis and visualization of architecture within and across business domains in an unambiguous way.
Archi is an open source modeling toolkit for creating ArchiMate models and stetches. Developed by enterprise architects and used by enterprise architects.
The ArchiSurance Case Study is a fictitious example developed to illustrate the use of the ArchiMate® modeling language in the context of the TOGAF® framework. The Case Study concerns the insurance company ArchiSurance, which has been formed as the result of a merger of three previously independent companies. The Case Study describes the Baseline Architecture of the company and then a number of change scenarios
The case study is one good learning material for preparing ArchiMate certification examination.
During myself's learning journey and passing the ArchiMate certificate, I've found that not only read the case study, but also do the hands-on modeling was the most important experience for deeper understanding the ArchiMate theory and context.
This course was recorded the end to end modeling journey for ArchiSurance case study after I got the certificate, through re-reading the material and practicing the modeling again, more knowledge are captured, I do hope this experience can bring some reference to you if you're also either interested on EA modeling via ArchiMate (using Archi tool), or intend to pass ArchiMate certificate soon. Remember to have your Archi tool on-hand and do the modeling activity yourself during follow the course!
Good luck!