PDB-01 3HNA006147-001 PDB01 自动化配电PC板 ABB
PDB-01 3HNA006147-001 PDB01 自动化配电PC板 ABB
PDB-01 3HNA006147-001 PDB01 自动化配电PC板 ABB
核心流程用例干系人与EA数据开发人员合作确定
为了支持核心流程,需要共享信息。概念的
结果信息交换的示例如下图所示。注意,在这个
在这种情况下,为决策提供的数据可能不是EA数据,而是分析结果
通过分析EA数据。
评估过程EA信息共享的概念模式
交换架构数据时,PES是交换规范。PES
提供了一种有效和标准的方法,以确保数据共享可以在工具集无关、方***无关的环境中进行。架构师对文档的使用
工具、电子表格或其他方式中的架构数据和信息,以及
通过
使用PES的基本共识。
91
物理交换规范
http://cio-nii.defense.gov/sites/dodaf20/PES.html[2011年3月3日下午3:37:04]
DM2 PES XML模式(XSD)为EA之间的数据交换提供了一种中性格式
数据和数据源包括:
1.EA数据库。
2.***部***来源数据库(如***部信息技术组合
存储库[DITPR])。
3.DoDAF和***部架构框架(MODAF)的统一概要
(UPDM)和基于SysML的统一标记语言(UML)工具。
4.其他信息技术(IT)和企业架构工具。
5.用于EA评估的建模和仿真工具,如AoA。
6.报告工具,如联合参谋长指令(CJCSI)主席或
***部指令(DoDI)提交。
7.系统工程工具。
8.其他联邦机构(如国土安全部
司法部。
9.联盟伙伴和北大西洋公约组织(北约)。
10.***部与之交换企业架构(EA)数据的其他组织
(例如,行业、州、国家***组织[非***组织])。
该角色如下图所示。
DM2在为数据交换提供中立模型中的作用说明
请注意,在上述任何特定社区中,可能存在数据交换格式
特别是该社区。一个特别重要的例子是UPDM SysML.XML
用于UML模型数据交换的元数据交换(XMI)格式。XMI提供了
在UML工具之间交换模型数据(包括图表数据)的中立方式。普遍的
DM2 PES到XMI的转换将允许UPDM SysML工具和其他工具互操作
以及***部EA中使用的数据源。
XSD
DM2 PES可扩展标记语言(XML)模式定义(XSD)是从DM2逻辑数据模型自动生成的。不添加或更改其他语义。
有四个DM2 PES XSD:
92
物理交换规范
http://cio-nii.defense.gov/sites/dodaf20/PES.html[2011年3月3日下午3:37:04]
1.IDEAS基金会,1.0版
2.DM2附加基础
3.分类标记(外部控制)
4.DM2交换数据
用于数据交换的DM2 PES XSD具有非常简单的结构,如图所示
在下面
用于交换的DM2 PES XSD的顶层结构
IdeasData部分包含具有元素的平面结构中的所有DM2域数据
使用标准XML文档和IDref链接在一起。图中显示了该平面结构的一部分
如下图所示。本节包含了所有要交换的DM2数据。
Core process use case stakeholders work with EA data developers to determine what
information needs to be shared when in order to support the core process. A notional
example of the resultant information exchange in shown in the figure below. Note that in this
case, the data presented for decisions may not be EA data, but, rather, the analysis results
from analyzing EA data.
Notional Pattern of EA Information Sharing for Assessment Processes
When exchanging architectural data, the PES is the specification for the exchange. The PES
provides an efficient and standard means to ensure that data sharing can occur in a toolsetagnostic, methodology-agnostic environment. Use of the by architects to document
architectural data and information in tools, through spreadsheets, or other means, and
deposit that data and organized information into federated repositories is facilitated by the
common understanding underlying the use of the PES.
91
Physical Exchange Specification
http://cio-nii.defense.gov/sites/dodaf20/PES.html[3/3/2011 3:37:04 PM]
The DM2 PES XML schema (XSD) provides a neutral format for data exchange between EA
data and data sources including:
1. EA databases.
2. DoD Authoritative Source Databases (e.g., DoD Information Technology Portfolio
Repository [DITPR]).
3. Unified Profile for DoDAF and Ministry of Defence Architecture Framework (MODAF)
(UPDM) and SysML-based Unified Markup Language (UML) Tools.
4. Other Information Technology (IT) and enterprise architecture Tools.
5. Modeling and Simulation Tools that are used in EA assessments, e.g., AoA’s.
6. Reporting Tools, e.g., for Chairman of the Joint Chief of Staff Instruction (CJCSI) or
Department of Defense Instruction (DoDI) submission.
7. Systems Engineering Tools.
8. Other Federal agencies (e.g., Department of Homeland Security (DHS), Department of
Justice (DoJ).
9. Coalition partners and North Atlantic Treaty Organization (NATO).
10. Other organizations with which DoD exchanges Enterprise Architecture (EA) data
(e.g., industry, States, National Government Organizations [NGO’s]).
This role is illustrated in the figure below.
Illustration of DM2 Role in Providing a Neutral Model for Data Exchange
Note that within any particular community above, there may be a data exchange format
particular to that community. A particularly important case is the UPDM-SysML XML
Metadata Interchange (XMI) format for data exchange of UML models. XMI provides a
neutral way to exchange model data, including diagram data, between UML tools. A universal
DM2 PES to XMI translation will allow UPDM-SysML tools to interoperate with the other tools
and data sources used in DoD EA.
XSD
The DM2 PES eXtensible Markup Language (XML) Schema Definitions (XSDs) is autogenerated from the DM2 Logical Data Model. No additional semantics are added or changed.
There are four DM2 PES XSD’s:
92
Physical Exchange Specification
http://cio-nii.defense.gov/sites/dodaf20/PES.html[3/3/2011 3:37:04 PM]
1. IDEAS Foundation, version 1.0
2. DM2 additional foundation
3. Classification marking (externally controlled)
4. DM2 exchange data
The DM2 PES XSD used for data exchange has a very simple structure as shown in the figure
below.
Top-Level Structure of a the DM2 PES XSD for Exchange
The IdeasData section contains all the DM2 domain data in a flat structure with elements
linked together using standard XML document IDref’s. A piece of this flat structure is shown
in the figure below. All of the DM2 data that is to be exchanged is contained in this section.
PDB-01 3HNA006147-001 PDB01 自动化配电PC板 ABB
PDB-01 3HNA006147-001 PDB01 自动化配电PC板 ABBPDB-01 3HNA006147-001 PDB01 自动化配电PC板 ABB