供应 1MYN743217-A 74331458-AD 自动化控制卡

供应 1MYN743217-A 74331458-AD 自动化控制卡 

架构开发的主要重点已经从以产品为中心转变
流程到以数据为中心的流程，旨在提供有组织的决策数据
作为管理者的信息。
产品已被表示特定演示类型的视图所取代
建筑数据和衍生信息。随着对数据的关注，DoDAF V2.0
没有产品，但有DoDAF描述的模型。而不是操作性的
视点5（OV-5）作战活动模型产品，有活动模型
具有相同的支持数据。这将架构工作的重点转移到
架构开发过程早期的数据。
体系结构视图依次组织为视点，这些视点提供了广泛的
理解目的、目标、组成部分和能力
由各个建筑视图表示。
在先前版本中描述的架构的三个主要观点（例如。，
操作、技术和系统）已更改为更具体的观点
与架构相关数据的收集有关，这些数据可以组织为
为管理者决策提供有用信息。支持客户
需求和重组需求：
所有概念、逻辑或物理数据模型都已放置到
数据和信息观点。
技术标准观点已更新为标准
观点，可以描述商业、商业和理论标准
除了技术标准之外。
操作视点现在可以描述任何
功能（商业、情报、作战等），而不仅仅是那些
从数据关系。
由于部门内部强调能力、PfM和反馈
从采办社区、能力观点和项目观点
已添加。
8.
多达夫导言
http://cio-nii.defense.gov/sites/dodaf20/background.html[2011年3月3日下午3:33:50]
系统已从DoDAF 1.5版更改。系统不仅是计算机硬件，而且
计算机软件。系统现在被定义为一般意义上的
组件-机器、人员-执行活动（因为它们是
表演者），并且相互作用或相互依赖。这可以是任何东西。，
任何东西，从具有相互作用或相互依存的小型设备
要素、系统系列（FoS）和系统体系（SoS）。注意
系统由装备（如设备、飞机和船舶）组成
人员类型。
部门针对体系结构、联合和分层责任的举措包括：
已并入2.0版。
在联合环境中共享数据和派生信息的要求
描述。
已确定部门内的特定架构类型，以及
描述（例如，部门级[包括部门、能力&
组件架构]和解决方案架构）。
描述了国防部企业架构。
定义并描述了与联邦企业架构的链接。
初在英国国防部建筑中描述的建筑结构
框架（MODAF）、北约架构框架（NAF）和开放组
DoDAF中采用了架构框架（TOGAF）。
DoDAF元模型（DM2），包含概念数据模型（CDM），逻辑
数据模型（LDM）和物理交换规范（PES）。
描述和讨论了SOA开发的方法。
对于架构师来说，DoDAF V2.0改变了架构开发的重点
过程在“架构师需要做什么”中描述？基础
体系结构开发过程现在是数据元模型组，如

供应 1MYN743217-A 74331458-AD 自动化控制卡 

供应 1MYN743217-A 74331458-AD 自动化控制卡 

The major emphasis on architecture development has changed from a product-centric
process to a data-centric process designed to provide decision-making data organized
as information for the manager.
Products have been replaced by views that represent specific types of presentation for
architectural data and derived information. With the focus on data, DoDAF V2.0 does
not have products but has DoDAF-described Models. Rather than the Operational
Viewpoint-5 (OV-5) Operational Activity Model Product, there is the Activity Model
with the same supporting data. This is shifting the focus of the architecture effort onto
the data early in the Architecture Development Process.
Architecture views are, in turn, organized into viewpoints, which provide a broad
understanding of the purpose, objectives, component parts, and capabilities
represented by the individual architectural views.
The three major viewpoints of architecture described in previous version (e.g.,
Operational, Technical, and System) have been changed to more specific viewpoints
that relate to the collection of architecture-related data which can be organized as
useful information for the manager in decision-making. To support customer
requirement and re-organization needs:
All the models of data—conceptual, logical, or physical—have been placed into
the Data and Information Viewpoint.
The Technical Standards Viewpoint has been updated to the Standards
Viewpoint and can describe business, commercial, and doctrinal standards, in
addition to technical standards.
The Operational Viewpoint now can describe rules and constraints for any
function (business, intelligence, warfighting, etc.) rather that just those derived
from data relationships.
Due to the emphasis within the Department on Capability PfM and feedback
from the Acquisition community, the Capability Viewpoint and Project Viewpoint
have been added.
8
DoDAF Introduction
http://cio-nii.defense.gov/sites/dodaf20/background.html[3/3/2011 3:33:50 PM]
System has changed from DoDAF V1.5. System is not just computer hardware and
computer software. System is now defined in the general sense of an assemblage of
components - machine, human - that perform activities (since they are subtypes of
Performer) and are interacting or interdependent. This could be anything, i.e.,
anything from small pieces of equipment that have interacting or interdependent
elements, to Family of Systems (FoS) and System of Systems (SoS). Note that
Systems are made up of Materiel (e.g., equipment, aircraft, and vessels) and
Personnel Types.
The Department initiatives for Architecture Federation and Tiered Responsibility have
been incorporated into Version 2.0.
Requirements for sharing of data and derived information in a Federated environment
are described.
Specific types of architecture within the Department have been identified and
described (e.g., Department-level [which includes Department, Capability &
Component architectures] and Solution Architectures).
The DoD Enterprise Architecture is described.
Linkages to the Federal Enterprise Architecture are defined and described.
Architecture constructs originally described in the UK Ministry of Defence Architecture
Framework (MODAF), the NATO Architecture Framework (NAF), and the Open Group
Architecture Framework (TOGAF) are adopted for use within DoDAF.
A DoDAF Meta-model (DM2), containing a Conceptual Data Model (CDM), a Logical
Data Model (LDM), and a Physical Exchange Specification (PES) has been created.
Approaches to SOA development are described and discussed.
For the architect, DoDAF V2.0 changes the focus of the Architecture Developmenta
Process are described in “What Does the Architect Need to Do”? The basis of the
Architecture Development Process is now the Data Meta-model Groups, described in