Chapter 1: Foundations of Enterprise Architecture

Chapter 1: Foundations of Enterprise Architecture

Introduction

This chapter covers the basic concepts of enterprise architecture (EA), emphasizing the need for a solid foundation before any business initiative can advance.

It begins with a modern definition of EA and outlines the essential techniques for handling enterprise complexity.

The evolving role and responsibilities of enterprise architects in leading successful modernization programs are also discussed.

Definition of Enterprise Architecture

EA in information technology defines a macro‑level IT architecture for the enterprise, focusing on mapping IT functions to business needs through governance.

Traditional EA uses a city‑planning metaphor to visualize and communicate the architecture, which this book adopts to illustrate abstract concepts.

EA describes relationships, logical flows, business processes, activities, functions, data, applications, underlying technologies, and supporting tools.

The three core aspects of EA—vision, processes, and plans—are driven by enterprise‑level business requirements, capabilities, and demands.

EA progresses through five maturity stages: Initial, Baseline, Target, Integrated, and Optimized. Modernization initiatives must consider each stage individually and collectively.

Common reference models include the Business Reference Model (BRM), Component Reference Model (CRM), Technical Reference Model (TRM), Data Reference Model (DRM), and Performance Reference Model (PRM). These models cover capabilities, functions, standards, systems, data descriptions, and quality metrics, and are used by methods such as TOGAF, Zachman, and FEA.

Managing Enterprise Complexity

Enterprise environments can be highly complex, spanning multiple layers of systems, technologies, tools, and processes. Architects manage this complexity through partitioning, simplification, and iteration.

Partitioning (or segmentation) breaks a large system into smaller, manageable groups—for example, dividing a network into WAN and LAN segments.

Simplification reduces the number of components, such as consolidating servers, to lower operational overhead.

Iteration involves executing activities in small, incremental steps, allowing rapid feedback, cheap failure, and continuous improvement.

Enterprise Solution Cost

Modernization incurs both known and hidden costs. While known costs are easier to manage, hidden costs—like performance penalties, SLA fines, and downtime—pose greater challenges.

Architects can lower solution costs without sacrificing quality by applying systematic trade‑offs, collaborative input from business and technical teams, and agile processes.

Developing a Bill of Materials (BOM) after high‑level design helps control budgets, and architects must ensure that no BOM is formalized without approved architecture.

Infrastructure components such as data centers, servers, mobile BI, big data platforms, and cloud services affect cost but also enable feasible enterprise solutions.

Service availability and performance directly impact SLA penalties; automated SLA monitoring can identify low‑availability events and enforce contractual penalties.

Enterprise Modernization Approach

Enterprise modernization is a long journey from chaos to harmony, focusing primarily on enterprise IT systems—including business processes, data, applications, infrastructure, and service delivery.

Both top‑down and bottom‑up approaches can be applied, but integration is critical due to inter‑dependencies across domains.

Architects translate business strategies into detailed roadmaps, outlining outcomes, timelines, and cost estimates, while assessing feasibility, risks, assumptions, constraints, and dependencies.

Requirement collection is delegated to domain experts, program architects, and business analysts, with architects coordinating the effort and prioritizing requirements based on strategic and financial criteria.