Enterprise Architecture

Enterprise architecture (EA) is the practice of describing an organization's business, information, applications, and technology as a connected whole, and using those descriptions to steer change.

12 frameworks, from 1965 to today · Information Systems · Business, Management & Finance

still a working view ended · each leads to its entry below

Overview

Enterprise architecture (EA) is the practice of describing an organization's business, information, applications, and technology as a connected whole, and using those descriptions to steer change1. Its central object is not a single system but the architecture: a structured account of what the enterprise does, what information and systems support it, and how those parts fit together, together with the rules and plans that keep them fitting together as the organization changes. What is at stake is coordination at scale. Large organizations accumulate hundreds of systems, overlapping data, and projects that duplicate or contradict one another; EA exists to make that tangle visible, to decide what the target state should be, and to govern the path from here to there. Its history is a sequence of attempts to answer three questions: how to describe an enterprise, how to plan its change, and how to keep the plan honest.

Precursors: Planning Information Systems in the 1960s and 1970s

The problems EA later addressed first appeared as planning problems. As computers spread through large organizations in the 1960s, firms found themselves buying systems department by department, with no view of the whole. Information systems planning emerged as a management concern: the idea that an organization should decide in advance which information systems it needs, in what order, and for what business purposes, rather than reacting to each request.

A landmark statement of this view was the business systems planning method developed at IBM in the 1970s, which mapped business processes against data classes to derive an orderly portfolio of systems. The underlying claim was that data, not programs, should be the stable foundation of planning: if an organization understood the information it depended on, systems could be built and rebuilt around it. These methods were heavy and consultant-driven, but they established the core EA instinct—that the enterprise, not the individual project, is the right unit of design.

Zachman: A Framework for Description (1987)

The word "architecture" entered the field through John Zachman. In a 1987 article in the IBM Systems Journal, "A Framework for Information Systems Architecture," Zachman argued that information systems had become too complex to describe ad hoc, and borrowed a lesson from building construction: different participants in a building project—owner, architect, builder—each need a different description of the same building, and those descriptions must be consistent with one another.

Zachman's framework is a grid. Its rows are perspectives or audiences (planner, owner, designer, builder, subcontractor, and the functioning system itself), and its columns are interrogatives—what, how, where, who, when, and why—each corresponding to a kind of model: data, function, network, people, time, and motivation. The cell at a given row and column is the model that a particular audience needs for a particular aspect of the enterprise. The framework's power was conceptual rather than procedural: it gave practitioners a vocabulary for completeness, showing that most organizations described some cells well (usually data and function for builders) and left others empty. It did not say how to fill the grid or in what order, a gap later methods tried to close.

Enterprise Architecture Planning and the First Methods (1990s)

Through the early 1990s, EA became a named practice with its own methods. Steven Spewak's Enterprise Architecture Planning, published in 1992, organized the work into layers—data, applications, and technology—each described for a current state and a target state, with a migration plan between them. The layering idea proved durable: architecture is described at successive levels, from business concerns down to technical infrastructure, with each level constraining the one below.

A parallel strand came from defense. The U.S. Department of Defense, managing enormous and interdependent systems, developed the C4ISR Architecture Framework in the 1990s, which specified a set of views—operational, systems, and technical—that together describe an enterprise for different purposes. This evolved into the Department of Defense Architecture Framework (DoDAF), which organized architecture description around viewpoints: coherent collections of models serving a particular concern, such as capability, operational activity, or systems interface. DoDAF's contribution was to make viewpoint selection explicit—you describe the enterprise from the angle the decision requires—and to tie architecture to acquisition and capability decisions rather than to documentation for its own sake.

TOGAF and the Industrialization of Method (1995 onward)

The Open Group Architecture Framework (TOGAF), first released in 1995 and built on an earlier U.S. Department of Defense technical architecture framework, became the most widely adopted general-purpose EA method. Its core is the Architecture Development Method (ADM): a cyclic process that moves from preliminary setup through a vision of the architecture, then business, information systems, and technology architectures, then opportunities and solutions, migration planning, implementation governance, and change management, before returning to a new cycle.

The ADM's significance is that it turned architecture into a repeatable organizational process with defined phases, inputs, and outputs, and it introduced the idea of an architecture repository and a continuous requirements-management step running through every phase. TOGAF also standardized the notion of architecture artifacts and a content framework, and it explicitly separated architecture description from the method used to produce it. Its adoption spread through large enterprises and consultancies, and later versions added guidance on architecture capability, governance, and—in recent editions—agile delivery and digital transformation.

Describing Architecture: Standards and Modeling Languages

As methods multiplied, the field needed a common way to write architectures down. The IEEE 1471 standard, published in 2000 and later revised as ISO/IEC 42010, defined the basic vocabulary that most later work adopted: an architecture has stakeholders with concerns; a view addresses a set of concerns; a viewpoint is the convention for constructing a view; and an architecture description is the organized set of views. This settled a persistent confusion—that a diagram is not an architecture, but one view of one, meaningful only relative to the concerns it serves.

Modeling languages followed. The Unified Modeling Language (UML), standardized in the late 1990s, was general-purpose software notation, and EA practitioners adapted it. The ArchiMate language, introduced in 2004 and later standardized by The Open Group, was designed specifically for enterprise architecture, with a small set of concepts—business actors, services, application components, technology nodes—and explicit service relationships linking the layers. ArchiMate's concrete contribution was to make cross-layer dependency modelable: a business service can be shown as realized by an application service, which runs on a technology node, in one consistent notation. Alongside these, structured frameworks such as the Zachman grid and DoDAF viewpoints continued in use, and the field increasingly treated description standards and modeling languages as separable choices layered on top of any method.

Governance: Making Architecture Binding

A description changes nothing by itself. Architecture governance is the set of decision rights, review bodies, and compliance processes that give architecture authority over projects. In practice this meant architecture review boards that assess projects against target-state principles, architecture principles stated as standing rules, and exception processes for justified deviations. Governance connected EA to IT governance more broadly: architecture decisions became part of how an organization directed its technology investment, and compliance with the architecture became a condition of project approval. The recurring tension, visible throughout the field's later history, is between governance that is rigorous enough to prevent drift and light enough not to strangle delivery.

Capability-Based Planning

A shift in emphasis came with capability-based planning, which describes the enterprise in terms of capabilities—what the organization is able to do, such as "process an insurance claim" or "manage supplier relationships"—rather than in terms of processes, systems, or organizational units. A capability is a stable, outcome-oriented unit that survives reorganizations; processes and systems are the means by which it is delivered. This framing, prominent in defense planning and later in business architecture, let executives connect strategy to investment: a capability assessment shows where the organization is weak, and the architecture shows what would strengthen it. It also gave EA a language that business leaders could use, addressing a long-standing complaint that architecture was a technical conversation conducted in technical terms.

Agile and Lean Enterprise Architecture

From the 2010s, the field confronted agile and lean delivery. If software is delivered in short increments by empowered teams, a heavy upfront target-state architecture and a slow review board become obstacles. The response was not to abandon architecture but to change its tempo and granularity: architecture as emerging and evolutionary, with lightweight principles, architecture runways that prepare just enough foundation for upcoming work, and architects embedded in delivery teams rather than sitting in a separate function. Lean thinking contributed the idea of limiting architecture work to what is pulled by real demand, and of treating architecture as a service to delivery rather than a gate. This remains contested ground: practitioners disagree about how much upfront design is necessary and how governance can operate at agile speed without becoming either absent or bureaucratic.

The Present

Enterprise architecture today is a plural field. TOGAF's ADM remains the most widely taught method, often used in adapted rather than literal form; DoDAF and its viewpoint approach persist in defense and government; ArchiMate and UML supply the notation; and ISO/IEC 42010's vocabulary underpins how architectures are described and reviewed. Capability-based planning has become standard in business architecture, and agile and lean variants have reshaped how architecture work is sequenced and governed. The open questions are the ones its history kept raising: how to keep architecture descriptions current when systems change continuously, how to govern without slowing delivery, and how to make the enterprise-wide view genuinely useful to decision-makers rather than a documentation obligation.

References

  1. Enterprise architecture, Wikipedia

The frameworks of Enterprise Architecture

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1965-1990

    Information Systems Planning

    Which information systems should an organization build, and in what order?

    Fly to its tower in Nousfarer

  2. 1970-1990

    Business Systems Planning

    How do business processes and data determine a systems portfolio?

    Fly to its tower in Nousfarer

  3. 1987-Present

    Zachman Framework

    What descriptions does an enterprise need, for whom?

    Fly to its tower in Nousfarer

  4. 1992-2005

    Enterprise Architecture Planning

    How do we get from current to target architecture?

    Fly to its tower in Nousfarer

  5. 1995-Present

    Architecture governance

    Who decides whether projects conform to the architecture?

    Fly to its tower in Nousfarer

  6. 1995-Present

    Department of Defense Architecture Framework

    Which views describe an enterprise for a given decision?

    Fly to its tower in Nousfarer

  7. 1995-Present

    TOGAF Architecture Development Method

    What repeatable process produces an enterprise architecture?

    Fly to its tower in Nousfarer

  8. 2000-Present

    Capability-based planning

    What is the organization able to do, and what delivers it?

    Fly to its tower in Nousfarer

  9. 2000-Present

    ISO/IEC 42010

    What is an architecture description made of?

    Fly to its tower in Nousfarer

  10. 2004-Present

    ArchiMate

    How can dependencies across business and IT layers be modelled?

    Fly to its tower in Nousfarer

  11. 2004-Present

    Enterprise Architecture Modeling Languages

    What notation should enterprise architectures be written in?

    Fly to its tower in Nousfarer

  12. 2010-Present

    Agile and lean enterprise architecture

    How can architecture keep pace with fast delivery?

    Fly to its tower in Nousfarer

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

Information Systems PlanningBusiness Systems PlanningZachman FrameworkEnterprise Architecture PlanningArchitecture governanceDepartment of Defense Architecture Fr…TOGAF Architecture Development MethodCapability-based planningISO/IEC 42010ArchiMateEnterprise Architecture Modeling Lang…Agile and lean enterprise architecture

Beyond the field

Where Enterprise Architecture's ideas came from in other fields, and what they led to there: the strongest 12 of 42 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Enterprise Architecture is a planet in Nousfarer

Its city has a tower for each of these 12 frameworks. Land, walk in, and climb one concept at a time.

Land on Enterprise Architecture

Related fields

Fields its ideas are linked to

More in Information Systems

See where Enterprise Architecture sits on the Map of Human Knowledge