Practical Notes on Combining TOGAF and ArchiMate
I've spent years watching enterprise architecture teams try to use TOGAF and ArchiMate together, and more often than not it ends up being a lot of paperwork and very little clarity. The frameworks are sound in theory. The problem is usually execution, and the gap between the two standards is wider than most people expect when they start. TOGAF gives you the structure. It tells you where to start, what phases to work through, and which artifacts you should be producing. ArchiMate gives you the visual modeling language to actually draw the relationships between business processes, applications, and infrastructure components. The two were designed to work together. The Open Group explicitly aligns them. In practice, you use TOGAF's Architecture Development Method as your project management wrapper and ArchiMate as your primary modeling tool inside it. Here is how the ADM phases map to actual ArchiMate work. During Preliminary Phase you define your enterprise architecture capabilities and governance model, which means you write down who approves what. You don't model anything yet. This phase is mostly legal and organizational. Phase A, Architecture Vision, is where you produce the first set of ArchiMate diagrams. Stakeholder maps, a baseline Business layer showing current processes, and a target state picture with just enough detail to get budget approval. You do not model everything at this stage. Stakeholders will stare at a fifty-element application architecture diagram and immediately ask whether the firewall between production and staging is accounted for. Keep it high level.
Phase B through D are where people drown. Business Architecture, Information Systems Architectures for both data and application, and Technology Architecture. Each phase has its own ArchiMate viewpoints. Business uses process flows, organizational structures, and roles. Application and Data sit together because ArchiMate's Application Layer has direct association relationships to the Data Layer. Technology covers infrastructure nodes, devices, and network connections. The temptation is to model every single system and every single interface. Don't. Model the interfaces that matter to the change you are trying to drive. Everything else is noise. One thing most guides don't tell you about TOGAF and ArchiMate is that the ADM is not a linear process. It loops. Real projects loop back constantly. I had a situation a few years ago where we were mid-phase E, Migration Planning, and discovered the baseline application architecture we built during phase C was completely wrong about a middleware dependency. An older integration platform sat between two systems we had assumed talked directly. Fixing that required going back to phase B, redoing about forty percent of the Business Architecture work, and then updating every downstream diagram. The framework accommodates this. You just have to accept that plan for two weeks of rework becomes four weeks on day one. ArchiMate itself has a limitation that trips up a lot of people. The language was designed as a cross-domain notation. It is not a diagramming tool with drag and drop. If you are using something like Sparx EA or the free Archi tool, fine. But the real issue comes when you try to mix ArchiMate notation with regular BPMN or UML in the same diagram. It looks cleaner but it breaks the semantic integrity. People do it anyway because their audience prefers familiar notation. Just keep them separate. A TOGAF deliverable should have one standard view per artifact.
Another practical issue is model density. TOGAF expects you to maintain baseline, transition, and target architectures at every layer. That means three states for every element you model. If you model five hundred business processes and keep three versions of each, you now have fifteen hundred elements to manage, track, and update. It is sustainable only if you use archetypes and parameterized templates. Define what a Process archetype looks like, what an Application Component archetype looks like, and build from there. I built a simple archetype library in Archi that cut my modeling time roughly in half for repeat element types. Creating a new Business Function template took me about ten minutes and saved maybe six hours per project over its lifetime. The TOGAF Content Metamodel defines what artifacts exist, and ArchiMate implements those concepts through its own metamodel. The mapping is mostly one-to-one but there are gaps. TOGAF expects Deliverables, Building Blocks, and Requirements artifacts that don't have direct ArchiMate equivalents. You handle this by creating custom ArchiMate elements for requirements tracking and using the Notes or Documentation aspects in your modeling tool. Sparx EA handles this well. The free Archi tool requires a bit more manual setup with attributes and tables. For governance and compliance, ArchiMate's realization relationships are the most useful feature and the least used. A realization relationship explicitly connects a Business Actor to an Application Component to a Technology Node and shows who owns each layer. Most teams draw arrows between boxes and call it good. Adding the proper realization and assignment relationships makes audit and handoff infinitely easier. You can also run queries against a properly modeled ArchiMate diagram to extract traces from business capability down to technology component. That traceability is what makes the whole effort defensible when someone asks how a regulatory requirement maps to a deployed service.
Get the Full Details
When to not use this approach is worth mentioning. If your organization has fewer than fifty applications and two dozen business units, TOGAF is overkill. You don't need the full ADM cycle. A lightweight architecture review with basic ArchiMate diagrams for the critical paths is sufficient. Running a full TOGAF engagement for a small program typically takes six to nine months from kick off to completed target architecture, and I've seen it drag to fourteen months on the first attempt because the team was learning the framework as they went. ArchiMate adds about two weeks of initial setup cost for training and tool configuration. That investment pays off after the second or third project in a mature practice. If you want to start, get the TOGAF Standard, Eleventh Edition, from the Open Group website. Download Archi from archi-4e.github.io. The free tool includes built-in templates for both ArchiMate 3.2 and the TOGAF Content Metamodel. Start with a single Architecture Vision document and one Business Architecture diagram. Don't try to model the entire enterprise on day one. Build the habit, get feedback, and expand from there.
