PM633 3BSE008062R1 PM 633 CPU处理器模块

PM633 3BSE008062R1 PM 633 CPU处理器模块 

体系结构描述在开发时进行分类，以便于对齐（映射
和链接）、编目、导航和搜索
国防部财产登记处。各层开发的所有体系结构描述应：
联合，如国防部联合战略所述。
为了使国防部企业体系结构能够被发现、共享和
可互操作。体系结构描述还可以支持层中的许多目标，每个目标
其中可能包含对结构、内容或详细程度的具体要求。对齐
决策应平衡体系结构描述的相互依赖性和以下需求：
解决当地问题的当地灵活性。对齐描述了所需的小约束
以确保跨架构级别的一致性。架构描述通常涉及
某些“接触点”指向同一级别或以上级别的其他架构描述，或
以下级别，应在建筑设计开发中发现和使用
确保建立和维护适当联系的说明。需要
它们的计划意味着共享一个接触点的每个体系结构描述应该
可供双方建筑师使用。数据的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程序的核心原则是：
业务驱动的方法。
促进协作和重用。
通过以下方式提高业务运营的效率和有效性：
资本投资流程的企业架构。
通过改进核心流程证明成本节约和成本避免，以及
跨机构共享和相互投资。

PM633 3BSE008062R1 PM 633 CPU处理器模块 

PM633 3BSE008062R1 PM 633 CPU处理器模块 

Architectural descriptions are classified during development to facilitate alignment (mapping
And links), cataloging, navigation, and searching
Property registry of the Ministry of defence. All architecture descriptions developed by each layer shall:
Joint, as described in the DOD joint strategy.
To enable the DOD enterprise architecture to be discovered, shared, and
Interoperable. The architecture description can also support many objectives in the layer, each of which
It may contain specific requirements for structure, content or level of detail. alignment
The decision should balance the interdependencies described in the architecture with the following requirements:
Local flexibility to solve local problems. Alignment describes the minimum constraint required
To ensure consistency across architecture levels. Architecture description usually involves:
Some "touchpoints" point to other schema descriptions at the same level or above, or
The following levels should be found and used in architectural design and development
Instructions to ensure that appropriate contacts are established and maintained. need
Their plan means that each architectural description that shares a touchpoint should
It can be used by architects of both parties. DMR of data and Dar of Architecture
Registration helps to discover and utilize architecture data, but it should be noted that
Any touchpoint within the established COI authority complies with the COI guidelines.
DoD Architecture Enterprise Services
The next generation DOD enterprise architecture will adopt a set of
Registration, discovery, tuning, and,
Translate and leverage architecture data and derived information to support key DOD
The decision-making process is conducted through the implementation of the concept of the DOD network centric strategy.
Dae will be implemented using web services with specific content and / or functions
Provided by one user to other users, many of whom may not be known to the provider. one
Operational resource flow description (redesigned operational viewpoint 2 (ov-2))
DoDAF description model) has been retained in DoDAF v2.0 to describe the following services:
Can be discovered and subscribed from one or more specific sources and delivered to one or
More known or unknown subscribers.
Architecture registration is one of the goals of NCD and the first step to achieve the following goals
Discovery of schema metadata. Dae includes a registration service for registering
Metadata (via DMR) and description
Architecture description (through DARS). The registration service will enable the following directories:
Architecture description in the federated repository and the completed architecture
Description can be used to find. When the architecture description can be found,
It can be aligned, linked, or reused with other architectural descriptions. find
This service enables users to perform joint search of architecture holding meetings
Specified search parameters.
Consistent with the Federal Enterprise Architecture
OMB formulated the Federal Enterprise Architecture (FEA) plan in 2003 to establish
A comprehensive business driven blueprint for the entire federal government. Notice of OMB
nineteen
DoDAF architecture development - 6-step process
http://cio-nii.defense.gov/sites/dodaf20/arch_development.html [3:33:54 PM, March 3, 2011]
A-11 requires cabinet level agencies, including the Ministry of defense, to link their budget submissions
Submit to FEA and evaluate these submissions annually through enterprise architecture
The evaluation plan establishes evaluation scores for the overall progress of the organization.
The core principles of FEA procedure are:
Business driven approach.
Promote collaboration and reuse.
Improve the efficiency and effectiveness of business operation by:
Enterprise structure of capital investment process.
Demonstrate cost savings and avoidance by improving core processes, and
Cross institutional sharing and mutual investment.