EA Domains
Business, application, data and technology architecture as viewpoints.
4 to work through
-
beginner Multiple choice
A team says a choice is "an enterprise architecture concern, not ours". What actually distinguishes an enterprise-level decision from a team-level one?
2 min answer -
intermediate
An enterprise architecture function is asked to cover business, application, data and technology domains. Where should its effort concentrate in a fast-growing company?
1 min answer -
intermediate
An enterprise architecture practice is strong in technology architecture and weak in business and data architecture. What problems does that imbalance cause?
2 min answer -
intermediate Multiple choice
Which enterprise architecture domain produces the most value in practice, and why?
2 min answer
4 terms in this topic
Decision Rights Boundary
The line separating choices a team may make alone from choices that bind other teams - drawn by where the consequence of a mistake lands, not by the …
conceptEA Domain Layers
The four conventional layers of enterprise architecture — business, data, application and technology — each answering a different question about the …
conceptEA Domains
The four conventional views of an enterprise — business, data, application, technology — and what each is actually for.
conceptSystem of Record
The single system authoritative for a business entity, from which all other copies derive - the absence of which is the dominant source of enterprise…
Neighbouring topics
Enterprise Architecture
General material on architecture at portfolio and estate scale.
Application Architecture
The application estate as a designed portfolio rather than an accumulation.
Technology Architecture
Platforms, runtimes and infrastructure standards across the estate.
Capability Maps in EA
The stable frame for hanging investment, ownership and health off.
Application Portfolio Management
Inventory, ownership, cost and health for every application.
Application Rationalisation
Retire, consolidate, replatform — and why retirement is under-applied.
Technology Standards
Guidance that teams follow because it helps, not because it is mandated.
Technology Radar
Adopt, trial, assess and hold — with movement, dates and owners.
Reference Architectures
Pre-approved templates for recurring solution shapes.
Architecture Governance
Preventive, automated controls rather than review meetings.
Architecture Review Boards
Thresholds, early engagement and a real route to accept deviation.
Enterprise Integration
Estate-wide integration strategy, standards and shared infrastructure.
TOGAF
The ADM as a checklist, tailored rather than followed literally.
EA Frameworks
Zachman, FEAF and others — vocabulary rather than method.
Architecture Roadmaps
Sequencing change across an estate with dependencies and funding.
Paved Roads
Making the supported path the easiest path, with a way to leave it.
Platform Teams
Reducing other teams' cognitive load, measured by adoption.
InnerSource
Open-source collaboration practices applied inside an organisation.
EA Metrics
Measuring whether architecture work changed anything.