DKH-E2201 DKH 2201 GAT532215R0101 伺服启动器

DKH-E2201 DKH 2201 GAT532215R0101 伺服启动器 

由各个建筑视图表示。
在先前版本中描述的架构的三个主要观点（例如。，
操作、技术和系统）已更改为更具体的观点
与架构相关数据的收集有关，这些数据可以组织为
为管理者决策提供有用信息。支持客户
需求和重组需求：
所有概念、逻辑或物理数据模型都已放置到
数据和信息观点。
技术标准观点已更新为标准
观点，可以描述商业、商业和理论标准
除了技术标准之外。
操作视点现在可以描述任何
功能（商业、情报、作战等），而不仅仅是那些
从数据关系。
由于部门内部强调能力、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改变了架构开发的重点
过程在“架构师需要做什么”中描述？基础
体系结构开发过程现在是数据元模型组，如
LDM。
为了与ISO标准保持一致，在适当的情况下，术语已从
视图到视点（例如，操作视图现在是操作视点）。
DoDAF可以捕获安全标记，并在PES中进行了描述。此外，a
已经讨论了映射到DoDAF概念的安全特性
补充。
在DoDAF V1.5及以前的版本中，节点是逻辑概念，在
架构的交流和讨论。在所审查的一个架构中，
映射到系统、组织、人员类型、设施、装备的作战节点，
和安装。在同一架构内，
物资、组织和位置。重叠的组织和系统节点
（系统、组织、材料）说明了尝试定义节点的复杂性。
节点的具体概念（包括活动、系统、组织、人员
类型、设施、位置、装备和安装）被纳入国防部发展战略框架
元模型。因为节点是逻辑概念，可以用来表示
活动、系统、组织、人员类型的更具体概念，
设施、位置、材料、装置或这些东西的组合，
DoDAF V2.0侧重于这些具体概念。将不存在节点的映射
到DoDAF V2.0元模型组、概念、类或关联。对于
架构师，架构开发中有一些变化：
适当时，使用节点的DoDAF V1.0和V1.5体系结构
概念将需要更新架构，以表达中的具体概念
节点表示的抽象概念的位置。在DoDAF V2.0之前
将体系结构与DoDAF V2.0体系结构进行比较
必须为较新的体系结构定义该节点表示的。
DoDAF V2.0体系结构将需要表达具体的概念（活动，
系统、组织、人员类型、设施、位置、材料和
安装等）。
9
体系结构框架

DKH-E2201 DKH 2201 GAT532215R0101 伺服启动器 

DKH-E2201 DKH 2201 GAT532215R0101 伺服启动器 

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 Development
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
the LDM.
To align with ISO Standards, where appropriate, the terminology has changed from
Views to Viewpoint (e.g., the Operational View is now the Operational Viewpoint).
DoDAF can capture the security markings and is described in the PES. In addition, a
discussion of the security characteristics mapped to the DoDAF Concepts has been
added.
In DoDAF V1.5 and previous versions, Nodes are logical concepts that caused issues in
the exchange and discussion of architectures. In one architecture that was reviewed,
Operational Nodes mapped to System, Organization, Person Type, Facility, Materiel,
and Installation. Within the same architecture, System Node maps to System,
Materiel, Organization, and Location. The overlap Organizational and System nodes
(System, Organization, Material) illustrates the complexity of trying to define Nodes.
The concrete concepts of Node (including Activities, System, Organization, Person
Type, Facility, Location, Materiel, and Installation) were incorporated into the DoDAF
Meta-model. Since Nodes are logical concepts that could be used to represent the
more concrete concepts of activities, systems, organizations, personnel types,
facilities, locations, materiels, and installations or combinations of those things,
DoDAF V2.0 focuses on those concrete concepts. There will not be a mapping of Node
to the DoDAF V2.0 Meta-model Groups, concepts, classes, or associations. For the
architect, there are some changes in architecture development:
When appropriate, DoDAF V1.0 and V1.5 architectures that use the Node
concept will need to update the architecture to express the concrete concepts in
place of the abstract concept that Node represents. When pre-DoDAF V2.0
architecture is compared with DoDAF V2.0 architecture, the concrete concepts
that Node represents must be defined for the newer architecture.
DoDAF V2.0 architectures will need to express the concrete concepts (activities,
systems, organizations, personnel types, facilities, locations, materiels, and
installations, etc.).
9
DoDAF Introduction
http://cio-nii.defense.gov/sites/dodaf20/background.html[3/3/2011 3:33:50 PM]
Go to top of page ↑
Privacy Policy | Web Policy |