← Dashboard
T17Definition-Heavy

TOGAF Reference Models — TRM & III-RM

2
TOGAF reference models
Taxonomy + Graphic
Both have these 2 parts
Platform
TRM focus
BIF
III-RM drives Boundaryless Info Flow
💡 The Big Idea

The Open Group publishes two TOGAF reference models — in TOGAF 10 as TOGAF Series Guides, not part of the Fundamental Content: the TRM (Technical Reference Model) — about the application platform, portability and interoperability — and the III-RM (Integrated Information Infrastructure Reference Model) — about the applications space and Boundaryless Information Flow. Both have exactly two components: a taxonomy and a graphic.

A reference model is a blueprint you start FROM rather than a blank page. TOGAF's two models both live at the Foundation end of the Enterprise Continuum.

  • ▸📐 A reference model = a generic, reusable model that seeds a specific architecture
  • ▸🧱 Both TOGAF models sit in the Reference Library of the Architecture Repository
  • ▸📚 TOGAF 10: both are published as TOGAF Series Guides (the TRM guide is G175, Sept 2017) — they are NOT in the six Fundamental Content documents. Earlier TOGAF 9.1 included them in the main standard.
  • ▸🔤 Both consist of exactly TWO components: a TAXONOMY (terminology + description) and a GRAPHIC (visual of the taxonomy)
  • ▸⚠️ TOGAF does NOT mandate their use — they are provided as a starting point and can be replaced with an industry model

Explore the layers of the TRM, the parts of the III-RM, and the difference between the two.

The Technical Reference Model is part of TOGAF’s Foundation Architecture. It has two components: a taxonomy (terminology + description of platform services) and a graphic (a visual of that taxonomy). Its aim: application portability and interoperability via a consistent set of platform services.

Application Software▾

Split into Business Applications (specific to a business need, e.g. payroll) and Infrastructure Applications (general-purpose, e.g. email, a browser). Sits on top of the platform.

Application Platform Interface (API)▾

The boundary between application software and the platform. A consistent API here gives applications portability across platforms.

Application Platform▾

The heart of the TRM — a single conceptual platform offering ~12 categories of service (see below). The TRM's goal is a consistent set of platform services so applications are portable and interoperable.

Communications Infrastructure Interface▾

The boundary between the platform and the communications infrastructure.

Communications Infrastructure▾

The networks, hardware and physical links that carry information between systems — local and wide-area, including the basic long-haul connections.

Application Platform — the ~12 service categories
Data InterchangeData ManagementGraphics & ImagingInternational OperationsLocation & DirectoryNetwork ServicesOperating System ServicesSoftware EngineeringTransaction ProcessingUser InterfaceSecuritySystem & Network Management
Plus Service Qualities (e.g. availability, security, manageability) shown running down both sides of the graphic — they apply to every service.

The TRM describes a generic application platform and the services it provides. Its purpose is portability and interoperability.

  • ▸🎯 Focus: the Application Platform space — the layer between application software and the communications infrastructure
  • ▸🔌 Structure: Application Software → Application Platform Interface → Application Platform → Communications Infrastructure Interface → Communications Infrastructure
  • ▸🧰 The Application Platform offers ~12 service categories (Data Management, Security, Network Services, User Interface, …)
  • ▸🏛️ Service Qualities (availability, security, manageability, …) run down both sides — they apply to every service
  • ▸💡 Goal: application PORTABILITY (move an app between platforms) and INTEROPERABILITY (apps work together)

The III-RM zooms into the applications space to model an integrated information infrastructure.

  • ▸🎯 Focus: the Applications space — Business Applications and Infrastructure Applications
  • ▸🧩 Infrastructure Applications include: Brokering apps, Information Provider apps, Information Consumer apps, Development tools, Management utilities
  • ▸🌊 Driving vision: Boundaryless Information Flow — the right information to the right people at the right time, across boundaries
  • ▸🔍 It is a SUBSET of the TRM's scope, but it EXPANDS the applications part — fundamentally an Application Architecture reference model

Both are TOGAF reference models with a taxonomy and a graphic. The difference is what they model:

  • ▸🔧 TRM → the PLATFORM. Concern: portability & interoperability of applications.
  • ▸📱 III-RM → the APPLICATIONS. Concern: an integrated information infrastructure for Boundaryless Information Flow.
  • ▸🔗 Relationship: III-RM is derived from the TRM — a subset in scope that expands the business/infrastructure applications detail.
  • ▸⚠️ Trap: "the III-RM is about the technology platform" — FALSE (that's the TRM).