What enterprise architecture is: business, data, application and technology
In short: Enterprise architecture (EA) is the practice of describing how an organisation works today, deciding how it should work in future, and planning the changes in between. It covers four linked domains: business, data, application and technology. The goal is IT that clearly supports business goals.
Why organisations need architecture
Large organisations collect systems over many years. Each department buys its own tools, data is copied between them, and nobody can say which servers support which services. Enterprise architecture (EA) brings order. It provides a shared, big-picture model of the organisation so that leaders can make change decisions with their eyes open. A city planner is a useful comparison: they do not design each house, but they set zones, roads and utilities so the city grows sensibly.
The four domains
| Domain | Questions it answers | Example artefact |
|---|---|---|
| Business | What do we do, for whom, and how? | Capability map, process model |
| Data | What information do we hold, where, and who owns it? | Data model, data flow diagram, classification |
| Application | Which systems support each capability, and how do they connect? | Application portfolio, integration diagram |
| Technology | What infrastructure runs the applications? | Network and hosting diagrams, technology standards |
Data and application architecture together are sometimes called information systems architecture. Security is not a separate box: it cuts across all four domains, which is why many teams add a security view to every model.
How EA work is done
Architects document the baseline (current state) and agree a target (future state) with business leaders. A gap analysis lists what must be added, changed or retired. The gaps become a roadmap of projects in a sensible order, considering cost, risk and dependencies. Governance then checks that projects follow the agreed direction. Frameworks such as TOGAF and Zachman give structure to this work.
Why it matters to engineers
EA can sound like management theory, but it shapes daily technical work:
- A standard that says "all new apps use the central identity provider" decides how you design authentication.
- A roadmap that retires the on-premises data centre in three years changes how much you invest in its switches.
- An application portfolio shows which servers support critical services, which guides patching and disaster recovery priorities.
- Data ownership and classification tell you which systems need encryption and stricter access control.
Tip: a common failure is "ivory tower" EA: beautiful diagrams that nobody uses. Good architecture is lightweight, kept up to date and tied to real decisions and budgets.
Roles you may meet include the enterprise architect (whole organisation), solution architect (one project or system) and domain architects such as network, security or data architects. Many engineers move into solution architecture as their career grows.
Practice
Name the four classic enterprise architecture domains.
What is a gap analysis in EA?
How does an enterprise architect differ from a solution architect?
Key takeaways
- EA describes the current organisation, the desired future and the route between.
- Four domains: business, data, application and technology; security cuts across all.
- Baseline, target, gap analysis and roadmap are the core activities.
- Governance keeps projects aligned with the agreed direction.
- Useful EA is lightweight, current and tied to real decisions.
Original content written by Mohamed Fayas for FM TecHub. © 2026 FM TecHub. You're welcome to share a link to this page; please don't copy the text elsewhere without permission.