One Diagram That Reveals the Full Software Architecture Family Tree

Introduction

Many beginners feel overwhelmed by the term “software architecture.” The article promises a quick, five‑minute understanding using a family‑tree metaphor.

Software Architecture Family Tree

软件架构家族
│
├── 第一代老祖宗
│   └── 软件架构（总称）
│
├── 第二代掌门人（按层次分）
│   ├── 企业架构 EA
│   │   ├── 业务架构
│   │   └── IT架构
│   └── 应用架构
│       ├── 逻辑架构
│       └── 物理架构
│
└── 第三代高手（按领域分）
    ├── 系统架构
    ├── 技术架构
    ├── 数据架构
    ├── 安全架构
    └── 云架构

The three generations solve different problems.

First Generation – The Ancestor

Software Architecture is the overarching term. Its official definition is “the fundamental structure of a software system and the principles and guidelines for creating that structure.” In plain language, it is the “skeletal framework” you must decide before building a system, similar to planning a house’s type, floors, materials, and layout.

Second Generation – Layer‑Based Architectures

Enterprise Architecture (EA)

Highest‑level architecture focusing on the enterprise’s IT blueprint, answering questions such as which systems will be used in the next three years, how they relate, how data flows, and how IT investment is allocated. Practitioners are called Enterprise Architects. Typical frameworks: TOGAF, Zachman.

Application Architecture

Mid‑level architecture describing the structure of a single application system. It splits into:

Logical architecture : functional view from a business perspective.

Physical architecture : technical view of deployment and runtime.

Typical questions include required modules for an e‑commerce system, module communication, and technology choices.

Third Generation – Domain‑Specific Architectures

System Architecture

Focuses on the composition and collaboration of the whole system. Example: a smart‑city system with traffic management, environmental monitoring, and emergency command modules, and how they integrate.

Technical Architecture

Focuses on the technology stack used to implement the system, e.g., choosing Java vs. Go, MySQL vs. MongoDB, Kafka vs. RabbitMQ.

Data Architecture

Focuses on how data is stored, moved, and used. Includes data model design, data‑warehouse construction, data‑governance standards, and big‑data platform architecture.

Security Architecture

Focuses on protecting the system, covering identity authentication, access control, data encryption, and security auditing.

Cloud Architecture

With the rise of cloud computing, this architecture addresses building systems on the cloud, such as choosing AWS vs. Alibaba Cloud, public vs. private cloud, and cloud‑resource planning.

Architectural Views – The 4+1 Model

Logical view : answers “What does the system do?” – audience: users, business analysts.

Development view : answers “How is the code organized?” – audience: developers.

Process view : answers “How does the system run?” – audience: integration engineers.

Physical view : answers “Where is the system deployed?” – audience: operations staff.

Scenario view : answers “How is the system used?” – audience: all stakeholders.

Summary Table of Architecture Types

Enterprise Architecture – focus: enterprise IT blueprint – level: high – typical outputs: enterprise architecture diagrams, roadmaps.

Business Architecture – focus: business processes and capabilities – level: high – typical outputs: capability maps.

Application Architecture – focus: structure of a single system – level: medium – typical outputs: application architecture diagrams.

Technical Architecture – focus: technology selection and implementation – level: medium – typical outputs: technical solution documents.

Data Architecture – focus: data storage, flow, and usage – level: medium – typical outputs: data models.

Security Architecture – focus: system security protection – level: low – typical outputs: security plans.

Cloud Architecture – focus: cloud resource planning – level: low – typical outputs: cloud architecture diagrams.

Remember this “family tree,” and you will have a global view of software architecture, instantly recognizing which layer is being discussed.