PPC907BE 3BHE024577R0101 工业自动化通讯主板

XVC770BE101 3BHE021083R0101 输入输出通讯主板 

在资源之间流动的信息的内容（例如，接口定义）。
资源相对于一个资源的顺序或顺序行为（并行或串行）
另一个（例如，项目任务执行和关键路径）。
组织之间或内部的资源流的行为（例如，
信息流等）。
在资源的空间和/或时间存在期间的状态变化。
修改资源流的行为的规则（例如，
控制、决策等）。
定义资源流质量、约束、时间等的措施
（例如，服务质量（QoS）、性能度量、有效性度量等），
等等）。
协调资源流行为的控制流。
数据组描述
包括资源流的数据的DoDAF元模型如下图所示。
应注意以下几点：
a、 而先前版本的DoDAF仅对信息和数据交换进行建模
流，此版本还允许对其他流进行建模，例如：
1.弹药、燃料等对模拟火力很重要的物资流
能力解决方案的速率、物流等方面，以便与
其他替代解决方案。
2.人员类型，如军事职业专业（MOS），允许
代表理论的培训和教育管道方面，
组织、培训、材料、领导和教育、人员和
设施（DOTMLPF）。
3.执行者，如服务、系统或组织
项目设计和生产过程（活动）的输出或结果。这
例如，允许对采办项目进行建模。
b、 与先前版本的DoDAF的另一个不同之处在于，所有交换和流都是
由于生产或消费活动。资源流是基于活动的，而不是
基于执行者，因为执行者不能生产或使用除
通过进行生产或消费活动。也就是说，表演者只能
通过进行生产或消费活动来提供或消费。对于
实例、发布和订阅被建模为
发布活动、订阅活动以及信息或数据资源。
出身背景
建筑发展
元模型
概念的
必然的
表演者
资源流动
信息和数据
规则
目标
能力
服务
项目
物化
组织结构
措施
位置
纯种
PES
思想基金会
本体论
观点和模型
展示技巧
配置管理
概述
缩略语列表和词汇表
术语
网站地图
档案
国防部
46
DM2-资源流
http://cio-nii.defense.gov/sites/dodaf20/resource_flows.html[2011年3月3日下午3:43:08]
请注意，发布通常不与订阅同时进行，但
订阅服务器必须访问发布位置才能检索资源。对于
例如，数据可能在格林尼治时间2:00发布在位于某个URL的服务器上，并且
订户在格林尼治标准时间10:00之前不得重叠。请在图表中注意重叠
是生产活动、消费活动和资源的三重结构。
c、 交换或流量三元组可能有与其相关的标准（规则），例如：
信息保证（IA）/安全规则或数据发布或订阅
COI和web服务标准。
d、 规则和措施适用于特定活动及其执行者。活动，
系统和人员可以分配到位置，也可以进一步分配
条件和约束

XVC770BE101 3BHE021083R0101 输入输出通讯主板 

XVC770BE101 3BHE021083R0101 输入输出通讯主板 

The content of the information flowing between resources (e.g., interface definition).
The order or sequential behavior (parallel or serial) of the resources in relation to one
another (e.g., project task execution and critical path).
The behavior of Resource Flow between or within organizations (e.g., work flow,
information flow, etc.).
The changes in state during the spatial and/or temporal existence of the resource.
The rules that modify the behavior of the Resource Flow (e.g., business rules,
controls, decisions, etc.).
The measures that define the quality, constraints, timing, etc. of the Resource Flow
(e.g., Quality of Service (QoS), measures of performance, measures of effectiveness,
etc.).
The flow of control orchestrating the behavior of the Resource Flow.
Data Group Description
The DoDAF Meta Model for the data comprising Resource Flows is shown in the figure below.
The following should be noted:
a. Whereas prior versions of DoDAF modeled only information and data exchanges and
flows, this version also allows modeling of other flows, such as:
1. Materiel flows such as ammunition, fuel, etc. important for modeling the fire
rate, logistics, etc., aspects of a Capability solution so it can be compared with
other alternative solutions.
2. Personnel Types such as Military Occupational Specialty (MOS) that allow
representation of the Training and Education pipeline aspects of Doctrine,
Organization, Training, Material, Leadership and Education, Personnel, and
Facilities (DOTMLPF).
3. Performers such as Services, Systems, or Organizations that might be the
output or result of a Project’s design and production process (activities). This
allows modeling of, for instance, an acquisition project.
b. Another difference from prior versions of DoDAF is that all exchanges and flows are by
virtue of a producing or consuming Activity. Resource Flows are Activity-based, not
Performer based since a Performer cannot produce or consume a resource other than
by conduct of a production or consumption activity. That is, a Performer can only
provide or consume by conducting an activity of production or consumption. For
instance, publication and subscription are modeled as an interaction between the
publishing Activity, the subscribing Activity, and the information or data Resource.
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
46
DM2 - Resource Flows
http://cio-nii.defense.gov/sites/dodaf20/resource_flows.html[3/3/2011 3:43:08 PM]
Note that publication is typically not at the same time as subscription but the
subscriber does have to go to the publication place to retrieve the Resource. For
example, data might be published at 2:00 GMT on a server located at some URL and
the subscriber may not overlap until 10:00 GMT. Also note in the diagram the overlap
is a triple - the producing Activity, the Consuming Activity, and the Resource.
c. The exchange or flow triple may have standards (Rules) associated with it such as
Information Assurance (IA)/Security rules or, for data publication or subscription, data
COI and web services standards.
d. Rules and Measures are applied to specific Activities and their Performers. Activities,
Systems and Personnel can be assigned to Locations and further can be assigned
Conditions and Constraints