ArchiMate 3 Practitioner study plan

Classify each of the three ArchiMate core layers (Business, Application, Technology) and list the element types belonging to each from memory

Distinguish active structure, behavior, and passive structure elements and give one example of each per layer

Define specialization, composition, aggregation, and realization and state the structural constraint each imposes on endpoints

Draw a single-layer business diagram containing at least six distinct element types with correct notation

Differentiate the serving, access, assignment, and realization relationships and justify each choice in a worked example

Map the ArchiMate 3 motivation elements (stakeholder, driver, assessment, goal, outcome, principle, requirement, constraint) into a coherent motivation view

Explain the purpose of the implementation and migration, strategy, and physical layers and name their principal element types

Identify and correct at least five common notation errors in a diagram you construct deliberately incorrectly

Model a business process across business, application, and technology layers using correct cross-layer relationships

Apply the service-orientation principle by exposing behavior as services and connecting consumers via serving relationships

Compose at least three cross-layer relationship chains and verify each against allowed source-target combinations

Annotate every cross-layer arrow in a diagram with the relationship name and a one-sentence justification

Construct a capability map and connect capabilities to business services and to application components

Model a business process using business interaction, event, and business service elements without violating layer boundaries

Derive an application cooperation view from a business process view and document each mapping decision

Evaluate a peer-style diagram for relationship misuse and propose concrete corrections

Define derivation and transformation in ArchiMate terms and state when each is appropriate versus redrawing from scratch

Derive a technology usage view from an application usage view, preserving element identity and relationship semantics

Apply a set of transformation rules to convert a baseline model into a target model and record each rule applied

Distinguish baseline, transition, and target architecture states within a single plateaus-and-gaps model

Build a gap analysis identifying which elements are removed, added, or modified between baseline and target

Derive a realization view showing which work packages and deliverables realize which target elements

Test a derived model for orphaned elements and dangling relationships and repair each defect

Cross-check a derived view against its source view for consistency of names, types, and relationship direction

Select appropriate viewpoints for three distinct stakeholder groups and justify each choice by the concern it addresses

Produce a stakeholder-to-viewpoint-to-concern matrix for a single scenario

Adapt the level of abstraction and notation density of one model for an executive audience versus a technical audience

Write a narrative walkthrough of a model that a non-modeler can follow without the diagram in front of them

Assemble a complete multi-view architecture description from motivation through technology for one scenario

Verify every relationship in the assembled description against the language specification and log corrections

Produce a derivation trail from requirements through target elements to realization work packages

Present the full description as a timed stakeholder briefing with a defensible viewpoint rationale