TOGAF® Standard, 10th Edition · OGEA-101 Foundation · Quick revision
Interoperability
Official definition — learn word for word
1.“The ability to share information and services.”
2.“The ability of two or more systems or components to exchange and use information.”
3.“The ability of systems to provide and receive services from other systems and to use the services so interchanged to enable them to operate effectively together.”
Source: CC §4.51 · TECH §7.1
Memory aid
Three classes: B-I-T — Business (operational), Information, Technical.
Memory aid — not TOGAF wording.
In plain words
How well processes, information and systems can work together and share with each other.
Plain-English summary — not TOGAF wording.
Worked example
DUK decides: Business — one admissions process for all campuses; Information — one student record shared by every system; Technical — all systems talk through the same API gateway.
Illustrative example (Digital University Kerala) — not from the Standard.
01Mind map — related concepts
Interoperability
3 CLASSES
Business · Information · Technical
EAI VIEW
Presentation · Information · Application · Technical
THROUGH THE ADM
Revealed in A → logically implemented in F
PHASE E · 9.3.5
Consolidate and reconcile requirements
RECORDED IN
Architecture Requirements Specification
NOT TO CONFUSE WITH
Only a technical concern
Source: TECH §7.1–7.2 · ADM §9.3.5 · AC §4.2.6
02Categories of interoperability (TECH §7.2)
| Category | Defines |
|---|---|
| Operational or Business | How business processes are to be shared |
| Information | How information is to be shared |
| Technical | How technical services are to be shared, or at least connect to one another |
From an IT perspective it can also be viewed like Enterprise Application Integration: presentation, information, application, and technical integration/interoperability.
Source: TECH §7.2
03Interoperability through the ADM (TECH §7.1)
Phase Anature and security of exchanges revealed in business scenarios
Phase Bexchanges defined in business terms
Phase CData: content detailed · Application: how applications share
Phase Dtechnical mechanisms specified
Phase Eactual solutions (e.g. COTS) selected
Phase Finteroperability logically implemented
Source: TECH §7.1
04Where it appears in the ADM
Phase E · Step 9.3.5
Consolidate and Reconcile Interoperability Requirements.
ADM §9.3.5
Deliverable
The Architecture Requirements Specification includes interoperability requirements.
AC §4.2.6
05Exam traps
“Interoperability is only technical” → Business (operational), information, and technical
“It is defined once, in Phase D” → It is present throughout the ADM, from Phase A to Phase F
“Actual solutions are selected in Phase D” → Phase E selects the actual solutions (e.g. COTS)
“Interoperability is implemented in Phase E” → It is logically implemented in Phase F
06Self-test — tap to reveal
Q1Give the short definition of interoperability.
The ability to share information and services.
Q2Name the three categories.
Operational/business, information, technical.
Q3Where are exchanges first revealed?
Phase A, in business scenarios.
Q4Which phase specifies technical mechanisms?
Phase D.
Q5Which phase selects actual solutions?
Phase E.
Q6Which phase logically implements interoperability?
Phase F.
Q7Which Phase E step reconciles interoperability requirements?
9.3.5.
Q8Which deliverable records interoperability requirements?
The Architecture Requirements Specification.