Mastering Enterprise Architecture: A Practical Guide to TOGAF and the 4A Framework

Effective Enterprise Architecture and TOGAF Overview

Effective Enterprise Architecture (EA) draws a beautiful blueprint that is decisive for a company's survival and success, serving as an indispensable means for gaining competitive advantage through IT. TOGAF, the most widely applied EA framework, provides a complete and continuously optimized knowledge system to support efficient EA implementation.

01 Reflections on Architecture

Question: What problems arise if no architectural planning is performed?

System “chimney” construction leads to blurred system boundaries, frequent disputes, duplicate development, inconsistent standards, lack of integration, and hindered innovation.

The four main architectures in EA—business, data, application, and technology—focus on different aspects but are interrelated and support each other, forming the overall enterprise architecture. In a middle‑platform construction, data architecture is core; planning and designing enterprise data resources enables data sharing, governance, and increased value and efficiency.

A clear enterprise architecture ensures smooth business processes, reasonable IT support, and orderly construction steps. It serves as a crucial basis for project decisions and future development.

Data analysts should understand the business, maintain a global view, choose appropriate technologies, solve key problems, and propose implementable solutions.

TOGAF Architecture Model

Why do it – strategic goals, business motivations

What to do – business functions, capabilities

Who does it – organizational structure, business roles

How to do it – business processes, rules

Data used – business data

Applications used – application systems

Technology used – technical infrastructure

02 Enterprise Architecture 4A Model

Business Architecture: strategy, value chain, end‑to‑end, business processes, business components, top‑down decomposition.

Application Architecture: system construction, integration, middle platform, bottom‑up abstraction.

Technology Architecture: technology selection, frameworks, PaaS platforms, cloud‑native, DevOps, microservices, containerization, deployment architecture.

Data Architecture: data standards, acquisition, processing, lake, governance, sharing services, security, quality.

Relationship among the 4A architectures is illustrated below:

03 What Is Business Architecture?

Business architecture defines business strategy, governance, organization, and key processes. It is the core of EA, linking corporate strategy to implementation capability and serving as a prerequisite for other architecture domains.

Its main goal is to analyze the current business state, identify existing capabilities and issues, propose improvement requirements, and design the target business architecture based on the enterprise’s strategic vision.

When mapping the AS‑IS business architecture, the 5W1H questionnaire is used to gather information, combined with management documents, and components are collected according to business component aggregation principles. Components are then linked to form process diagrams.

Purpose: Based on the enterprise strategy, analyze business processes along the value chain, identify upstream/downstream dependencies, and describe the platform or product implementation from a business and product perspective.

Design Steps:

Identify strategy, conduct business department visits, questionnaire surveys.

Consider external factors: macro background, industry space, competition, and upstream/downstream industry chain.

Consider internal factors: business model, technical barriers, and resource investment.

How to draw a business architecture diagram:

1. Map the user operation scenario and list functional modules.

2. Form a functional matrix.

3. Perform horizontal and vertical layering.

Another reference for business architecture diagram:

04 What Is Application Architecture?

Application architecture provides a blueprint for deploying individual application systems, their interactions, and their relationship with core business processes. Its main goal is to design the target application architecture based on current application needs, business architecture data flows, and existing IT landscape.

Purpose: Identify which application systems support business and data processing needs, enabling the transformation from business to IT.

Design Steps:

Based on the business architecture diagram, map business to IT, identify applications and components.

Optimize applications and components: split where needed, aggregate where appropriate.

Design relationships among applications, business functions, processes, and data.

Design application integration, interaction, and development.

How to draw an application architecture diagram:

05 What Is Technology Architecture?

Technology architecture describes the logical software and hardware capabilities needed to support business, data, and application services, including infrastructure, middleware, networks, communication, processes, and standards. Its goal is to design the target technology architecture based on the current state, standards, and requirements from business, application, and data architectures.

Purpose: Support the technical components and selections required by application systems.

Design Steps:

Analyze technical support requirements based on the application architecture.

Select technologies: development architecture, products, tech stack, development and runtime platforms.

Assess technical impact: cost, difficulty, planning, governance.

How to draw a technology architecture diagram:

06 What Is Data Architecture?

Data architecture describes the structure of an enterprise’s logical and physical data assets and data management resources. Its main goal is to design the target data architecture based on current data needs and data flows identified in the business architecture.

Purpose: Describe data sources, asset management, governance, and open sharing.

Design Steps:

Connect to business, analyze data requirements, identify data types, and collect data.

Design data models: conceptual (business domains), logical (ER), physical (tables, fields).

Implement data governance, security compliance, and quality management.

Enable data sharing and openness to support business decisions and innovation.

How to draw a data architecture diagram: