R&D Management 13 min read

Enterprise Architecture: Business Domain Design, Multi-Layer Architecture & Governance

This article outlines enterprise architecture fundamentals using a 'four horizontal, five vertical' framework, detailing business domain design principles, typical design methods for business, data, application, and technical architectures, and governance practices including principles, reviews, and asset management to align IT with business strategy.

Smart Sea Tide
Smart Sea Tide
Smart Sea Tide
Enterprise Architecture: Business Domain Design, Multi-Layer Architecture & Governance

Enterprise Architecture Overview

Enterprise architecture serves as a bridge between organizational strategy and IT, using structured methods to define business, data, application, and technology architectures, ensuring enterprise goals align with resources. A typical framework is the "four horizontal, five vertical" model: four horizontals — strategy layer (global planning), management layer (business-IT collaboration), design layer (solution design), implementation layer (concrete delivery); five verticals — business architecture, application architecture, data architecture, technology architecture, and architecture governance — forming a V-model that refines top-down and enforces bottom-up compliance.

Business Domain Design

Business domains represent divisions of the enterprise core business value chain, often corresponding to organizational departments such as planning management, financial management, and marketing management. Design follows five principles:

Strategy-driven: Business domains must support enterprise strategic goals, ensuring alignment with strategic direction.

Reflect business essence: Comprehensively cover business, clearly express business logic, avoid omissions.

Enable capability improvement: Support unified management and gap analysis of business capabilities, promoting business improvement.

Promote integration and efficiency: Break down departmental silos, support end-to-end process collaboration, improve overall efficiency.

Stability and continuous improvement: Planning is forward-looking, with regular review and optimization.

Typical Design Methods

Business Architecture Design

Business architecture design uses value stream analysis to identify enterprise-level and professional-level value streams, clarifying the value creation process. Based on value streams, business objects are designed, data standards defined, achieving process-data integration. A business capability framework is built, cataloging business capabilities to support componentization and servitization of business capabilities.

Data Architecture Design

Data architecture design defines data domains and data subjects, establishing conceptual, logical, and physical data models. It clarifies data distribution and flow rules, ensuring single-source-of-truth sharing and cross-system information consistency.

Application Architecture Design

Application architecture design maps application domains from business domains, plans application modules and functions, and defines application interaction relationships. It adopts layered decoupling and service-oriented architecture to enable flexible composition and rapid response of applications.

Technology Architecture Design

Technology architecture design defines technology domains and technology capabilities, selecting appropriate technology platforms and components. It plans system deployment architecture to ensure system reliability, scalability, and security.

Architecture Governance

Architecture governance is key to ensuring enterprise architecture implementation, comprising:

Architecture principles and standards: Formulate architecture design principles, standards, and specifications to guide architecture design.

Architecture review and compliance checks: Conduct regular reviews of architecture designs to ensure adherence to architecture standards.

Architecture asset operations: Manage architecture assets such as architecture blueprints, reference architectures, and design templates to support continuous architecture optimization.

Enterprise architecture and business domain design is a continuous iterative process that must combine enterprise strategy, business requirements, and external environmental changes to continuously optimize and adjust architecture, supporting sustainable enterprise development.

The article includes numerous architectural diagrams illustrating the frameworks and models described above.

Architecture diagram 1
Architecture diagram 1
Architecture diagram 2
Architecture diagram 2
Architecture diagram 3
Architecture diagram 3
Architecture diagram 4
Architecture diagram 4
Architecture diagram 5
Architecture diagram 5
Architecture diagram 6
Architecture diagram 6
Architecture diagram 7
Architecture diagram 7
Architecture diagram 8
Architecture diagram 8
Architecture diagram 9
Architecture diagram 9
Architecture diagram 10
Architecture diagram 10
Architecture diagram 11
Architecture diagram 11
Architecture diagram 12
Architecture diagram 12
Architecture diagram 13
Architecture diagram 13
Architecture diagram 14
Architecture diagram 14
Architecture diagram 15
Architecture diagram 15
Architecture diagram 16
Architecture diagram 16
Architecture diagram 17
Architecture diagram 17
Architecture diagram 18
Architecture diagram 18
Architecture diagram 19
Architecture diagram 19
Architecture diagram 20
Architecture diagram 20
Architecture diagram 21
Architecture diagram 21
Architecture diagram 22
Architecture diagram 22
Architecture diagram 23
Architecture diagram 23
Architecture diagram 24
Architecture diagram 24
Architecture diagram 25
Architecture diagram 25
Architecture diagram 26
Architecture diagram 26
Architecture diagram 27
Architecture diagram 27
Architecture diagram 28
Architecture diagram 28
Architecture diagram 29
Architecture diagram 29
Architecture diagram 30
Architecture diagram 30
Architecture diagram 31
Architecture diagram 31
Architecture diagram 32
Architecture diagram 32
Architecture diagram 33
Architecture diagram 33
Architecture diagram 34
Architecture diagram 34
Architecture diagram 35
Architecture diagram 35
Architecture diagram 36
Architecture diagram 36
Architecture diagram 37
Architecture diagram 37
Architecture diagram 38
Architecture diagram 38
Architecture diagram 39
Architecture diagram 39
Architecture diagram 40
Architecture diagram 40
Architecture diagram 41
Architecture diagram 41
Architecture diagram 42
Architecture diagram 42
Architecture diagram 43
Architecture diagram 43
Architecture diagram 44
Architecture diagram 44
Architecture diagram 45
Architecture diagram 45
Architecture diagram 46
Architecture diagram 46
Architecture diagram 47
Architecture diagram 47
Architecture diagram 48
Architecture diagram 48
Architecture diagram 49
Architecture diagram 49
Architecture diagram 50
Architecture diagram 50
Architecture diagram 51
Architecture diagram 51
Architecture diagram 52
Architecture diagram 52
Architecture diagram 53
Architecture diagram 53
Architecture diagram 54
Architecture diagram 54
Architecture diagram 55
Architecture diagram 55
Architecture diagram 56
Architecture diagram 56
Architecture diagram 57
Architecture diagram 57
Architecture diagram 58
Architecture diagram 58
Architecture diagram 59
Architecture diagram 59
Architecture diagram 60
Architecture diagram 60
Architecture diagram 61
Architecture diagram 61
Architecture diagram 62
Architecture diagram 62
Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

technical architecturearchitecture governanceapplication architecturedata architectureenterprise architecturearchitecture frameworkbusiness domain design
Smart Sea Tide
Written by

Smart Sea Tide

Sharing cutting‑edge big data and AI technologies, with occasional lifestyle insights.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.