GDC801A 3BHE024747R0101 3BHE024748P201 制动控制主板

GDC801A 3BHE024747R0101 3BHE024748P201 制动控制主板 

建立并定义用于描述和讨论的受限词汇
DoDAF模型（以前称为“产品”）及其在6个核心流程中的使用
2.指定联邦EA数据交换的语义和格式
之间：体系结构开发和分析工具与体系结构数据库
国防部企业架构（EA）利益共同体（COI）和
其他权威数据来源
3.支持EA数据的发现和可理解性：
使用DM2信息类别发现EA数据
使用DM2的语义增强EA数据的可理解性
语言可追溯性（别名）
4.为架构描述中的语义精度提供基础，以支持
支持核心的异构体系结构描述、集成和分析
决策过程。
DM2定义了体系结构数据元素，并支持集成和联合
架构描述。它为语义（即理解）奠定了基础
架构描述内部和之间的一致性。通过这种方式，DM2支持
JCA、组件和联邦之间架构信息的交换和重用
以及联盟伙伴，从而促进对
过程和系统的互操作性。随着DM2的成熟，以满足持续的数据
流程所有者、决策者、架构师和新技术的要求
更全面地支持体系结构数据需求的资源，已发布
以一致可理解的方式，并将使发现、共享和共享更加容易，
以及跨组织边界重用架构数据。
为了便于在数据层使用信息，DoDAF描述了一组用于
通过图形、表格或文本方式可视化数据。这些观点涉及：
利益相关者对生成架构描述的要求。
DM2是什么，在哪里
出身背景
建筑发展
元模型
概念的
必然的
PES
思想基金会
本体论
观点和模型
展示技巧
配置管理
概述
缩略语列表和词汇表
术语
网站地图
档案
国防部
22
DM2-DoDAF元模型
http://cio-nii.defense.gov/sites/dodaf20/DM2.html[2011年3月3日下午3:34:01]
根据标准数据建模约定，DM2有几个级别，如
如下图所示。
DM2的三个级别
其中每一项对于部门流程的特定查看者都很重要。
1.概念级或概念数据模型（CDM）定义数据
从中以非技术术语创建架构描述的构造，
使各级主管和管理人员能够了解
架构描述。
2.逻辑数据模型（LDM）向
CDM，必要时，将关系澄清为明确的用途
释义
3.物理交换规范（PES）由LDM和一般数据组成
指定类型并添加实现属性（例如，源、日期），然后
生成为XSD。
DM2由以下数据项组成：
LDM和PES可从国防部元数据注册中心（MDR）获取
命名空间。ARCH名称空间服务于国防部企业体系结构利益共同体（COI）。国防部
MDR是所有国防部元数据的权威来源。DoDAF网站也包含CDM
如LDM、PES和本体文档。
23
DM2-DoDAF元模型
http://cio-nii.defense.gov/sites/dodaf20/DM2.html[2011年3月3日下午3:34:01]
转到页面顶部↑
隐私政策|网络政策124;联系人
24
DM2——DoDAF概念数据模型
http://cio-nii.defense.gov/sites/dodaf20/conceptual.html[2011年3月3日下午3:36:57]
首页DoDAF-DM2工作组DoDAF期刊国防部元数据注册想法链接
DM2-DoDAF元模型
DM2概念数据模型
与普遍核心和Zachman框架疑问句的关系
DM2主要要素与国防部六大核心流程的关系
DM2基金会概述
CDM定义了涉及高层数据结构的概念，架构
创建描述，使各级主管和经理能够理解
架构描述的数据基础。关键概念如下：
1.活动：不特定于单个组织、武器系统或个人的工作
将输入（资源）转换为输出（资源）或更改其状态。
2.资源：数据、信息、执行者、物资或人员类型
生产或消费的。
物资：感兴趣的设备、仪器或用品，无
用于行政或作战目的的区别。
信息：感兴趣的事物被具体化的状态
媒介或形式——并传达或接收。
数据：以形式化的方式表示信息，适用于
人类或通过

GDC801A 3BHE024747R0101 3BHE024748P201 制动控制主板 

GDC801A 3BHE024747R0101 3BHE024748P201 制动控制主板 

 Establish and define the constrained vocabulary for description and discourse about
DoDAF models (formerly “products”) and their usage in the 6 core processes
2. Specify the semantics and format for federated EA data exchange
between:architecture development and analysis tools and architecture databases
across the DoD Enterprise Architecture (EA) Community of Interest (COI) and with
other authoritative data sources
3. Support discovery and understandability of EA data:
Discovery of EA data using DM2 categories of information
Understandability of EA data using DM2’s precise semantics augmented with
linguistic traceability (aliases)
4. Provide a basis for semantic precision in architectural descriptions to support
heterogeneous architectural description integration and analysis in support of core
process decision making.
The DM2 defines architectural data elements and enables the integration and federation of
Architectural Descriptions. It establishes a basis for semantic (i.e., understanding)
consistency within and across Architectural Descriptions. In this manner, the DM2 supports
the exchange and reuse of architectural information among JCAs, Components, and Federal
and Coalition partners, thus facilitating the understanding and implementation of
interoperability of processes and systems. As the DM2 matures to meet the ongoing data
requirements of process owners, decision makers, architects, and new technologies, it will to
a resource that more completely supports the requirements for architectural data, published
in a consistently understandable way, and will enable greater ease for discovering, sharing,
and reusing architectural data across organizational boundaries.
To facilitate the use of information at the data layer, the DoDAF describes a set of models for
visualizing data through graphic, tabular, or textual means. These views relate to
stakeholder requirements for producing an Architectural Description.
What and Where is the DM2
Background
Architecture Development
Meta-Model
Conceptual
Logical
PES
IDEAS Foundation
Ontology
Viewpoints & Models
Presentation Techniques
Configuration Management
Overview
Acronyms List and Glossary
of Terms
Site Map
Archives
Department of Defense
22
DM2 - DoDAF Meta-Model
http://cio-nii.defense.gov/sites/dodaf20/DM2.html[3/3/2011 3:34:01 PM]
In accordance with standard data modeling conventions, the DM2 has several levels, as
shown in the figure below.
DM2's Three Levels
Each of these is important to a particular viewer of Departmental processes.
1. The conceptual level or Conceptual Data Model (CDM) defines the high-level data
constructs from which Architectural Descriptions are created in non-technical terms,
so that executives and managers at all levels can understand the data basis of
Architectural Description.
2. The Logical Data Model (LDM) adds technical information, such as attributes to the
CDM and, when necessary, clarifies relationships into an unambiguous usage
definition.
3. The Physical Exchange Specification (PES) consists of the LDM with general data
types specified and implementation attributes (e.g., source, date) added, and then
generated as an XSD.
The DM2 consists of the following data items:
The LDM and PES can be obtained from the DoD Meta Data Registry (MDR) ARCH
namespace. The ARCH namespace serves the DoD EA Community of Interest (COI). The DoD
MDR is the authoritative source for all DoD metadata. This DoDAF site contains CDM as well
as LDM, PES, and ontology documentation.
23
DM2 - DoDAF Meta-Model
http://cio-nii.defense.gov/sites/dodaf20/DM2.html[3/3/2011 3:34:01 PM]
Go to top of page ↑
Privacy Policy | Web Policy | Contacts
24
DM2 - The DoDAF Conceptual Data Model
http://cio-nii.defense.gov/sites/dodaf20/conceptual.html[3/3/2011 3:36:57 PM]
Home DoDAF-DM2 WG DoDAF Journal DoD Meta Data Registry IDEAS Links
DM2 - DoDAF Meta-Model
The DM2 Conceptual Data Model
Relationship to Universal Core and the Zachman Framework interrogatives
Relationship of DM2 Principal Elements to DoD's Six Core Processes
Overview of The DM2 Foundation
The CDM defines concepts involving high-level data constructs from which Architectural
Descriptions are created, enabling executives and managers at all levels to understand the
data basis of Architectural Description. The key concepts are as follows:
1. Activity: Work, not specific to a single organization, weapon system or individual that
transforms inputs (Resources) into outputs (Resources) or changes their state.
2. Resource: Data, Information, Performers, Materiel, or Personnel Types that are
produced or consumed.
Materiel: Equipment, apparatus or supplies that are of interest, without
distinction as to its application for administrative or combat purposes.
Information: The state of a something of interest that is materialized -- in any
medium or form -- and communicated or received.
Data: Representation of information in a formalized manner suitable for
communication, interpretation, or processing by humans or by automatic
means. Examples could be whole models, packages, entities, attributes,
classes, domain values, enumeration values, records, tables, rows,
columns, and fields.
Architectural Description: Information describing an architecture such
as an OV-5b Operational Activity Model.
Performer: Any entity - human, automated, or any aggregation of human
and/or automated - that performs an activity and provides a capability.
Organization: A specific real-world assemblage of people and other
resources organized for an on-going purpose.
System: A functionally, physically, and/or behaviorally related group of
regularly interacting or interdependent elements.
Person Type: A category of persons defined by the role or roles they
share that are relevant to an architecture.
Service: A mechanism to enable access to a set of one or more
capabilities, where the access is provided using a prescribed interface
and is exercised consistent with constraints and policies as specified by
the service description. The mechanism is a Performer. The capabilities
accessed are Resources -- Information, Data, Materiel, Performers, and
Geo-political Extents.
3. Capability: The ability to achieve a Desired Effect under specified (performance)
standards and conditions through combinations of ways and means (activities and
resources) to perform a set of activities.
4. Condition: The state of an environment or situation in which a Performer performs.
5. Desired Effect: A desired state of a Resource.
6. Measure: The magnitude of some attribute of an individual.
7. Measure Type: A category of Measures.