Interoperability Perspectives
2026-10-09
A broad topic that can be analyzed from multiple angles
These perspectives form the foundation for the rest of the course — we will return to them regularly.
Four basic integration styles (Hohpe & Woolf, EIP Chapter 2)
Prepare 1–2 slides summarizing your key findings. You have 30 minutes.
Syntax vs. Semantics: Consider the simple XML tag
<customer>. While the data format may be identical, the meaning of Customer in a banking application is quite different from the meaning of Customer in a health insurance application.
Examples of technologies and concepts used on different levels
| Level / Task | Syntactic | Semantic | Organizational |
|---|---|---|---|
| Exchange | Exchange formats: CSV, EDIFACT, XML, JSON Query languages: SQL, XPath |
Schema mapping, ontologies | Message exchange |
| Integrate | Databases, REST, OData | Schema languages, generic and user-defined schemas. | Correlation and choreography |
| Orchestrate | BPMN, Petri Nets, Workflow engines | Verification, service invocation, integration patterns | Choreography |
Different integration scenarios and methods are used in different domains
| Application Domain | UI Integration | Process Integration | Application & Function Integration | Data & Information Integration |
|---|---|---|---|---|
| Method / Style | UI-oriented | Message-oriented | Message-oriented | Query-based |
| Realization | Portals, Robotic Process Automation, Workflow management systems | Process engines | EAI systems, Message-oriented middleware, ETL tools | ETL tools, everything mentioned in Levels and Tasks |
Three levels, two questions
Data level
Process level
The same what / how pattern applies on all three levels (data, service, process).
Systems Integration | Interoperability Perspectives | Prof. C. Drumm