SYNPOL D CMA-130R 3DDE300410 基本控制器面板

SYNPOL D CMA-130R 3DDE300410 基本控制器面板 

这些观点普遍理解这一点。
DM2提供了收集、组织和存储数据所需的信息
理解。
DM2取代了以前支持的核心体系结构数据模型（CADM）
DoDAF的版本。DM2是一种数据结构，有助于读者理解
架构文档中数据的使用。CADM可继续用于支持：
DoDAF早期版本中创建的架构。注：DoDAF V2.0不
规定物理数据模型（PDM），将该任务留给软件开发人员
谁将在自己的软件中实施DoDAF的原则和实践
供品
DoDAF V2.0与早期版本的命令、控制和应用程序相比有显著变化，
通信、计算机和情报监视侦察体系结构
框架（C4ISR AF）或DoDAF，因为架构师现在可以自由创建
满足客户需求的企业架构。DoDAF V2.0的核心是
一种以数据为中心的方法，其中创建支持决策的体系结构是：
辅助数据的收集、存储和维护，以提高效率和
有效决策。架构师和涉众选择视图以确保
将解释正在审查的过程或活动的当前和未来状态。选择
架构视图仔细确保它们充分解释了需求，并且
提出的解决方案将增强观众的理解。
DoDAF V2.0还提供但不要求体系结构中的特定方法
发展它提供了如何确保其他建议
方法可以根据需要进行调整，以满足国防部数据收集和
存储类似地，DoDAF中给出的视图是示例，旨在作为
特定视图的可能可视化。DoDAF V2.0还继续为以下方面提供支持：
视图（即在框架的先前版本中开发的“产品”）。这些观点没有
要求工具集供应商进行任何特定的图形设计。
权威：DoDAF支持的法律和政策
联邦法律和政策已经表达了对支持业务的体系结构的需求
4.
多达夫导言
http://cio-nii.defense.gov/sites/dodaf20/background.html[2011年3月3日下午3:33:50]
决定。
政策/指导说明
克林格-科恩法案
1996年
认识到联邦机构需要改进其工作方式
选择和管理IT资源和状态，“信息技术
对于执行机构而言，架构意味着集成
发展或维护IT并获取新IT的框架
实现机构的战略目标和信息资源
管理目标。”首席信息官被指派
负责“开发、维护和促进
为
执行机构”。
电子政务
2002年法案
要求开发企业架构以帮助增强
管理和推广电子政务服务，以及
过程。
办公室
管理和
预算通告
A-130
“制定联邦信息管理政策
“资源”，并要求使用企业架构来支持
资本规划和投资控制流程。包括
创建和维护的实施原则和指南
企业架构。
OMB联邦
企业
建筑学
参考模型
（有限元分析室）
促进跨机构分析和识别重复
内部和跨部门的投资、差距和合作机会
联邦机构。与参考模型的对齐确保：
有限元分析的重要元素以通用和
以一致的方式。国防部企业架构参考模型包括：
与FEA RM对齐。
OMB企业
建筑学
看法
框架
（EAAF）
作为企业架构成熟度评估的基础。
遵守EAAF可确保企业架构：
先进并适当开发，以提高性能
信息资源管理和IT投资决策。

SYNPOL D CMA-130R 3DDE300410 基本控制器面板 

SYNPOL D CMA-130R 3DDE300410 基本控制器面板 

commonly understood across those views.
The DM2 provides information needed to collect, organize, and store data in a way easily
understood.
The DM2 replaces the Core Architecture Data Model (CADM) which supported previous
versions of the DoDAF. DM2 is a data construct that facilitates reader understanding of the
use of data within an architecture document. CADM can continue to be used in support of
architectures created in previous versions of DoDAF. NOTE: DoDAF V2.0 does NOT
prescribe a Physical Data Model (PDM), leaving that task to software developers
who will implement the principles and practices of DoDAF in their own software
offerings.
DoDAF V2.0 is a marked change from earlier versions of Command, Control,
Communications, Computers, and Intelligence Surveillance Reconnaissance Architecture
Framework (C4ISR AF) or DoDAF, in that architects now have the freedom to create
enterprise architectures to meet the demands of their customers. The core of DoDAF V2.0 is
a data-centric approach where the creation of architectures to support decision-making is
secondary to the collection, storage, and maintenance of data needed to make efficient and
effective decisions. The architect and stakeholders select views to ensure that architectures
will explain current and future states of the process or activity under review. Selecting
architectural views carefully ensures that they adequately explain the requirement and
proposed solution in ways that will enhance audience understanding.
DoDAF V2.0 also provides, but does not require, a particular methodology in architecture
development. It provides guidance and suggestions on how to ensure that other proposed
methods can be adapted as needed to meet the DoD requirements for data collection and
storage. Similarly, the views presented in DoDAF are examples, intended to serve as a
possible visualization of a particular view. DoDAF V2.0 also continues providing support for
views (i.e., 'products' developed in previous versions of the Framework). These views do not
require any particular graphical design by toolset vendors.
Authority: Law and Policy DoDAF Supports
Federal law and policies have expressed the need for architectures in support of business
4
DoDAF Introduction
http://cio-nii.defense.gov/sites/dodaf20/background.html[3/3/2011 3:33:50 PM]
decisions.
Policy/Guidance Description
Clinger-Cohen Act
of 1996
Recognizes the need for Federal Agencies to improve the way they
select and manage IT resources and states, “information technology
architecture, with respect to an executive agency, means an integrated
framework for evolving or maintaining IT and acquiring new IT to
achieve the agency’s strategic goals and information resources
management goals.” Chief Information Officers are assigned the
responsibility for “developing, maintaining, and facilitating the
implementation of a sound and integrated IT architecture for the
executive agency”.
E-Government
Act of 2002
Calls for the development of Enterprise Architecture to aid in enhancing
the management and promotion of electronic government services and
processes.
Office of
Management and
Budget Circular
A-130
“Establishes policy for the management of Federal information
resources” and calls for the use of Enterprise Architectures to support
capital planning and investment control processes. Includes
implementation principles and guidelines for creating and maintaining
Enterprise Architectures.
OMB Federal
Enterprise
Architecture
Reference Models
(FEA RM)
Facilitates cross-agency analysis and the identification of duplicative
investments, gaps, and opportunities for collaboration within and across
Federal Agencies. Alignment with the reference models ensures that
important elements of the FEA are described in a common and
consistent way. The DoD Enterprise Architecture Reference Models are
aligned with the FEA RM.
OMB Enterprise
Architecture
Assessment
Framework
(EAAF)
Serves as the basis for enterprise architecture maturity assessments.
Compliance with the EAAF ensures that enterprise architectures are
advanced and appropriately developed to improve the performance of
information resource management and IT investment decision making.