Auto-sync: 2026-04-29 04:03
This commit is contained in:
38
wiki/concepts/EA-SA-TA-Framework.md
Normal file
38
wiki/concepts/EA-SA-TA-Framework.md
Normal file
@@ -0,0 +1,38 @@
|
||||
---
|
||||
title: "EA-SA-TA Framework"
|
||||
type: concept
|
||||
tags: [Enterprise-Architecture, Solution-Architecture, Technical-Architecture, Cloud-Governance]
|
||||
sources: ["ctp-topic-23-introduction-to-the-technical-architecture-team-and-function"]
|
||||
last_updated: 2026-05-11
|
||||
---
|
||||
|
||||
## Definition
|
||||
EA-SA-TA Framework 是 OpenText 云转型办公室采用的三层架构职能分工体系,通过明确的职责边界实现从业务战略到技术实施的完整覆盖。
|
||||
|
||||
## Layer Breakdown
|
||||
|
||||
### Enterprise Architecture (EA) — 企业架构
|
||||
- **定位**:最顶层,对接业务战略
|
||||
- **职责**:将业务目标转化为技术原则和标准,确保技术投资与商业战略一致
|
||||
- **核心问题**:我们应该在哪些技术领域进行投资?如何与技术战略保持一致?
|
||||
|
||||
### Solution Architecture (SA) — 方案架构
|
||||
- **定位**:中间层,连接 EA 与 TA
|
||||
- **职责**:专注于特定项目或服务的优化实施,确保系统组件间的高效协作
|
||||
- **核心问题**:针对特定项目,什么是最佳的技术解决方案?
|
||||
|
||||
### Technical Architecture (TA) — 技术架构
|
||||
- **定位**:最底层,贴近技术实施
|
||||
- **职责**:负责具体基础设施的设计、实施治理以及技术路线图的维护
|
||||
- **核心问题**:如何实施和维护技术基础设施?技术路线图如何规划?
|
||||
|
||||
## Design Rationale(from Martin Nash)
|
||||
- 大型组织(PSTC + IT 合并至 CIO)需要清晰的架构分工
|
||||
- 三层分工使技术治理从"救火式"转向"主动规划"
|
||||
- EA 负责战略方向,SA 负责方案优化,TA 负责落地执行,分工明确减少职责重叠
|
||||
|
||||
## Connections
|
||||
- [[Cloud-First-Policy]] — EA 层制定的云优先技术原则
|
||||
- [[AWS-Enterprise-Landing-Zone]] — TA 层维护的标准化基础设施
|
||||
- [[Architecture-Roadmap]] — TA 层制定的 12-24 个月路线图
|
||||
- [[Cloud-Transformation-Programme]] — 三层架构体系的组织背景
|
||||
Reference in New Issue
Block a user