NDBU-95C 64008366D NDBU95C 光纤适配器

 

NDBU-95C 64008366D NDBU95C 光纤适配器 

DoDAF V2.0侧重于架构“数据”，而不是开发单个“产品”
如先前版本中所述。通常，可以收集、组织和存储数据
通过商业来源开发的各种架构工具。预计
这些工具将采用DM2 PES来交换架构数据。
DoDAF V2.0为DM2的每个数据组提供了数据捕获方法，以指导
建筑师收集和组织必要的建筑数据。
DoDAF使“适合目的”的体系结构内容成为体系结构
与特定项目或任务目标一致的描述。因为
体系结构描述可以应用于企业、目的或用途的无数级别
每个层次的体系结构描述的内容、结构和层次都不同
细节调整体系结构描述开发，以解决特定的、清晰的和可理解的目的，将有助于确保在
支持特定决策或目标的适当详细程度。
通过模型（例如，所描述的产品）实现体系结构数据的可视化
在DoDAF的先前版本中）。模型可以是文档、电子表格、仪表板或
其他图形表示，并用作中组织和显示数据的模板
更容易理解的格式。当数据被收集并以“已填写”的形式呈现时
模型，结果称为视图。视图的有组织集合（通常表示
过程、系统、服务、标准等）称为视点，并
适当的定义统称为架构描述。
DoDAF V2.0讨论了DoDAF描述的模型和适用视图：
DoDAF描述的模型（也称为模型）是从
用于特定目的的数据子集。一旦DoDAF被描述，模型是
这些“视图”充满数据，可作为演示目的的示例，
并且可以根据需要进行描述、修改或定制。
出身背景
DoDAF的六个核心流程
支持
DM2对六核的支持
DoDAF支持的过程
DoDAF V2.0的新增功能
建筑发展
元模
观点和模型
展示技巧
配置管理
概述
缩略语列表和词汇表
术语
网站地图
档案
国防部
3.
多达夫导言
http://cio-nii.defense.gov/sites/dodaf20/background.html[2011年3月3日下午3:33:50]
适用视图是体系结构数据子集的用户定义视图
为特定目的而创建（即“适合目的”）。但这些观点并非如此
如DoDAF中所述或定义，可以根据需要创建它们，以确保
架构数据的表示易于理解。这使组织能够：
在他们的讨论中使用他们自己确定的演示偏好。
DoDAF中描述的模型，包括从先前版本
框架作为预定义示例提供，可在开发时使用
建筑数据的展示。
特定目的的特定DoDAF描述模型由流程所有者规定。
不必创建DoDAF描述的所有模型。如果创建了活动模型，则
活动模型需要一组必要的数据。关键流程所有者将决定什么
需要体系结构数据，通常通过DoDAF描述的模型或适合用途
意见。但是，国防部和主席的其他条例和指示
参谋长（CJC）有特定的演示视图要求。
架构师和涉众选择视图，以确保体系结构描述将
支持正在审查的过程或活动的当前和未来状态。选择
架构（Architecture）视点仔细确保视图充分地构建关注点，例如
以提高受众的方式解释需求和建议的解决方案
理解力
DoDAF还作为集成体系结构开发的主要指南
在国防部指令4630.8中定义，该指令将集成架构定义为
由多个视图或透视图组成的架构，便于集成和
促进跨能力和集成架构之间的互操作性”
集成意味着架构视图中多个实例所需的数据是
这些观点普遍理解这一点。
DM2提供了收集、组织和存储数据所需的信息
理解。

NDBU-95C 64008366D NDBU95C 光纤适配器 
 

NDBU-95C 64008366D NDBU95C 光纤适配器 

 

DoDAF V2.0 focuses on architectural "data", rather than on developing individual "products"
as described in previous versions. In general, data can be collected, organized, and stored
by a wide range of architecture tools developed by commercial sources. It is anticipated that
these tools will adopt the DM2 PES for the exchange of architectural data.
DoDAF V2.0 provides a Data Capture Method for each data group of the DM2 to guide
architects in collecting and organizing the necessary architectural data.
The DoDAF enables architectural content that is "Fit-for-Purpose" as an architectural
description consistent with specific project or mission objectives. Because the techniques of
architectural description can be applied at myriad levels of an enterprise, the purpose or use
of an architectural description at each level will be different in content, structure, and level of
detail. Tailoring the architectural description development to address specific, wellarticulated, and understood purposes, will help ensure the necessary data is collected at the
appropriate level of detail to support specific decisions or objectives.
Visualizing architectural data is accomplished through models (e.g., the products described
in previous versions of DoDAF). Models can be documents, spreadsheets, dashboards, or
other graphical representations and serve as a template for organizing and displaying data in
a more easily understood format. When data is collected and presented as a "filled-in"
model, the result is called a view. Organized collections of views (often representing
processes, systems, services, standards, etc.) are referred to as viewpoints, and with
appropriate definitions are collectively called the Architectural Description.
DoDAF V2.0 discusses DoDAF-described Models and Fit-for-Purpose Views:
DoDAF-described Models (also referred to as Models) are created from the
subset of data for a particular purpose. Once the DoDAF-described Models are
populated with data, these "views" are useful as examples for presentation purposes,
and can be used as described, modified, or tailored as needed.
Background
Six Core Processes DoDAF
Supports
DM2 Support for the Six Core
Processes DoDAF Supports
What is New in DoDAF V2.0
Architecture Development
Meta Model
Viewpoints & Models
Presentation Techniques
Configuration Management
Overview
Acronyms List and Glossary
of Terms
Site Map
Archives
Department of Defense
3
DoDAF Introduction
http://cio-nii.defense.gov/sites/dodaf20/background.html[3/3/2011 3:33:50 PM]
Fit-for-Purpose Views are user-defined views of a subset of architectural data
created for some specific purpose (i.e., "Fit-for-Purpose"). While these views are not
described or defined in DoDAF, they can be created, as needed, to ensure that
presentation of architectural data is easily understood. This enables organizations to
use their own established presentation preferences in their deliberations.
The models described in DoDAF, including those that are legacies from previous versions of
the Framework, are provided as pre-defined examples that can be used when developing
presentations of architectural data.
Specific DoDAF-described Models for a particular purpose are prescribed by process-owners.
All the DoDAF-described Models do not have to be created. If an activity model is created, a
necessary set of data for the activity model is required. Key process owners will decide what
architectural data is required, generally through DoDAF-described Models or Fit-for-Purpose
Views. However, other regulations and instructions from the DoD and the Chairman, Joint
Chiefs of Staff (CJCS) have particular presentation view requirements.
The architect and stakeholders select views to ensure that the Architectural Descriptions will
support current and future states of the process or activity under review. Selecting
Architecture Viewpoints carefully ensures that the views adequately frame concerns, e.g., by
explaining the requirements and proposed solutions, in ways that enhance audience
understanding.
DoDAF also serves as the principal guide for development of integrated architectures as
defined in DoD Instruction 4630.8, which defines an integrated architecture as "An
architecture consisting of multiples views or perspectives facilitating integration and
promoting interoperability across capabilities and among integrated architectures". The term
integrated means that data required in more than one instance in architectural views is
commonly understood across those views.
The DM2 provides information needed to collect, organize, and store data in a way easily
understood.