NI0C-01 3BSE005735R1 NI0C01 自动化控制电路板

NI0C-01 3BSE005735R1 NI0C01 自动化控制电路板 

模型中使用了编码：
a、 <<个体>>个体的实例-具有时空范围的事物
【颜色名称：灰色（80%），颜色代码：R40 G40 B40】
b、 <<类型>>类型的规格[颜色名称：淡蓝色，颜色代码：R153
G204 B255]
c、 ＜＜IndividualType＞＞成员为个体的类型的规范
【颜色名称：浅橙色，颜色代码：R255 G173 B91】
d、 ＜＜TupleType＞成员为元组的类型规范〔颜色名称：
浅绿色，颜色代码：R204 G255 B204]
e、 ＜＜Powertype＞＞一种类型的规范，它是给定类型的所有子集的集合
类型[颜色名称：薰衣草，颜色代码：R204 G153 B255]
f、 <>名称的规范，示例文本作为标记提供
值[颜色名称：棕褐色，颜色代码：R255 G254 B153]
g、 ＜＜NamingScheme＞＞类型的规范，其成员为名称[Color]
名称：黄色，颜色代码：R255 G255 B0]
模型中使用了以下定型关系：
a、 ＜＜typeInstance＞＞类型与其实例之一之间的关系
（UML：依赖项）[颜色名称：红色，颜色代码：R255 G0 B0]
b、 <>类型与其幂集之间的关系
（UML：依赖项）[颜色名称：红色，颜色代码：R255 G0 B0]
c、 ＜＜nameTypeInstance＞名称与其名称类型之间的关系
（UML：依赖项）[颜色名称：红色，颜色代码：R255 G0 B0]
d、 ＜＜超级子类型＞＞类型与其子类型之一之间的关系
（UML：泛化）[颜色名称：蓝色，颜色代码：R0 G0 B255]
出身背景
建筑发展
元模型
概念的
必然的
表演者
资源流动
信息和数据
规则
目标
能力
服务
项目
物化
组织结构
措施
位置
纯种
PES
思想基金会
本体论
观点和模型
展示技巧
配置管理
概述
缩略语列表和词汇表
术语
网站地图
档案
国防部
37
DoDAF元模型和逻辑模型
http://cio-nii.defense.gov/sites/dodaf20/logical_1-2.html[2011年3月3日下午3:42:55]
e、 <>个人与其一部分之间的关系
（UML：聚合）[颜色名称：绿色，颜色代码：R0 G147 B0]
f、 ＜＜namedBy＞＞名称与其命名的事物之间的关系〔颜色名称：
黑色，颜色代码：R0 G0 B0]
g、 ＜＜元组＞/＜＜耦合＞事物之间的关系（UML:n元关系）
钻石）[颜色名称：灰色（80%），颜色代码：R40 G40 B40]
下图描述了一些示例：
（点击放大）
类、属性和关联名称的命名约定为驼峰大小写
跟随：
a、 类名以大写字母开头。
b、 属性和关联名称以小写开头。
c、 首字母缩略词均为大写。避免在名称中间使用首字母缩略词
因为首字母缩略词、大写字母和后续字母的连接
前导大写的字符串。
注意，图标的大小并不表示其重要性；尺寸调整为：
减少线交叉和弯曲，使图表更易于理解。
注：在某些情况下，数据模型图可能难以在硬拷贝打印输出中读取
但在线DoDAF v2.0中发布了一个可以放大的全分辨率版本
元模型数据字典。模型术语的定义包含在DoDAF v2.0中
元模型数据字典（1节中引用的下载链接）。这包括以下内容的摘要：
别名、复合术语定义、权威来源定义和基本原理。注意
基本类通常不显示在数据组图上；这个基础
在ideas基础本体选项卡中可以找到材料。这包括超级子类型whole38
DoDAF元模型和逻辑模型
http://cio-nii.defense.gov/sites/dodaf20/logical_1-2.html[2011年3月3日下午3:42:55]
部分、时间整体部分、重叠、类型实例（成员）和前后模式。
还未显示用于架构信息分类标记的数据结构
在整体和要素（部分）层面上，使用智能社区-智能
标准标记（IC-ISM）。IC-ISM的模式是物理交换
规格（PES）选项卡。后，请注意，图标的大小并不表示其
重要性调整尺寸以减少线交叉和弯曲，以绘制图表
更容易理解。
转到页面顶部↑
隐私政策|Web

NI0C-01 3BSE005735R1 NI0C01 自动化控制电路板 

NI0C-01 3BSE005735R1 NI0C01 自动化控制电路板 

coding are used in the model:
a. <> An instance of an Individual - something with spatio-temporal extent
[Color Name: Grey(80%), Color Codes: R40 G40 B40]
b. <> The specification of a Type [Color Name: Pale Blue, Color Code: R153
G204 B255]
c. <> The specification of a Type whose members are Individuals
[Color Name: Light Orange, Color Codes: R255 G173 B91]
d. <> The specification of a Type whose members are tuples [Color Name:
Light Green, Color Codes: R204 G255 B204]
e. <> The specification of a Type that is the set of all subsets of a given
Type [Color Name: Lavender, Color Codes: R204 G153 B255]
f. <> The specification of a name, with the exemplar text provided as a tagged
value [Color Name: Tan, Color Codes: R255 G254 B153]
g. <> The specification of a Type whose members are names [Color
Name: Yellow, Color Codes: R255 G255 B0]
The following stereotyped relationships are used in the model:
a. <> a relationship between a type and one of its instances
(UML:Dependency) [Color Name: Red, Color Codes: R255 G0 B0]
b. <> a relationship between a type and its powerset
(UML:Dependency) [Color Name: Red, Color Codes: R255 G0 B0]
c. <> a relationship between a name and its NameType
(UML:Dependency) [Color Name: Red, Color Codes: R255 G0 B0]
d. <> a relationship between a type and one of its subtypes
(UML:Generalisation) [Color Name: Blue, Color Codes: R0 G0 B255]
Background
Architecture Development
Meta-Model
Conceptual
Logical
Performers
Resource Flows
Information and Data
Rules
Goals
Capability
Services
Project
Reification
Organizational Structure
Measures
Locations
Pedigree
PES
IDEAS Foundation
Ontology
Viewpoints & Models
Presentation Techniques
Configuration Management
Overview
Acronyms List and Glossary
of Terms
Site Map
Archives
Department of Defense
37
DoDAF Meta-Model Logical Model
http://cio-nii.defense.gov/sites/dodaf20/logical_1-2.html[3/3/2011 3:42:55 PM]
e. <> a relationship between an individual and one of its parts
(UML:Aggregation) [Color Name: Green, Color Codes: R0 G147 B0]
f. <> a relationship between a name and the thing it names [Color Name:
Black, Color Codes: R0 G0 B0]
g. <>/< a relationship between a things (UML:n-ary relationship
diamond) [Color Name: Grey(80%), Color Codes: R40 G40 B40]
Some examples are depicted in the figure below:
(click to enlarge)
The naming convention for classes, attributes, and association names is camel case as
follows:
a. Class names start with uppercase.
b. Attributes and association names start with lowercase.
c. Acronyms are all uppercase. Acronyms in the middle of a name are avoided
because of the concatenation of the acronym uppercase and the succeeding
string leading uppercase.
Note that the size of the icons is not indicative of their importance; the sizes are adjusted to
reduce line crossings and bends to make the diagrams easier to understand.
Note: In some instances the data model figures may be hard to read in a hardcopy printout
but a version at full-resolution which can be zoomed in is published in the online DoDAF v2.0
Meta-Model Data Dictionary. Definitions for the model terms are contained in the DoDAF v2.0
meta-model data dictionary (download links cited in section 1). This includes a summary of
aliases, composite term definitions, authoritative source definitions, and rationale. Note that
foundational classes are generally not shown on data group diagrams; this foundational
material is found in the ideas foundation ontology tab. This includes super-subtype, whole38
DoDAF Meta-Model Logical Model
http://cio-nii.defense.gov/sites/dodaf20/logical_1-2.html[3/3/2011 3:42:55 PM]
part, temporal-whole-part, overlap, type-instance (member-of), and before-after patterns.
Also not shown are the data structures for classification marking of architecture information
at the whole and element (portion) levels using the Intelligence Community - Intelligence
Standard Markings (IC-ISM). The schema for the IC-ISM is in physical exchange
specification (PES) tab. Lastly, note that the size of the icons is not indicative of their
importance; sizes are adjusted to reduce line crossings and bends to make the diagrams
easier to understand.
Go to top of page ↑
Privacy Policy | Web