TOGAF Fundamentals
TOGAF is an enterprise architecture framework and method that structures, develops, governs, and evolves architecture work across business, data, application, and technology domains.
itEnterprise architecture and integration | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Don't Panic
Don't Panic — TOGAF Fundamentals
TOGAF is a framework and a method for enterprise architecture, which is a less flattering way of saying it is a disciplined way to stop large organizations from making the same decision in seven incompatible places. It does not arrive with your architecture in it. It arrives with a cycle, a vocabulary, and the strong implication that you are meant to do the work.
The useful mental picture is the ADM — the Architecture Development Method. You prepare, agree a vision, describe the business, then the data, application, and technology domains, sequence the opportunities and solutions into a roadmap, govern the implementation, and manage change. Requirements run across the whole cycle rather than through one phase, which is the part most teams discard first and miss most later.
Tailoring is the load-bearing idea. The ADM is a method to be adapted to the enterprise, its delivery processes, its risk appetite, and its scope, not a script to run end to end unchanged. Running every phase verbatim produces a complete document set that proves the method was followed and tells you nothing about whether the enterprise improved. The Open Group says this explicitly, which is unusually helpful of a standard.
The four architecture domains — business, data, application, and technology — exist so a change in one has somewhere to show its effect on the others. Architecture views translate the same architecture into the concerns a given stakeholder can act on, and governance keeps the decisions, standards, exceptions, and implementation evidence attached to the approved direction rather than drifting apart.
The surprise is that a framework this widely adopted still fails often. The method is sound; the failure is in treating it as the deliverable. An architecture that nobody implements, or a governance board that only approves, is the ADM run as paperwork.
The 10th Edition split into Fundamental Content and Series Guides is the standard catching up with how it was always meant to be used: universal concepts plus configurable how-to, with tailoring made first-class rather than hidden in a preface.
Read the Introduction for the full method and domain structure. The Slides give you the ADM cycle at a glance, and the Cheatsheet keeps the phases and tailoring rules to hand. Field Notes adds the operational traps that turn a respectable method into a binder nobody opens. The Quiz checks whether the terms survive a relabelling.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://www.opengroup.org/togaf
Supports
- TOGAF framework and methodology definition
- 10th Edition structure (Fundamental Content and Series Guides)
- Vendor-neutral, public-domain standard positioning
- Version history milestones across versions 1.0 through 9.2
- https://www.opengroup.org/architecture/togaf7-doc/arch/p2/p2_intro.htm
Supports
- ADM definition as a reliable, proven method
- ADM cycle phases and iterative development
- Tailoring guidance and reasons to adapt the ADM
- Requirements management across the cycle
- Architecture design principles
- Enterprise Continuum and repository context
- https://help.opengroup.org/hc/en-us/articles/32115987894930-How-the-ArchiMate-Language-and-the-TOGAF-Standard-Complement-Each-Other
Supports
- TOGAF and ArchiMate complementarity (method vs modelling language)
- Four architecture domains shared across the two standards
- Views, viewpoints, stakeholders, concerns
- Per-phase mapping of ArchiMate views to ADM phases
- Architecture governance and traceability
- https://en.wikipedia.org/wiki/TOGAF
Supports
- TOGAF version history from 1.0 (1995) through 8.1.1 (2006) and 9 (2009)
- TAFIM origin and the 9.x content metamodel changes
- https://pubs.opengroup.org/architecture/togaf9-doc/arch/chap04.html
Supports
- TOGAF 9 new features including the formal Content Metamodel and architecture repository
- https://publications.opengroup.org/c182
Supports
- TOGAF 9.2 business architecture and content metamodel improvements
- https://www.opengroup.org/open-group-announces-launch-togaf-standard-10th-edition
Supports
- TOGAF Standard 10th Edition split into Fundamental Content and TOGAF Series Guides and its agile-enterprise guidance
- Field Notes shift card on the modular 10th Edition structure
- https://doi.org/10.1109/EMR.2020.3031968
Supports
- EA initiatives failing when not established at operational and tactical levels, the difficulty card on business-vs-diagram
- https://www.isaca.org/resources/isaca-journal/issues/2017/volume-4/challenges-and-lessons-learned-implementing-itil-part-2
Supports
- The user cost of added controls and the tradeoff card on governance spending lead time
- https://www.sparxsystems.com/
Supports
- Sparx Enterprise Architect architecture modeling and repository product role in the Landscape
- https://www.avolutionsoftware.com/abacus/
Supports
- Avolution ABACUS repository and prebuilt TOGAF and ArchiMate content in the Landscape
- https://www.bizzdesign.com/
Supports
- BiZZdesign Enterprise Studio cross-domain modeling product role in the Landscape
- https://www.adoit.org/
Supports
- BOC ADOIT architecture repository and governance workflow product role in the Landscape
- https://www.orbussoftware.com/
Supports
- Orbus iServer Microsoft-integrated architecture platform product role in the Landscape
- https://www.softwareag.com/en/products/aris/aris-platform.html
Supports
- Software AG ARIS process and architecture modeling product role in the Landscape
- https://www.leanix.net/
Supports
- LeanIX application portfolio and EA management product role in the Landscape
- https://www.mega.com/en/solutions/enterprise-architecture
Supports
- MEGA HOPEX architecture modeling and repository product role in the Landscape
- https://www.essential-project.eu/
Supports
- The Essential Project open-source EA repository product role in the Landscape
