iwantcoding.com
🔥 Daily 👥 Rooms 🏆 Top Log in Sign up

1.1 Defining EA

Enterprise Architecture (EA) is the conceptual blueprint that aligns business strategy with IT infrastructure. The book defines EA as four interdependent layers - Business, Information, Application, Technology.

1.1 Defining Enterprise Architecture

What EA actually is

Enterprise Architecture is a conceptual blueprint that defines the structure and operation of an organisation, aligning business strategy with IT infrastructure across four interdependent layers.

Business Architecture strategy, processes, governance Information Architecture data models, standards, sharing Application Architecture the software landscape Technology Architecture networks, servers, cloud, devices Figure 1.1 - The four EA layers

Why each layer needs the others

Business drives what Information must capture. Information shapes what Applications must operate on. Applications run on what Technology must provide. Technology constrains what Business can promise.

LayerDrivesConstrained by
BusinessAll other layersRegulatory + market
InformationApplication data shapesBusiness processes
ApplicationTechnology capacity needsInformation data model
TechnologyCost, latency, sovereigntyApplication requirements

Worked example - a bank loan service

LayerElement
BusinessApprove consumer loans within 24 hours
InformationApplicant identity, credit score, document set
ApplicationLoan engine, KYC service, document store
TechnologyCore banking, identity provider, message bus

When EA earns its keep

  • Mergers and acquisitions (whose stack survives?)
  • Regulatory change (Data Privacy Act, BSP circulars)
  • Cloud migration (what moves, what stays, what re-platforms?)
  • Mass digital transformation (CHED-driven academic e-gov)

Common misconceptions

  • 'EA is a Visio diagram' - the diagram is the artefact, not the EA.
  • 'EA is centralised' - good EA is federated, with a small central team.
  • 'EA blocks innovation' - bad EA does; good EA documents the rails
  so teams can move fast without breaking the bank.
Mentor’s tip: EA is a layered alignment exercise, not a diagram archive. Four layers, four perspectives, one shared blueprint. The diagrams are how you communicate it; the alignment is the value.

Test yourself

Q1. Enterprise Architecture primarily aligns:
Q2. Which is NOT one of TOGAF ADM phases?
Q3. Zachman is best described as:
Q4. The correct order of TOGAF ADM starts with:
Q5. EA deliverables are useful because they:

Discussion

Loading…