操作界面触摸屏 原厂带盒子 说明书 PP220 3BSC690099R2

 操作界面触摸屏 原厂带盒子 说明书 PP220 3BSC690099R2

而先前版本的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、 规则和措施适用于特定活动及其执行者。活动，
系统和人员可以分配到位置，也可以进一步分配
条件和约束。
e、 术语流意味着某些东西（如物资、信息）正在从
点A到点B，因此使用了“重叠”的基础概念。
f、 交换或流三重可以具有与之相关联的度量，
吞吐量、可靠性或QoS。
g、 资源流建模可以在不同的细节和保真度级别上执行
这取决于正在分析的关注领域和正在寻求的解决方案。这个
在先前版本的DoDAF中，上层聚合被称为需求线。
使用表示聚合级别的其他术语，具体取决于
兴趣社区（例如，SysML建模标准使用生命线）。
h、 应该指出，资源之间的信息输入和输出
分解级别可能比信息的抽象级别更高
矩阵中表示的特征。这通常是为了简化图形
信息流的表示或在初始定义阶段，其中
特征仍然未知。在这种情况下，将映射多个信息交换
到单个资源输入或输出。同样，信息输入和输出
在资源之间，低层次的分解可能在更高层次的细节
而不是矩阵中的信息交换以及多个信息输入
输出可以映射到单个信息交换。在这些情况下，提供
必要的清晰和，信息的本体或分类结构
应开发聚合，以用于
资源流模型（例如，海军通用信息交换列表[CIEL]
表示显示分类结构或聚合级别的计划）。

 操作界面触摸屏 原厂带盒子 说明书 PP220 3BSC690099R2

 操作界面触摸屏 原厂带盒子 说明书 PP220 3BSC690099R2
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.
e. The term flow implies that something (e.g., materiel, information) is moving from
point A to point B, hence the use of the foundation concept of "overlap".
f. The exchange or flow triple may have Measures associated with it such as timeliness,
throughput, reliability, or QoS.
g. Resource Flow modeling can be performed at varying levels of detail and fidelity
depending on the areas of concern being analyzed and the solutions being sought. The
upper-level aggregations have been termed need lines in previous versions DoDAF.
Other terminology expressing levels of aggregation are used depending on the
community of interest (e.g., The SysML modeling standard uses lifeline).
h. It should be noted that information inputs and outputs between resources for some
levels of decomposition may be at a higher-level of abstraction than the information
characteristics represented in the matrix. This is commonly done to simplify graphical
representations of information flow or in the initial definition stages where the
characteristics are still unknown. In this case, multiple information exchanges will map
to a single resource input or output. Similarly, the information inputs and outputs
between resources at a low-level of decomposition may be at a higher-level of detail
than the information exchanges in the matrix, and multiple information inputs and
outputs may map to a single information exchange. In these cases, to provide the
necessary clarity and precision, an ontological or taxonomic structure of information
aggregation should be developed for use in each level of decomposition of the
Resource Flow models (e.g., The Navy Common Information Exchange List [CIEL]
represents initiatives showing taxonomic structure or levels of aggregation).