控制板 83886-001 UI 4-083885-001 83886001

 控制板 83886-001 UI 4-083885-001 83886001

决策应平衡体系结构描述的相互依赖性和以下需求：
解决当地问题的当地灵活性。对齐描述了所需的小约束
以确保跨架构级别的一致性。架构描述通常涉及
某些“接触点”指向同一级别或以上级别的其他架构描述，或
以下级别，应在建筑设计开发中发现和使用
确保建立和维护适当联系的说明。需要
它们的计划意味着共享一个接触点的每个体系结构描述应该
可供双方建筑师使用。数据的DMR和架构的DAR
注册有助于发现和利用体系结构数据，但需注意
已建立的COI权限内的任何接触点均遵守COI指南。
国防部架构企业服务
下一代国防部企业架构将采用一套
国防部体系结构企业服务（DAE）的注册、发现、调整和，
翻译和利用体系结构数据和衍生信息，以支持关键国防部
通过实施国防部网络中心战略的概念进行决策过程。
DAE将使用Web服务实现，其中特定内容和/或功能
由一个用户提供给其他用户，其中许多用户可能不为提供商所知。一
作战资源流描述（重新设计的作战视点2（OV-2）
DoDAF描述模型）已保留在DoDAF V2.0中，用于描述以下服务：
可以从一个或多个特定源发现和订阅，并交付给一个或
更多已知或未知订户。
体系结构注册是NCD的目标之一，是实现以下目标的一步
架构元数据的发现。DAE包括一个注册服务，用于注册
元数据（通过DMR）和描述
架构描述（通过DARS）。注册服务将启用以下目录：
联邦存储库中的体系结构描述，以及完成后的体系结构
描述可用于查找。当可发现架构描述时，
它可以与其他体系结构描述对齐、链接或重复使用。发现
该服务使用户能够执行架构控股会议的联合搜索
指定的搜索参数。
与联邦企业体系结构保持一致
OMB于2003年制定了联邦企业架构（FEA）计划，以建立
整个联邦政府的全面业务驱动蓝图。OMB的通告
19
DoDAF体系结构开发-6步流程
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[2011年3月3日下午3:33:54]
A-11要求内阁级机构，包括国防部，将其提交的预算联系起来
提交给FEA，并通过企业架构每年评估这些提交
评估计划，为机构的整体进展建立评估分数。
FEA程序的核心原则是：
业务驱动的方法。
促进协作和重用。
通过以下方式提高业务运营的效率和有效性：
资本投资流程的企业架构。
通过改进核心流程证明成本节约和成本避免，以及
跨机构共享和相互投资。
国防部利用FEA结构和核心原则为国防部提供
企业管理信息：它需要实现自身的战略转型
目标并响应OMB的向上报告要求。主要目标是：
通过提供跨任务分析框架，使用EA提高国防部的性能
确定差距和冗余；通过制定过渡计划和目标
有助于将国防部转移到网络中心环境的体系结构。
存在几个描述企业级的联邦和国防部特定EA工件
管理信息。其中包括：

 控制板 83886-001 UI 4-083885-001 83886001

 控制板 83886-001 UI 4-083885-001 83886001

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. When an Architectural Description is discoverable,
it can be aligned to, linked to, or re-used by other Architectural Descriptions. The discovery
service enables users to execute a federated search for architecture holdings meeting
specified search parameters.
Alignment to the Federal Enterprise Architecture
The OMB established the Federal Enterprise Architecture (FEA) program in 2003 to build a
comprehensive business-driven blueprint of the entire Federal Government. OMB’s Circular
19
DoDAF Architecture Development - 6 Step Process
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html[3/3/2011 3:33:54 PM]
A-11 requires that Cabinet-level agencies, including the DoD, link their budget submissions
to the FEA, and annually evaluates those submissions through the Enterprise Architecture
Assessment Program, which establishes an evaluation score for overall agency progress.
The core principles of the FEA program are:
Business-driven approach.
Promote collaboration of effort and reuse.
Improve efficiency and effectiveness of business operations through the use of
enterprise architecture for the capital investment process.
Demonstrate cost savings and cost avoidance through improved core processes, and
cross-agency sharing and mutual investment.
DoD leverages the FEA construct and core principles to provide the Department with the
enterprise management information it needs to achieve its own strategic transformation
goals and respond to upward reporting requirements of OMB. The primary objective is to
improve DoD performance, using EA, by providing a framework for cross-mission analysis
and identification of gaps and redundancies; and by developing transition plans and target
architectures that will help move DoD to the net-centric environment.
Several Federal and DoD-specific EA artifacts exist that describe enterprise-level
management information. These include: