Uncia
FR / EN Demo

Glossary

TOGAF

The TOGAF Standard is a standard of The Open Group, described as an enterprise architecture methodology and framework. It sets out how to run architecture work, from the initial vision to governing the implementation, and prescribes neither a tool nor a notation.

Updated

What is TOGAF?

TOGAF is a standard published by The Open Group, which also publishes ArchiMate. Its official page describes it as an enterprise architecture methodology and framework. A working TOGAF definition fits in one sentence: an organized way to decide what your systems should look like in a few years, and through which steps you get there.

TOGAF describes an approach. It says which questions to ask, in what order, which documents to produce and who signs them off. It ships no software and no symbols. You can apply TOGAF with a spreadsheet and a drawing tool, and you can own an enterprise architecture tool without following TOGAF at all.

The standard works at the scale of the whole organization. It frames a transformation that touches several business units and dozens of applications: merging two IT estates, leaving a data center, replacing an ERP. For the design of a single application, the reference document remains the architecture document. The three scales at which architects work are covered in the IT architecture entry.

What does the TOGAF Standard contain?

The current release is the 10th Edition. The Open Group's page names it as the current edition and lists Version 9.2 as an earlier one.

The standard is divided into two sets. The TOGAF Fundamental Content provides, in the catalog's words, the core concepts and practices. It has six parts: Introduction and Core Concepts, the Architecture Development Method (ADM), ADM Techniques, Applying the ADM, Architecture Content, and Enterprise Architecture Capability and Governance.

The TOGAF Series Guides advise on how to configure the Fundamental Content for a given subject. The catalog lists more than twenty of them. Some deal with the business side (business capabilities, value streams, business models). Others cover how the work is run (applying the ADM using agile sprints, architecture project management, roles and skills). A third group addresses technical subjects such as integrating risk and security, or microservices architecture.

This split has a practical consequence. Nobody reads TOGAF cover to cover and applies it as written. A team keeps the method, two or three techniques, and the guides that match its subjects.

What is the TOGAF ADM, and what are its phases?

The ADM is the best-known part of TOGAF, the circular diagram pinned to many architects' walls. The text of the 10th Edition sits behind a login on The Open Group's site. The phases given here come from the reference card The Open Group published for Version 9.2, the most recent one we could read freely.

A Preliminary Phase prepares the organization: team, architecture principles, tool selection, tailoring of the framework. Phase A, Architecture Vision, sets scope, constraints and stakeholders, and obtains approval to proceed. Phases B, C and D develop the architecture in four domains: business, application, data and technology. The card states that in each case you develop the Baseline and Target Architecture and analyze gaps.

Phase E, Opportunities and Solutions, does the initial implementation planning and identifies Transition Architectures where an incremental approach is needed. Phase F, Migration Planning, details how to move from the Baseline to the Target Architecture. Phase G, Implementation Governance, checks that projects build what was decided. Phase H, Architecture Change Management, tracks change once the target is in place. Requirements Management sits at the center of the circle and runs through every phase.

The same card lists tailoring the framework among the steps of the Preliminary Phase. Sizing TOGAF to your organization is therefore part of the method.

What is the difference between TOGAF and ArchiMate?

Both standards come from The Open Group, and they do different jobs. TOGAF is the approach: steps, deliverables, governance. ArchiMate is the language: The Open Group describes it as an open and independent modeling language for enterprise architecture, with its element types, relationships and symbols.

A team can follow the ADM and draw its architectures with home-made boxes and arrows. It can also model its entire estate in ArchiMate without ever running a TOGAF phase. The two fit together well: the ADM asks you to describe business, applications, data and technology, and the language gives you layers to draw them in.

Much of the confusion comes from tooling. Enterprise architecture software usually offers ArchiMate notation along with templates inspired by TOGAF, which makes them look like one package. They are three separate things: a method, a notation and a piece of software. Each is chosen on its own, based on what the team actually has to decide and to show.

How does TOGAF relate to national traditions such as French IT urbanization?

Enterprise architecture did not develop the same way everywhere. In France it took the form of urbanisation du SI, a city-planning approach to IT described in the IT urbanization entry. It reasons in views (business, functional, application, technical), divides the estate into zones, districts and blocks, and sets rules that every project follows. TOGAF pursues the same goal with a different vocabulary and a more detailed process.

The two share the essentials: describe what exists, describe a target, organize the path between them. The most visible difference is the functional view, which the French tradition puts forward and which describes what the systems must do regardless of the applications doing it. TOGAF puts more weight on the work cycle and on governance.

If you work with a French subsidiary or supplier, expect both vocabularies in the same meeting. The zoning plan provides the breakdown and the rules, and the ADM provides the order of work.

What do practitioners criticize about TOGAF?

These criticisms concern how the standard gets used. They say nothing about its text.

Weight comes up most often. Applied to the letter by a team of two, TOGAF produces deliverables nobody reads. The standard expects to be tailored, but tailoring takes experience that a new team does not yet have. Pace is another: a full architecture cycle feels long to teams that ship every two weeks, and The Open Group does publish a Series Guide on applying the ADM using agile sprints. Certification is one more, which some practitioners find more common on resumes than in day-to-day practice.

The last criticism concerns the existing estate. The ADM asks for a description of the Baseline Architecture before the target is decided, and that description too often rests on interviews and old diagrams. Three application servers get written down because the 2021 design document showed three. Production runs five, one of them on an operating system that is out of support. The gap analysis then inherits every error in its starting point.

A baseline needs facts: a dated inventory, verified dependencies, recorded flows. That is the job of mapping the IT estate, and it is best done before Phase B.

What Uncia brings, and what it does not do

Uncia works on the existing estate, the side TOGAF calls the Baseline Architecture. It reads your sources read-only (connectors to clouds, hypervisors, CMDB, firewalls and scanners; dropped-in files such as an RVTools export, a flow matrix or an architecture document) and reconciles them into a knowledge base. From that it generates Architecture, Infrastructure and Network maps, from business domain to firewall rule, where every element has its record and its sources. The maps go back to your tools through ArchiMate or draw.io export.

Uncia is not a TOGAF tool. It does not run the ADM, produces none of the standard's deliverables, and is not where you draw the target or the roadmap. That work stays in your architecture tools and review boards, which Uncia complements and does not replace. The link between an application and its business domain appears only if one of your sources carries it. The knowledge updates with each collection.

Sources

Frequently asked questions

Is TOGAF a method, a tool or a notation?

A method and a framework. The Open Group describes the TOGAF Standard as an enterprise architecture methodology and framework. It is neither software nor a modeling language: the notation most often used with it, ArchiMate, is a separate standard from the same organization.

What is the current version of TOGAF?

The 10th Edition, according to The Open Group's page as read on November 17, 2026. It is divided into the TOGAF Fundamental Content and the TOGAF Series Guides. Version 9.2 is listed there as an earlier edition.

What are the phases of the ADM?

The Open Group's reference card for Version 9.2 lists a Preliminary Phase followed by Phases A to H: Architecture Vision, Business Architecture, Information Systems Architectures, Technology Architecture, Opportunities and Solutions, Migration Planning, Implementation Governance and Architecture Change Management. Requirements Management runs through all of them.

Is TOGAF mandatory for enterprise architecture?

No. TOGAF is a standard of The Open Group, described as an enterprise architecture methodology and framework. Nothing requires you to adopt it, and many organizations keep only its vocabulary and a few steps of its method.

Is there a TOGAF certification?

Yes. The Open Group presents a TOGAF certification portfolio on its site and maintains a directory of certified people. For the conditions, The Open Group's site is the only reference.

Every week, an article to know your IT estate better

Architecture documents, end of support, NIS2, CMDB, migrations: methods you can apply with or without Uncia.

Get a call from our team

Thirty minutes with a member of our team, remote or on site: Uncia on a demonstration instance, then on part of your own estate if you wish. We reply within 48 hours.

Request received

Thank you. A member of our team will reply within 48 hours to set a date.