ArchiMate / TOGAF
The standard frameworks for modelling and governing enterprise architecture.
What it is
About ArchiMate / TOGAF
ArchiMate is the modelling language for enterprise architecture — a visual notation for drawing the relationships between business processes, applications, data, and technology infrastructure. TOGAF (The Open Group Architecture Framework) is the methodology that defines how to run the architecture function: how to assess current state, define target state, plan the transition, and govern implementation. Most organisations that take architecture seriously use both together — TOGAF to structure the work, ArchiMate to document it. Architects use tools like Archi (free, open source), Sparx Enterprise Architect, or BiZZdesign to create ArchiMate models. The value is in the language's precision: by distinguishing motivation, strategy, business, application, technology, and implementation layers, teams can trace a regulation change through to the technology systems it impacts without ambiguity.
What you can do with it
Capabilities
Draw an ArchiMate diagram showing how a business capability is supported by applications and infrastructure.
Create an architecture roadmap showing the transition from current-state to target-state across multiple programmes.
Conduct an Architecture Definition Document (ADD) following the TOGAF ADM (Architecture Development Method).
Perform gap analysis between an as-is architecture and a proposed target architecture.
Model compliance obligations (e.g. DORA, GDPR) and trace them to the systems and controls that address them.
How to learn it
Learning Resources
The Open Group free TOGAF 10 Foundation study guide at opengroup.org/togaf
Archi tool tutorials at archimatetool.com/learn — free and directly practice-oriented
ArchiMate 3.2 specification freely available at opengroup.org — read the motivation and strategy layers first
Udemy courses on TOGAF certification preparation — search for courses by Marc Lankhorst or Andrew Josey
Pro Tip
Start with the motivation layer (goals, drivers, assessments) before drawing application diagrams — without clear motivation, architectural decisions look arbitrary to stakeholders and governance boards.
Skills that use this tool
Roles that use this tool