Skip to content
Software Architecture Guide

Enterprise Architecture

Explanation

Section titled “Explanation”

Enterprise architecture, or EA, looks at the organization as a whole. A well-known definition calls it a discipline for leading an enterprise’s response to disruptive forces. It does this proactively and holistically. It analyzes how change is carried out toward the desired business vision and outcomes.

Steering toward a target. The same definition says EA steers decision making toward the future-state architecture, also called the target architecture. Decisions made today should move the organization toward that target.

Goals. The main goals are:

  • better efficiency and effectiveness,
  • lower cost and risk,
  • better alignment between business and IT.

Difference from application architecture. Single-application architecture deals with one system. EA deals with how to organize many applications into a coherent whole. The iSAQB advanced EAM module frames the question this way: how do you keep a large IT and application landscape consistent and aligned with corporate strategy? See Relationship between Enterprise Architecture and Application Architecture.

Frameworks. The Zachman Framework is a classification schema, not a methodology or process. Its author says it is independent of methods and tools. That is why it can coexist with process frameworks such as the TOGAF Architecture Development Method. See Zachman Framework and TOGAF.

Challenges.

  • EA initiatives must recognize and respect organizational and political realities.
  • An organization’s full EA is too complex and extensive to document completely. Focused, incremental work is more practical.

Example

Section titled “Example”

A company runs separate systems for orders, billing and customer service. Each team chose its own tools. Leadership wants a clear picture of how these systems fit together and where they should be in a few years. The EA work describes that future state. It then guides each new project toward it. The team does not try to document everything at once. It starts with the areas that matter most and grows from there.

Trade-offs

Section titled “Trade-offs”

EA gives an enterprise-wide view, but it must work within the organization’s political realities. Ignoring them puts an initiative at risk. Documenting everything is impractical, so the work must stay focused and incremental. That means some areas stay undocumented for a while.

Checks

Section titled “Checks”
  • The document states which business vision or strategy the enterprise-level architecture supports.
  • A target (future-state) architecture is described and used to steer decisions.
  • The scope of the EA work is limited to the areas that matter most, not the entire organization.
  • Organizational and political realities are acknowledged in how the EA approach is applied.
Section titled “Related”

Sources

Section titled “Sources”