|
|
|
| Engineering Guide: Enterprise Architecture Design |
|
Zu Tao,Dragon Fruit Technology |
Enterprise architecture design is a complex and challenging task that involves multiple layers of architecture: business architecture, data architecture, application architecture, and technology architecture.
Before the architecture design, the corresponding architecture requirement analysis should be carried out. After the architecture design, the architecture governance, architecture application and evaluation should be carried out based on the architecture.
There are multiple roles and many artifacts involved. For clarity. The adoption of iSpace establishes the working model of the enterprise architect, which involves three aspects: |
|
Workflow
Role
workpiece |
| The details are as follows:
|
| Step 1: Process |
| 1.1 Process Diagram |
 |
| 1.2 Activity List |
| The following is the activity list generated based on the workflow model, and work plans can be made based on the activity list. |
| Task |
Role |
input |
export |
Planned completion date
|
Actual completion date |
Current state |
Architecture request
|
User/developer representative |
|
Architecture request |
|
|
|
| Architecture requirement analysis |
User/developer representative |
Architecture request |
Architectural requirement model |
|
|
|
| Determine architecture quality criteria |
Enterprise architect |
Architectural requirement model |
Architecture quality model |
|
|
|
| Business architecture design |
Enterprise architect |
Architecture Quality model, business architecture
|
Data architecture design, architecture governance plan
|
|
|
|
| Application architecture design |
Enterprise architect |
Data architecture design, application architecture |
Technical architecture design, architecture governance plan |
|
|
|
| Technical architecture design |
Enterprise architect |
Application architecture design, technology architecture |
Architecture governance plan |
|
|
|
| Data architecture design |
Enterprise architect |
Business architecture design, data architecture |
Application architecture design, architecture governance plan |
|
|
|
| Architecture governance plan |
Platform team |
Business architecture design, Data architecture design, Application architecture design, Technology architecture design |
Governance plan |
|
|
|
| Formulate technical specifications |
Platform team |
Governance plan |
Technical specifications, build the platform |
|
|
|
| Build platform |
Platform team |
Platform, develop technical specifications |
|
|
|
|
| Application item |
Application construction team |
Technical specification |
Platform, application feedback |
|
|
|
| Architecture reconstruction |
Enterprise architect |
Structure evaluation report |
Technical architecture
|
|
|
|
| Architecture application evaluation |
Enterprise architect |
Application feedback |
Structure evaluation report |
|
|
|
|
| For the level 2 workflow diagram in the activity list, expand as follows: |
|
Architecture requirement analysis |
 |
| Determine architecture quality criteria |
 |
| Business architecture design |
 |
| Application architecture design |
 |
| Technical architecture design |
 |
| Data architecture design |
 |
| Architecture governance plan |
 |
| Formulate technical specifications |
 |
| Architecture reconstruction |
 |
| Architecture application evaluation |
 |
| 2.Person |
| 2.1 Role Diagram |
 |
| 2.2 Role List |
| The following is the role list generated based on the role model. You can make a work plan based on the role list. |
| 人员/角色 |
任务 |
计划完成日期 |
实际完成日期 |
当前状态 |
| 用户/开发代表 |
架构请求 |
|
|
|
| 企业架构师 |
架构需求分析 |
|
|
|
| 确定架构质量标准 |
|
|
|
| 业务架构设计 |
|
|
|
| 应用架构设计 |
|
|
|
| 技术架构设计 |
|
|
|
| 数据架构设计 |
|
|
|
| 架构治理计划 |
|
|
|
| 制定技术规范 |
|
|
|
| 架构重构 |
|
|
|
| 架构应用评估 |
|
|
|
| Platform team |
构建平台 |
|
|
|
| 应用建设团队 |
应用项目 |
|
|
|
| IT主管 |
提出请求 |
|
|
|
| 编写集成需求说明书 |
|
|
|
| 质量求证 |
|
|
|
| 建立质量模型 |
|
|
|
| 业务代表 |
业务反馈 |
|
|
|
| 数据反馈 |
|
|
|
| 应用反馈 |
|
|
|
| 业务愿景 |
|
|
|
| 技术代表 |
技术反馈 |
|
|
|
| 技术愿景 |
|
|
|
| 业务架构师 |
业务调查 |
|
|
|
| 业务建模 |
|
|
|
| 业务框架设计 |
|
|
|
| 业务组件设计 |
|
|
|
| 业务确认 |
|
|
|
| IT团队 |
开发影响分析 |
|
|
|
| 业务实现 |
|
|
|
| 数据使用者 |
提出治理需求 |
|
|
|
| 数据应用 |
|
|
|
| 数据架构师 |
数据调查 |
|
|
|
| 数据建模 |
|
|
|
| 数据框架设计 |
|
|
|
| 搭建数据平台 |
|
|
|
| 数据评估 |
|
|
|
| 数据维护者 |
应用现状反馈 |
|
|
|
| 建立基础数据 |
|
|
|
| 应用使用者 |
提出治理需求 |
|
|
|
| 系统使用 |
|
|
|
| 应用架构师 |
应用调查 |
|
|
|
| 系统建模 |
|
|
|
| 应用架构设计 |
|
|
|
| 搭建应用平台 |
|
|
|
| 应用架构评估 |
|
|
|
| 应用运维者 |
系统现状反馈 |
|
|
|
| 构建应用基础 |
|
|
|
| 应用开发者 |
提出开发需求 |
|
|
|
| 应用开发 |
|
|
|
| 技术架构师 |
技术调查 |
|
|
|
| 开发资源流程 |
|
|
|
| 技术框架设计 |
|
|
|
| 设计技术平台 |
|
|
|
| 技术架构评估 |
|
|
|
| 平台开发者 |
技术现状反馈 |
|
|
|
| 构建平台 |
|
|
|
| 用户方 |
应用影响分析 |
|
|
|
| 架构师 |
确定治理目标 |
|
|
|
| IT团队 |
开发影响分析 |
|
|
|
| 应用开发 |
应用开发 |
|
|
|
| 应用构建 |
|
|
|
| 架构师 |
规范定位 |
|
|
|
| 确定规范范围 |
|
|
|
| 制定数据规范 |
|
|
|
| 制定接口规范 |
|
|
|
| 制定界面规范 |
|
|
|
| 制定功能规范 |
|
|
|
| 规范开发者 |
样例开发 |
|
|
|
| 应用开发者 |
系统逆向 |
|
|
|
| 应用开发 |
|
|
|
| 架构开发者 |
重构实现 |
|
|
|
| 用户 |
应用反馈 |
|
|
|
| 架构评估者 |
确定评估指标 |
|
|
|
| 问题收集 |
|
|
|
| 规范性评估 |
|
|
|
| 应用质量评估 |
|
|
|
| 质量建模 |
|
|
|
| 编写质量报告 |
|
|
|
| 开发者 |
开发反馈 |
|
|
|
| 运维者 |
运维反馈 |
|
|
|
|
| 3. Workpiece |
| 3.1 Job Diagram |
 |
| 3.2
工件列表 |
| 如下是基于角色模型生成的角色列表，可以基于角色列表制定工作计划。 |
| 工件 |
负责人 |
计划完成日期 |
实际完成日期 |
当前状态 |
| 架构需求模型 |
|
|
|
|
| 架构质量模型 |
|
|
|
|
|
架构模型 |
|
|
|
|
| 业务架构模型 |
|
|
|
|
| 数据架构模型 |
|
|
|
|
| 应用架构模型 |
|
|
|
|
| 技术架构模型 |
|
|
|
|
| 业务组件目录 |
|
|
|
|
| 数据组件目录 |
|
|
|
|
| 数据对象目录 |
|
|
|
|
| 应用组件目录 |
|
|
|
|
| 技术组件陌路 |
|
|
|
|
| 架构原型 |
|
|
|
|
|
技术规范 |
|
|
|
|
| 架构质量报告 |
|
|
|
|
|
|
更详细的信息请参考《能力模型：企业架构师》
|
|
具体的操作步骤，请看下面的操作视频： |
http://video.uml.com.cn/video/broVideoEA.asp?vidID=3443 |
欢迎联系：客户经理
联系方式：010-62670969
邮件：teacher@uml.net.cn |
| |
|
