Architecture Domain

Intro

An Architecture Domain is a scope such as business, data, application, or technology. In EA, domains help organise responsibilities and views.

Key points:

• Separates concerns for clearer ownership and decisions
• Improves traceability across cross‑domain changes
• Common use cases: domain‑specific standards, views, and governance
• Pitfall: siloed domains hinder end‑to‑end design if poorly integrated

Examples:

• Business domain defining capabilities and processes
• Data domain managing models, quality, and lineage
• Technology domain governing platforms and networks

In practice:

Coordinate domains within Enterprise Architecture forums.

Related terms: Business Architecture; Data Architecture; Technology Architecture

FAQs:

Q: How many domains should we use?
A: Start with business, data, application, technology; refine as needed.

Q: How to avoid siloed decisions?
A: Use cross‑domain governance and shared artefacts.

‍