CPUM-05 3HNE05890-1/02 3HNE09016-1 机器人电路板

CPUM-05 3HNE05890-1/02 3HNE09016-1 机器人电路板 

代表“原样”起点，其中遗留系统有时很差
文件化，过程基本上未定义。还有一个考虑是，长期目标往往非常灵活，导致“未来”版本的变化。
因为“现状”和“未来”体系结构描述是类似的时间特定版本
具有相似视角的数据集，过渡规划能够绘制演化路径
从“现状”到其相应的“未来”建筑愿景
通过未来（可能）了解预期结果或目标
未定义）未来点。预计未来的体系结构描述将发生变化
随着时间的推移，部门优先事项发生变化和重新调整。
国防部体系结构管理的联邦方法
国防部对分布式体系结构数据采用了联合方法
18
DoDAF体系结构开发-6步流程
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[2011年3月3日下午3:33:54]
服务、机构和COI之间的收集、组织和管理
利用虚拟而非物理数据开发国防部企业体系结构的方法
通过支持文档和架构视图描述的集合。这种方法
提供更大的灵活性，同时保留重要的监督和质量管理
部门一级的服务。关于国防部联邦方法的详细指南将包括：
包含在DoDD 8210“国防部企业架构”中
分级问责
分层问责（TA）是将权力和责任分配给国防部
国防部企业体系结构要素的组织。根据TA，国防部正在定义和构建
企业范围的能力，包括数据标准、业务规则、使能系统，
以及企业部门、特定部门的相关接口层
（例如，JCA、国防部组件）和程序解决方案。每一层都有具体的目标，如
以及对他们之上或之下的层的责任。
体系结构描述在开发时进行分类，以便于对齐（映射
和链接）、编目、导航和搜索
国防部财产登记处。各层开发的所有体系结构描述应：
联合，如国防部联合战略所述。
为了使国防部企业体系结构能够被发现、共享和
可互操作。体系结构描述还可以支持层中的许多目标，每个目标
其中可能包含对结构、内容或详细程度的具体要求。对齐
决策应平衡体系结构描述的相互依赖性和以下需求：
解决当地问题的当地灵活性。对齐描述了所需的小约束
以确保跨架构级别的一致性。架构描述通常涉及
某些“接触点”指向同一级别或以上级别的其他架构描述，或
以下级别，应在建筑设计开发中发现和使用
确保建立和维护适当联系的说明。需要
它们的计划意味着共享一个接触点的每个体系结构描述应该
可供双方建筑师使用。数据的DMR和架构的DAR
注册有助于发现和利用体系结构数据，但需注意
已建立的COI权限内的任何接触点均遵守COI指南。
国防部架构企业服务
下一代国防部企业架构将采用一套
国防部体系结构企业服务（DAE）的注册、发现、调整和，
翻译和利用体系结构数据和衍生信息，以支持关键国防部
通过实施国防部网络中心战略的概念进行决策过程。
DAE将使用Web服务实现，其中特定内容和/或功能
由一个用户提供给其他用户，其中许多用户可能不为提供商所知。一
作战资源流描述（重新设计的作战视点2（OV-2）
DoDAF描述模型）已保留在DoDAF V2.0中，用于描述以下服务：
可以从一个或多个特定源发现和订阅，并交付给一个或
更多已知或未知订户。
体系结构注册是NCD的目标之一，是实现以下目标的一步
架构元数据的发现。DAE包括一个注册服务，用于注册
元数据（通过DMR）和描述
架构描述（通过DARS）。注册服务将启用以下目录：
联邦存储库中的体系结构描述，以及完成后的体系结构
描述可用于查找。W

CPUM-05 3HNE05890-1/02 3HNE09016-1 机器人电路板 

CPUM-05 3HNE05890-1/02 3HNE09016-1 机器人电路板 

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.”
Tiered Accountability
Tiered Accountability (TA) is the distribution of authority and responsibility to a DoD
organization for an element of the DoD EA. Under TA, DoD is defining and building
enterprise-wide capabilities that include data standards, business rules, enabling systems,
and an associated layer of interfaces for Department, specified segments of the enterprise
(e.g., JCA, DoD Components), and Programmatic solutions. Each tier has specific goals, as
well as responsibilities to the tiers above or below them.
Architectural Descriptions are categorized when developed to facilitate alignment (mapping
and linking), cataloging, navigating, and searching disparate architecture information in a
DoD registry of holdings. All Architectural Descriptions developed by the tiers should be
federated, as described in the DoD Federation Strategy.
Alignment in the tiers is required for the DoD EA to be discoverable, shareable, and
interoperable. Architectural Descriptions can also support many goals within the tiers, each
of which may imply specific requirements for structure, content, or level of detail. Alignment
decisions should balance the interdependence of Architectural Descriptions with the need for
local flexibility to address local issues. Alignment describes the minimum constraints needed
to ensure consistency across architecture levels. Architectural Descriptions often relate at
some ‘touch point’ to other Architectural Descriptions on the same level, level(s) above, or
level(s) below, and should be discovered and utilized in the development of Architectural
Descriptions to ensure that appropriate linkages are created and maintained. The need to
plan for them implies that each Architectural Description sharing a touch-point should be
available to architects on both sides. The DMR for data and the DARS for architecture
registration facilitate the ability to discover and utilize architectural data, with the caveat
that any touch-points within the purview of an established COI adhere to COI guidance.
DoD Architecture Enterprise Services
The next generation of DoD Enterprise Architectures will be constructed by employing a set
of DoD Architecture Enterprise Services (DAES) for registering, discovering, aligning,
translating, and utilizing architectural data, and derived information to support key DoD
decision processes through implementing the concepts of the DoD Net-Centric Strategies.
DAES will be implemented using Web Services, in which specific content and/or functionality
is provided by one user for others, many of whom may be unknown to the provider. An
Operational Resource Flow Description (A redesigned Operational Viewpoint 2 (OV-2)
DoDAF-described Model) has been retained in DoDAF V2.0 to describe those services that
can be discovered and subscribed from one or more specific sources and delivered to one or
more known or unknown subscribers.
Registration of architectures, one of the goals of the NCDS , is the first step toward enabling
discovery of architecture metadata. DAES includes a registration service to register the
metadata (through the DMR), and a method to describe the purpose and scope of an
Architectural Description (through DARS). The registration service will enable cataloging of
Architectural Descriptions in federated repositories, and, once complete, Architectural
Descriptions are ‘available’ for discovery. W