PPC907BE101 3BHE024577R0101 模拟量自动化输出卡

PPC907BE101 3BHE024577R0101 模拟量自动化输出卡 

确定新的系统或服务、功能（活动）、组件和
需要修改。
2.确定新的资源流和系统集成需求。
3.确定应用新标准的必要性。
4.明确识别系统之间的关系和信息流
SoS中的系统/服务或面向服务的系统中的服务之间
架构（SOA），包括发布或订阅需求的定义
5.接口识别和定义，包括互操作性分析和
标准化。
6.支持接口的配置管理。接口通常是：
记录在接口文件中，代表
负责接口各端的责任方（两个信息
供应商和信息消费者）。这绝不意味着点对点
界面使用企业服务总线实现的接口，
定义了适当的发布/订阅文档，如果
必要时，信息供应商和
消费者
7.关键接口通常记录在正式接口文件中
由负责当局签署（信息供应商和信息
消费者）负责接口的每一端。对于传统的点对点
接口这可以是接口控制图（ICD）的形式，
接口需求文件（IRS）、接口设计文件（IDD），
多址或公共连接（无线电通信或总线
类型连接性）实现可以采用正式协议的形式
（本协议中定义为双方就条款和条件达成的同意
所述各方参与的活动）详细说明
数据的实现（例如，战术数字信息链路[TADILs]）
元素实现表，或者在SOA的情况下，发布/订阅
执行文件。这些协议通常是管理的，并且
由SoS或系统项目经理控制。在新系统中，以及
如果可能，应使用
通用精度数据模型。图4说明了从
网络中心的传统点对点接口的配置控制，
使用精心管理的发布实现连接的分布式处理手段
并根据正式文件签署协议和文件
逻辑和物理数据模型。
49
DM2-资源流
http://cio-nii.defense.gov/sites/dodaf20/resource_flows.html[2011年3月3日下午3:43:08]
从传统配置管理迁移到以数据为中心的配置管理
（点击放大）
e、 老年退休金计划
1.利用信息流的业务应与技术无关。
然而，运营及其关系可能会受到新
技术。在某些情况下，可能需要记录：
执行活动的方式，以检查新系统可以
促进简化活动
2.任务规划，包括模拟和培训。
3.物流规划。
4.为描述信息需求和任务提供必要的基础
排序有助于制定程序、操作计划和促进
相关人员培训。
5.通过以下方式确定关键任务线程和操作资源流交换
注释哪些活动是关键的（即，确定DoDAF描述模型中的关键活动，如关键路径）。
f、 CPM
1.资源流可用于表示结构和行为
投资组合中活动与执行者之间的关系
包括接口和相互依赖性。

PPC907BE101 3BHE024577R0101 模拟量自动化输出卡 

PPC907BE101 3BHE024577R0101 模拟量自动化输出卡 

Identify new system or service, functions (activities), components and
modifications required.
2. Identify new Resource Flow and system integration requirements.
3. Identification of the need for Application of new standards.
4. Clearly identify the relationship and information flow between systems and
system/services in an SoS or between services in a Service Oriented
Architecture (SOA) including definition of publish or subscribe requirements
5. Interface Identification and Definition including interoperability analysis and
standardization.
6. Support configuration management of interfaces. Interfaces are generally
documented in interface documentation representing the agreements of the
responsible parties in charge of each end of the interface (both information
supplier and information consumer). This, in no way implies a point-to-point
interface. Interfaces implemented with an enterprise service bus, for example,
are defined with appropriate publish/subscribe documentation formalized, if
necessary, with contractual agreements between information supplier and
consumer.
7. Critical interfaces are generally documented in formal interface documentation
signed by the responsible authorities (both information supplier and information
consumer) in charge of each end of the interface. For legacy point-to-point
interfaces this may be in the form of Interface Control Drawings (ICDs),
Interface Requirement Documents (IRSs), Interface Design Documents (IDDs),
etc. In multiple access or common connectivity (radio communications or bus
type connectivity) implementations may be in the form of formal agreements
(defined herein as a consent among parties regarding the terms and conditions
of activities that said parties participate in) detailing the specific set of
implementations (e.g., Tactical Digital Information Links [TADILs]) data
elements implementation tables or in the case of a SOA, a publish/subscribe
implementation document. These agreements are, in general, managed and
controlled by the SoS or System Project manager. In new systems, and where
possible the interface should be managed and configuration controlled using a
common precision data model. Figure 4 illustrates the evolution from
configuration control of legacy point-to-point interfaces to a net-centric,
distributed processing means of connectivity using carefully managed publish
and subscribe agreements and documentation based on formally documented
logical and physical data models.
49
DM2 - Resource Flows
http://cio-nii.defense.gov/sites/dodaf20/resource_flows.html[3/3/2011 3:43:08 PM]
Migrating from Legacy to Data Focused Configuration Management
(Click to enlarge)
e. Ops Planning
1. Operations utilizing information flows should be technology independent.
However, operations and their relationships may be influenced by new
technologies. There may be some cases in which it is necessary to document
the way activities are performed to examine ways in which new systems could
facilitate streamlining the activities
2. Mission Planning including simulation and training.
3. Logistics planning.
4. Provide a necessary foundation for depicting information needs and task
sequencing to assist in producing procedures, operational plans and facilitate
associated personnel training.
5. Identify critical mission threads and operational Resource Flow exchanges by
annotating which activities are critical (i.e., identify the activities in the DoDAFdescribed Model that are critical e.g., Critical Path).
f. CPM
1. Resource flows can be used to represent the structural and behavioral
relationships between the Activities and Performers within the portfolio
including interfaces and interdependencies.