If the term keeps coming up at work, you may be asking what is enterprise architecture. It is a blueprint linking business goals to processes, data, applications and technology, so IT choices support strategy.
This guide is part of the wider field of business technology, where strategy and IT decisions meet.
| Item | Value |
|---|---|
| First consistent use of the term “Enterprise Architecture” | 1989 (NIST Enterprise Architecture Model, seemingly) |
| First formal definition of the term | 1990 |
| Zachman’s framework paper for information systems architecture | 1987 |
| TOGAF first developed | 1995 |
| Typical architecture domains | Four (business, applications, data, technical) |
| Basic questions in the Zachman Framework | Six (what, how, where, who, when, why) |
These figures come from Wikipedia’s overview of enterprise architecture frameworks and Visual Paradigm’s framework guide. Sources get revised and dates can be disputed, so check the sources before you rely on the figures.
What does enterprise architecture cover?
Enterprise architecture looks at an organisation as one connected system. Wikipedia’s overview says it regards the enterprise as a large and complex system or system of systems, which is why architects need tools to step back from the detail builders work with.
Visual Paradigm’s guide describes the purpose as working out how an organisation can most effectively reach its current and future business goals. The same guide says enterprise architects keep IT systems aligned with ongoing business strategies and standards.
The guide lists four interrelated areas of specialisation, usually called architecture domains:
- Business architecture: the business strategy, governance, organisation and key business processes.
- Applications architecture: a blueprint for the individual systems to be deployed and how they interact.
- Data architecture: the structure of logical and physical data assets and the resources that manage them.
- Technical architecture: the hardware, software and network infrastructure that supports core applications.
Read from top to bottom, the domains move from why the organisation exists to what it runs on. A change in one layer, such as a new product, usually ripples into the others.

Why do organisations use enterprise architecture?
The German IT publication Computerwoche, in a March 2023 explainer, says enterprise architecture makes sure IT infrastructure matches business goals. It also lists uses beyond planning, which you can scan below.
- Guiding larger restructurings, such as change initiatives or the period after an acquisition.
- Supporting system development, IT management and decision-making.
- Reducing errors, outages and security gaps through IT risk management.
The same article also shows that results are uneven. Citing Bizzdesign’s State of Enterprise Architecture 2022 report, it says only 20 percent of respondents report that their EA programmes enable faster innovation and shorter time to market, and only 6 percent have agile teams whose architects can influence technology decisions.
Among the priorities that report found, 56 percent of EA professionals and IT decision-makers wanted to communicate the value of enterprise architecture to the business more effectively. For a beginner, that is a useful reminder: the discipline works best when it is explained in plain terms.
A short history of enterprise architecture
The idea is older than the name. Wikipedia traces the earliest rudiments of step-wise planning back to a 1962 Harvard Business Review article, and the sequence below covers the milestones that matter most.
- In 1982, John Zachman, working at IBM, outlined an enterprise-level framework for information systems architecture.
- In 1987, Zachman published his paper on a framework for information systems architecture. Wikipedia notes that it did not mention enterprise architecture.
- In 1989, the US National Institute of Standards and Technology published a five-layer model that seemingly was the first publication to use the term consistently.
- In 1990, the term was formally defined for the first time.
- In 1995, TOGAF was first developed, and in 1996 the Clinger-Cohen Act pushed US federal agency CIOs to maintain integrated systems architectures.
Details of these steps are in Wikipedia’s history section and a 2006 comparison of frameworks. Both agree that frameworks grew as technology spread through the workplace and large organisations needed a long-term plan.
The main enterprise architecture frameworks
A framework defines how to create and use an enterprise architecture. According to Wikipedia, its guidance falls into three main areas:
- Descriptions of architecture: how to document the enterprise from several viewpoints.
- Methods for designing architecture: the processes architects follow.
- Organisation of architects: team structure, governance, skills and training.
Four frameworks come up most often for beginners:
- Zachman Framework: a classification scheme with six perspectives (Planner, Owner, Designer, Builder, Subcontractor and User) crossed with six basic questions. The 2006 comparison notes that it gives no guidance on sequence, process or implementation.
- TOGAF: built around the Architecture Development Method, which Visual Paradigm’s guide says specifies a process for developing enterprise architecture.
- DoDAF: the US Department of Defense framework, which the same guide says is primarily focused on defence applications but can also be applied to commercial systems.
- FEAF: the US federal framework, written in response to the Clinger-Cohen Act of 1996.
The 2006 paper adds that some frameworks were built for very specific areas while others have broader functionality. Picking one is therefore about fit with your stakeholders, not about finding a universal winner.
How enterprise architecture relates to AI and low-code
Computerwoche says enterprise architecture has become a priority for organisations that want to keep pace with newer technologies such as cloud, the Internet of Things and machine learning. Each new technology raises the same architecture question: where does it fit among existing systems, data and processes?
Questions about artificial intelligence in business are partly architecture questions, such as which data feeds a model and which applications use its output. In the same way, low-code no-code platforms add a new place where applications get built, and someone has to decide how that layer connects to the rest.
Where beginners can start
You do not need a certification to begin thinking like an architect. Start small and describe one part of an organisation you already know.
- Learn the four domains so you can tell a business question from a data or technology question.
- Pick one process, such as taking an order, and list the applications and data it touches.
- Walk through the Zachman questions (what, how, where, who, when and why) for that process.
- Read an overview of one framework to see how its method organises the same information.
- Ask who decides when two systems overlap, because governance is part of the discipline.
The exercise rarely produces a perfect diagram. It does show where the gaps and overlaps are, and that is the habit enterprise architecture is meant to build.
Frequently asked questions
Is enterprise architecture the same as IT architecture?
Show answer
Not quite. Computerwoche says modern enterprise architecture strategies are not limited to the IT department but extend the approach across the whole enterprise, so that the organisation stays aligned with its digital transformation strategy. See the Computerwoche explainer.
When did the term “enterprise architecture” first appear?
Show answer
As of Wikipedia’s account, the NIST Enterprise Architecture Model of 1989 seemingly was the first publication to use the term consistently. The term was formally defined for the first time in 1990, according to Wikipedia.
Which framework should a beginner learn first?
Show answer
It depends on what you want to understand. The Zachman Framework helps you see how views and questions fit together, while TOGAF is organised around a process. The 2006 comparison study aims to help readers choose a best-fit framework for specific stakeholder needs.
Do small organisations need enterprise architecture?
Show answer
The sources frame it mainly for large organisations. Computerwoche says it suits large companies going through digital transformation, because it pulls existing processes and applications into a seamless environment. A smaller team can still borrow the basic questions to map how its tools and processes connect.



