Insight · Notation

TOGAF or ArchiMate First? How to Sequence Your EA Learning

Q: If my organization uses a different EA methodology, do I still start with ArchiMate?

Yes, with modifications. If your organization uses a different framework or a custom methodology, the principle holds: learn the notation first, then the process. If your organization uses SysML rather than ArchiMate (common in defense and systems engineering), start with SysML fundamentals. The notation gives you production capability; the framework gives you structure.

By Sparx Services · June 18, 2025 · 7 min read

Learn ArchiMate first. TOGAF describes a process made of ADM phases, governance structures and deliverable types. Without a notation to work in, that process stays abstract. ArchiMate gives you the language to build the content, so TOGAF becomes something you can do as well as describe.

This order matters more when AI does part of the drawing. An architect's job is to decide what the architecture should say, and AI-augmented work lets the architect state that intent and have AI build the elements and views in the repository. The prompt is only as good as the person writing it. Someone who knows ArchiMate can ask for a precise Business Layer view and spot a wrong relationship in what comes back. Someone who knows only the TOGAF phases can name the deliverable but cannot direct or check the model.

Architects early in their careers ask this often. Certifications push TOGAF as the headline credential, while the practical skill that makes TOGAF usable is ArchiMate. Learn the notation first, and TOGAF's Phase B becomes a capability map you already know how to build in Sparx EA.

What TOGAF teaches

TOGAF, The Open Group Architecture Framework, is a methodology for developing, managing, and governing enterprise architecture. Its core is the Architecture Development Method (ADM): a phased process that takes an organization from architectural intent (Phase A, Architecture Vision) through business, information-systems, and technology architecture (Phases B, C, D) into implementation governance and change management (Phases E through H).

TOGAF also provides:

A content metamodel defining what architectural artifacts exist and how they relate
Governance concepts: architecture contracts, compliance reviews, architecture boards
A repository pattern (the Architecture Repository) for storing content
Techniques for stakeholder management, gap analysis, and migration planning

What TOGAF does not provide is a notation. Its content metamodel describes what to produce: business, application, and technology deliverables. It does not specify how those deliverables should look or what language they should use. That is the gap ArchiMate fills.

What ArchiMate teaches

ArchiMate is a notation standard from The Open Group: a visual language with defined element types, relationship types, and layer organization for expressing architecture content. It teaches you how to represent business capabilities, processes, roles, and services; application components, services, and data objects and their links to business concepts; technology infrastructure and its relationship to the application layer; and what "realizes," "serves," "triggers," "is composed of," and "is assigned to" mean in an architectural context.

The immediate consequence is that you can build things. Open Sparx EA, activate the ArchiMate MDG profile, and produce a view that accurately represents a real capability, application, or technology configuration: with typed elements, meaningful relationships, and layers that carry distinct concerns.

Then, when you read TOGAF's Phase B, you do not see abstract descriptions. You see deliverables you know how to build: a capability map (Strategy and Business layers), business process models (Business Layer), role and actor mapping (Business Actor, Business Role, Assignment). TOGAF becomes a project plan for work you can do.

Why learning TOGAF first produces the wrong outcome

An architect who has studied TOGAF without any notation has process knowledge without production capability. They know Phase B produces a Business Architecture document. They do not know what that document looks like, how to build it, or how to tell whether a given diagram is architecturally correct.

An architect who learned TOGAF without a notation tends to produce slides.

The deck describes the architecture at a high level but contains no structured, typed, relationship-verified content. When stakeholders ask "show me how the applications map to the capabilities" or "which business processes does this system change affect?", the answer means going back to source, because the slides are not a model. TOGAF gives the process its shape; ArchiMate fills that shape with content that can be queried, governed, and maintained.

The recommended sequence

Five steps, roughly six months, each building on the last.

Step 1: ArchiMate fundamentals (months 1-2)

Start with the three core layers: Business, Application, Technology. Learn the element types in each and the key relationships. The key ones are Realization, Serving, Assignment, Composition, Triggering and Flow. Practice in Sparx EA with the ArchiMate MDG profile. Goal: produce a three-layer view for a real or illustrative scenario and explain every element and relationship choice. This is the skill that lets you instruct AI precisely later.

Step 2: repository practice in Sparx EA (months 2-3)

Learn how Sparx EA manages an ArchiMate repository: package structure, MDG profile configuration, naming conventions, diagram organization. Understand what MDG governance does and why it matters for quality. Goal: contribute to a governed repository without breaking its structure, and tell typed elements from informal ones.

Step 3: TOGAF ADM phases (months 3-4)

Now TOGAF, with a specific focus. For each ADM phase, identify the ArchiMate deliverables it requires and how they are built in Sparx EA. Phase A's Architecture Vision maps to Motivation and Strategy elements; Phase B's Business Architecture to the Business Layer; Phases C and D to Application and Technology. TOGAF's governance concepts now map to things you have built, not abstract descriptions. Goal: map each ADM phase to its ArchiMate deliverables and the repository structures that hold them.

Step 4: advanced ArchiMate (months 4-5)

Return to ArchiMate with TOGAF context. The Motivation and Strategy layers, often skipped by beginners, now make sense as strategic content layers. Viewpoints become something you design deliberately. Advanced relationships such as Influence, Access and Flow are now understood through real questions: how does a regulatory requirement influence a capability? How does a data object flow across an integration architecture?

Step 5: MDG governance (months 5-6)

The final layer is governance discipline: how MDG Technology enforces ArchiMate semantics in Sparx EA, and how to keep repository quality high as the model grows and multiple architects contribute. This is where ArchiMate practice meets the full platform.

The organizational exception

Some organizations mandate TOGAF certification before an architect may work on deliverables, an HR and compliance reality in some large enterprises and consulting firms. If yours does, get it: sit the Foundation and Practitioner exams. Treat it as a credential and keep building the notation skill alongside it. Once certified, follow the sequence above. The organizational requirement adds a sequencing constraint and leaves the best learning order unchanged.

Frequently asked questions

Is there a formal ArchiMate certification like there is for TOGAF?

Yes. The Open Group offers ArchiMate 3 Foundation and Practitioner certifications. They are worth pursuing for a formal credential, but like TOGAF, certification is not a substitute for practical modeling ability. ArchiMate certification combined with real Sparx EA practice is a strong combination.

Can I learn TOGAF and ArchiMate simultaneously?

You can, but parallel learning tends to slow both. ArchiMate first is recommended because producing models reinforces the learning. If a deadline requires both, use TOGAF phases as contexts for ArchiMate exercises rather than studying them separately.

Does TOGAF require ArchiMate as its notation?

No. TOGAF is notation-agnostic. ArchiMate is the most widely used notation in TOGAF-aligned practices because it covers all four architecture domains and maps cleanly to the content metamodel, but Zachman, UML, and informal notations are also used. TOGAF plus ArchiMate plus Sparx EA is a structured and governable combination.

If my organization uses a different EA methodology, do I still start with ArchiMate?

Yes, with modifications. The principle holds: learn the notation first, then the process. If your organization uses SysML rather than ArchiMate (common in defense and systems engineering), start with SysML fundamentals. The notation gives you production capability; the framework gives you structure.

What this means for the architect

The sequence above is how an architect builds the skill that AI-augmented work depends on: knowing the notation well enough to state intent precisely and to review what AI produces. Teams that skip it get fast output they cannot verify. Tools such as Claude or GitHub Copilot with AI Power Tools can do the drawing in Sparx EA once the architect can say what should be drawn.

Learn the notation first, then let AI do the drawing.

We can teach your architects ArchiMate and TOGAF on your own repository and mentor them until it sticks, or build the plan and the first models for you and hand them over. Most teams want some of both.

Book a call

Keep reading