Abstraction

Intro

Abstraction creates simplified, high‑level views by focusing on essential characteristics and hiding detail. In enterprise architecture, it enables clear communication and governance across layers and stakeholders.

Key points:

• Improves clarity by presenting concepts at the right level
• Supports reuse of patterns and standards across domains
• Common use cases: capability maps, process summaries, data domains, service interfaces, platform views
• Pitfall: over‑abstracting can hide critical constraints

Examples:

• Business capability map abstracting processes and systems
• API interface abstracting complex underlying services
• Data domain model abstracting physical schemas

In practice:

With OrbusInfinity, teams link this concept across strategy, processes, applications, and technology for traceability.

Related terms: Encapsulation; Layering; Decomposition

FAQs:

Q: Why is abstraction useful in EA?
A: It helps align decisions and communication without drowning in detail.

Q: How do I choose the right level?
A: Match the audience and decision, and maintain links to detailed artefacts.

‍