PFEA113-65 3BSE028144R0065 PFEA113 张力控制器

 PFEA113-65 3BSE028144R0065 PFEA113 张力控制器

JCA组合描述了未来、所需的作战、作战、业务和防御
情报能力，以及所需的系统和服务。他们提供
组织协调和联合国防部企业体系结构内容以支持国防部
投资组合管理结构。未来国防部作战环境的描述
相关能力需求代表了国防部企业体系结构的目标体系结构。
这些是由功能所有者和JCA开发人员确定的时间阶段。
在以网络为中心的操作环境中，从“现状”迁移到“未来”需要
国防部信息环境体系结构（DoD IEA）和网络中心战略
作为过渡序列的统一参考，并指导过渡序列，以确保
根据需要，适当描述了运营/业务能力和IT能力。
国防部首席信息官正在制定一项政策，以描述联邦如何成熟
国防部企业体系结构及其与联邦解决方案体系结构描述的关系。
过渡规划
如上所述，创建和使用体系结构描述的一个主要推动力是
指导新企业、能力和系统的获取和开发，或
对现有系统的改进。DoDAF的早期版本专门解决了这一需求
使用“现状”和“未来”体系结构描述，以及系统和/或服务
技术预测。“现状”和“未来”概念是特定于时间的快照
初作为过渡过程端点的DoDAF视图。然而
过渡战略有几个潜在的陷阱，包括难以准确
代表“原样”起点，其中遗留系统有时很差
文件化，过程基本上未定义。还有一个考虑是，长期目标往往非常灵活，导致“未来”版本的变化。
因为“现状”和“未来”体系结构描述是类似的时间特定版本
具有相似视角的数据集，过渡规划能够绘制演化路径
从“现状”到其相应的“未来”建筑愿景
通过未来（可能）了解预期结果或目标
未定义）未来点。预计未来的体系结构描述将发生变化
随着时间的推移，部门优先事项发生变化和重新调整。
国防部体系结构管理的联邦方法
国防部对分布式体系结构数据采用了联合方法
18
DoDAF体系结构开发-6步流程
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[2011年3月3日下午3:33:54]
服务、机构和COI之间的收集、组织和管理
利用虚拟而非物理数据开发国防部企业体系结构的方法
通过支持文档和架构视图描述的集合。这种方法
提供更大的灵活性，同时保留重要的监督和质量管理
部门一级的服务。关于国防部联邦方法的详细指南将包括：
包含在DoDD 8210“国防部企业架构”中。

 PFEA113-65 3BSE028144R0065 PFEA113 张力控制器

 PFEA113-65 3BSE028144R0065 PFEA113 张力控制器

The JCA portfolios describe future, required operational, warfighting, business, and Defense
intelligence capabilities, together with the systems and services required. They provide the
organizing construct for aligning and federating DoD EA content to support the Department
portfolio management structure. The description of the future DoD operating environment
and associated capability requirements represent the target architecture of the DoD EA.
These are time-phased as determined by functional owners and JCA developers.
Migration in a net-centric operating environment from the “As-Is” to the “To-Be” requires
that the DoD Information Environment Architecture (DoD IEA) and the Net-Centric strategies
act as uniform references for, and guide the transition sequence to ensure that both
operational/business capabilities and IT capabilities, as required, are properly described.
Policy is being developed by the DoD CIO to describe how federation will be used to mature
the DoD EA as well as its relationship to federated, solution Architectural Descriptions.
Transition Planning
As discussed above, one major impetus for creating and using Architectural Descriptions is to
guide acquisition and development of new enterprises, capabilities and systems or
improvements to existing ones. Earlier versions of DoDAF addressed this need exclusively
using “As-Is” and “To-Be” Architectural Descriptions, along with a Systems and/or Services
Technology Forecast. The “As-Is” and “To-Be” concepts are time-specific snapshots of
DoDAF views that initially served as the endpoints of a transition process. However, this
transition strategy has several potential pitfalls, to include the difficulty in accurately
representing the “As-Is” starting point where legacy systems are sometimes poorly
documented, and processes are largely undefined. There is also the consideration that longterm goals are often very flexible, resulting in flux in the “To-Be” version.
Since the “As-Is” and “To-Be” Architectural Descriptions are time-specific versions of similar
sets of data with similar viewpoints, transition planning is able to chart an evolutionary path
from the “As-Is” to its corresponding “To-Be” architectural vision given a clear
understanding of the expected outcomes or objectives through some future (perhaps
undefined) future point. It is expected that the To-Be Architectural Descriptions will change
over time as Departmental priorities shift and realign.
Federated Approach to DoD Architecture Management
The Department has adopted a federated approach to distributed architectural data
18
DoDAF Architecture Development - 6 Step Process
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[3/3/2011 3:33:54 PM]
collection, organization, and management among the Services, Agencies and COIs as its
means of developing the DoD Enterprise Architecture, with a virtual rather than physical data
set described through supporting documentation and architectural views. This approach
provides increased flexibility while retaining significant oversight and quality management
services at the Departmental level. Detailed guidance on the DoD federation approach will be
contained in DoDD 8210, “Architecting the DoD Enterprise.