DSBB188 3BSE005004R1 DSBB 188 DCS电源总线

DSBB188 3BSE005004R1 DSBB 188 DCS电源总线 

DSBB188 3BSE005004R1 DSBB 188 DCS电源总线 

DSBB188 3BSE005004R1 DSBB 188 DCS电源总线 

位置：空间中的一个点或范围，可以在物理上或逻辑上引用。
9.指南：旨在领导或指导执行的权威声明
行动。
规则：支配行为的原则或条件；规定的指南
行为或行动。
协议：双方就条款和
上述各方参与的活动条件。
标准：记录普遍接受的正式协议
产品、过程、程序、政策的规范或标准，
系统和/或人员。
10.项目：为创造资源或预期效果而进行的临时努力。
11.愿景：描述企业未来状态的目的，不考虑
如何实现这一目标；未来将是什么样子或可能是什么样子的心理图像。
技能：从知识、实践、才能等方面获得的能力
好的。
DoDAF-DM2数据字典中确定并定义了其他CDM概念。
CDM还以相对非技术性的方式描述了数据结构之间的关系
以及易于理解的术语。下图是清洁发展机制的图示。
DM2概念数据模型（DIV-1）图
转到页面顶部↑
隐私政策|网络政策124;联系人
26
DM2——DoDAF概念数据模型
http://cio-nii.defense.gov/sites/dodaf20/conceptual2.html[2011年3月3日下午3:46:36]
首页DoDAF-DM2工作组DoDAF期刊国防部元数据注册想法链接
DM2-DoDAF元模型
DM2 CDM与通用核心和Zachman框架的关系
疑问词
DM2主要要素与国防部六大核心流程的关系
DM2本体基础概述
DM2 CDM涉及通用核心，而Zachman框架询问：
如下图所示。明确地：
1.数据描述-什么（我们推广到除数据之外的其他资源）
2.功能描述-如何（以及执行功能的执行者，
与之相关的措施、规则和条件）
3.网络描述-其中（广义）
4.人员描述-谁（我们包括组织）
5.时间描述-何时
6.动机描述-原因（扩大到包括能力要求）
UCORE和Zachman框架询问与DM2 CDM的叠加
（点击放大）
出身背景
建筑发展
元模型
概念的
必然的
PES
思想基金会
本体论
观点和模型
展示技巧
配置管理
概述
缩略语列表和词汇表
术语
网站地图
档案
国防部
27
DM2——DoDAF概念数据模型
http://cio-nii.defense.gov/sites/dodaf20/conceptual2.html[2011年3月3日下午3:46:36]
转到页面顶部↑
隐私政策|网络政策124;联系人
28
DM2——DoDAF概念数据模型
http://cio-nii.defense.gov/sites/dodaf20/conceptual3.html[2011年3月3日下午3:46:38]
首页DoDAF-DM2工作组DoDAF期刊国防部元数据注册想法链接
DM2-DoDAF元模型
DM2主要要素与国防部六大核心流程的关系
与普遍核心和Zachman框架疑问句的关系
DM2本体基础概述
DM2和核心流程关系概述
DM2中建模的概念的作用概述如下表所示。这个
本表中符号的键位于底部：
将DM2 CDM核心概念映射到DoDAF支持的国防部核心过程
出身背景
建筑发展
元模型
概念的
必然的
PES
思想基金会
本体论
观点和模型
展示技巧
配置管理
概述
缩略语列表和词汇表
术语
网站地图
档案
国防部
29
DM2——DoDAF概念数据模型
http://cio-nii.defense.gov/sites/dodaf20/conceptual3.html[2011年3月3日下午3:46:38]
转到页面顶部↑
隐私政策|网络政策124;联系人
30
DM2——DoDAF概念数据模型
http://cio-nii.defense.gov/sites/dodaf20/conceptual4.html[2011年3月3日下午3:46:40]
首页DoDAF-DM2工作组DoDAF期刊国防部元数据注册想法链接
DM2-DoDAF元模型
DM2本体基础概述
与普遍核心和Zachman框架疑问句的关系
DM2主要要素与国防部六大核心流程的关系
DM2的底层是促进重用的公共本体结构的基础
常见数据模式的概述如下图所示。
DM2基金会概况
顶层基础要素包括：
1.事物，类似于其他模型的对象。
2.个体，作为一个不可分割的整体存在的事物，或作为一个
类别
3.类型，其他集合或类的一组个体或类。
4.元组，事物的有序位置（例如，电子表格或表格中的块）。
这些基础元素类似于许多其他基础数据结构
存在于该行业中。可重用的常见模式有：
1.组成（或全部或部分）。
2.超级/子类型（或一般化/专业化，如坦克或主蝙蝠） Location: A point or extent in space that may be referred to physically or logically.
9. Guidance: An authoritative statement intended to lead or steer the execution of
actions.
Rule: A principle or condition that governs behavior; a prescribed guide for
conduct or action.
Agreement: A consent among parties regarding the terms and
conditions of activities that said parties participate in.
Standard: A formal agreement documenting generally accepted
specifications or criteria for products, processes, procedures, policies,
systems, and/or personnel.
10. Project: A temporary endeavor undertaken to create Resources or Desired Effects.
11. Vision: An end that describes the future state of the enterprise, without regard to
how it is to be achieved; a mental image of what the future will or could be like.
12. Skill: The ability, coming from one's knowledge, practice, aptitude, etc., to do
something well.
Additional CDM concepts are identified and defined in DoDAF-DM2 Data Dictionary.
The CDM also describes the relationships among data constructs in relatively non-technically
and easily understood terms. The figure below is a graphical representation of the CDM.
DM2 Conceptual Data Model (DIV-1) Diagram
Go to top of page ↑
Privacy Policy | Web Policy | Contacts
26
DM2 - The DoDAF Conceptual Data Model
http://cio-nii.defense.gov/sites/dodaf20/conceptual2.html[3/3/2011 3:46:36 PM]
Home DoDAF-DM2 WG DoDAF Journal DoD Meta Data Registry IDEAS Links
DM2 - DoDAF Meta-Model
DM2 CDM Relationship to Universal Core and Zachman Framework
Interrogatives
Relationship of DM2 Principal Elements to DoD's Six Core Processes
Overview of the DM2 Ontologic Foundation
The DM2 CDM relates to Universal Core and the Zachman Framework interrogatives as
shown in the figure below. Specifically:
1. The Data Description — What (we generalize to other Resources besides just Data)
2. The Function Description — How (and also the Performer that performs the Function,
Measures, Rules, and Conditions associated with)
3. The Network Description — Where (generalized)
4. The People Description — Who (we include Organizations)
5. The Time Description — When
6. The Motivation Description — Why (broadened to include Capability requirements)
Overlay of UCORE and Zachman Framework Interrogatives with DM2 CDM
(click to enlarge)
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
27
DM2 - The DoDAF Conceptual Data Model
http://cio-nii.defense.gov/sites/dodaf20/conceptual2.html[3/3/2011 3:46:36 PM]
Go to top of page ↑
Privacy Policy | Web Policy | Contacts
28
DM2 - The DoDAF Conceptual Data Model
http://cio-nii.defense.gov/sites/dodaf20/conceptual3.html[3/3/2011 3:46:38 PM]
Home DoDAF-DM2 WG DoDAF Journal DoD Meta Data Registry IDEAS Links
DM2 - DoDAF Meta-Model
Relationship of DM2 Principal Elements to DoD's Six Core Processes
Relationship to Universal Core and the Zachman Framework interrogatives
Overview of the DM2 Ontologic Foundation
DM2 and Core Process Relationships Overview
An overview of the role of the concepts modeled in the DM2 is shown in the table below. The
key to the symbols in this table are at the bottom:
Mapping of DM2 CDM Core Concepts to DoD Core Processes DoDAF Supports
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
29
DM2 - The DoDAF Conceptual Data Model
http://cio-nii.defense.gov/sites/dodaf20/conceptual3.html[3/3/2011 3:46:38 PM]
Go to top of page ↑
Privacy Policy | Web Policy | Contacts
30
DM2 - The DoDAF Conceptual Data Model
http://cio-nii.defense.gov/sites/dodaf20/conceptual4.html[3/3/2011 3:46:40 PM]
Home DoDAF-DM2 WG DoDAF Journal DoD Meta Data Registry IDEAS Links
DM2 - DoDAF Meta-Model
Overview of the DM2 Ontologic Foundation
Relationship to Universal Core and the Zachman Framework interrogatives
Relationship of DM2 Principal Elements to DoD's Six Core Processes
Underlying the DM2 is a foundation of common ontologic constructs that facilitate the reuse
of common data patterns, an overview of which is shown in the figure below.
Overview of DM2 Foundation
The top-level foundation elements are:
1. Thing, similar to other model’s object.
2. Individual, a thing that exists as an indivisible whole, or as a single member of a
category.
3. Type, a set of individuals or classes of other sets or classes.
4. Tuple, ordered places of things (e.g., a block in a spreadsheet or a table).
These foundation elements are similar to many other foundation high-level data constructs
that exist in the industry. The common patterns that are reused are:
1. Composition (or whole-part).
2. Super/Sub Type (or generalization/specialization, e.g., tank or main battle tank).
3. Before /After, for things that have time-related relationships in their Type.
4. Overlap, e.g., for things that can exchange other things that are parts of themselves,
things that occur at overlapping times and overlapping places.
Composition and Super/Sub Type apply to almost all architecture concepts. Before/After is
frequently used to model before/after situations, while Interface applies to few concepts,
limited at this time to the pattern describing Activity.
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
31
DM2 - The DoDAF Conceptual Data Model
http://cio-nii.defense.gov/sites/dodaf20/conceptual4.html[3/3/2011 3:46:40 PM]
The benefits of adopting the IDEAS formal foundation and common patterns are:
1. Re-use of common patterns saved a lot of work
2. Model compactness through inheritance of superclass properties and common patterns
3. Reconciliation and analysis tool. The agreed-upon analysis principles provide a
principled basis for issue analysis
4. Information pedigree model
5. Design reification and requirements traceability