Frameworks compared

They’re not all the same kind of thing

The most common confusion about EA frameworks is comparing things that do different jobs. It helps to sort them by type:

Type	What it gives you	Examples
Method / process	How to do architecture work, step by step	TOGAF ADM
Taxonomy / ontology	How to classify architecture descriptions	Zachman
Notation / language	How to draw and model architecture	ArchiMate, C4, BPMN
Body of knowledge	Concepts and practices for a discipline	BIZBOK
Scaling / delivery framework	How architecture fits into agile delivery at scale	SAFe, Open Agile Architecture
Standard	Agreed vocabulary and requirements for architecture descriptions	ISO/IEC/IEEE 42010

Most mature practices combine several: for example, TOGAF for method, BIZBOK concepts for business architecture, ArchiMate for enterprise modeling, C4 for software views, and lean practices (ADRs, radar) for day-to-day decisions.

Side by side

Framework	Type	Origin	Strengths	Weaknesses	Use it when
TOGAF	Method + content + governance	The Open Group	Comprehensive; widely recognized; certification; vendor-neutral	Large; easy to over-apply; can feel heavyweight	You need a shared method and vocabulary, or a credential
Zachman Framework	Taxonomy	John Zachman (1987)	Rigorous classification; checks completeness	No method; doesn’t tell you what to do	You want to check that architecture descriptions cover all perspectives
FEAF	Method + reference models	US federal government	Reference models; designed for very large public organizations	Government-specific	Working in or with US public sector
Gartner’s approach	Practice guidance	Gartner	Pragmatic, business-outcome-focused, research-backed	Proprietary; requires a subscription	Your organization already uses Gartner research
SAFe	Scaling framework	Scaled Agile, Inc.	Places architecture inside agile delivery; runway and enablers	Can be prescriptive; adoption is a big commitment	Your organization already runs SAFe
Open Agile Architecture (O-AA)	Standard	The Open Group	Architecture for agile and digital organizations	Less widely adopted than TOGAF	You want a standard-backed agile EA approach
BIZBOK	Body of knowledge	Business Architecture Guild	The deepest treatment of capabilities, value streams, and information mapping	Business architecture only; full guide requires membership	You’re building a business architecture practice
ArchiMate	Modeling language	The Open Group	Connects business, application, and technology layers; aligned with TOGAF; tool support	Learning curve; can overwhelm non-specialists	Enterprise-level modeling and impact analysis
C4 model	Diagramming approach	Simon Brown	Simple; developer-friendly; four clear zoom levels	Software-focused; doesn’t cover business architecture	Communicating software structure
ISO/IEC/IEEE 42010	Standard	ISO / IEC / IEEE	Precise vocabulary: stakeholders, concerns, viewpoints, views	Abstract; not a method	Structuring architecture descriptions
DoDAF / NAF	Framework	US DoD / NATO	Rich viewpoints for defense systems	Defense-specific; heavyweight	Defense and government contracting

How they fit together at Quillfeather

• TOGAF, tailored heavily: the ADM shaped the EU expansion work (module 5); principles and governance followed TOGAF’s format (module 6)
• BIZBOK concepts: capability map and value streams (module 4)
• ArchiMate, in Archi: the enterprise model and layered views (module 7)
• C4, as diagrams-as-code: solution views alongside ADRs (module 7)
• Lean practices: ADRs, radar, paved road, fitness functions (module 8)
• SAFe: not used, but “architectural runway” entered the vocabulary

Choosing for your organization

• Don’t announce a framework. Use what helps, quietly. Talk about problems and outcomes, not frameworks.
• Learn TOGAF properly anyway. It’s the common language of the profession and the most recognized credential.
• Pick one modeling approach for each audience and use it consistently.
• Match your organization’s existing delivery framework. If it runs SAFe, use SAFe’s architecture vocabulary.