DKH-E1201 DKH 1201 GAT532207R0101 控制主板

DKH-E1201 DKH 1201 GAT532207R0101 控制主板 

国防部架构框架（DoDAF）2.0版是
总体、全面的框架和概念模型
促进国防部各级管理人员能力的体系结构
通过跨公司的有组织信息共享，更有效地做出关键决策
部门、联合能力领域（JCA）、任务、组件和项目边界。
DoDAF是支持国防部首席信息的主要支柱之一
负责架构开发和维护的官员（CIO）
根据《克林格-科恩法案》的要求。DoDAF规定用于使用和开发
部门的架构描述。它还就以下方面提供了广泛的指导：
开发支持采用和执行网络中心服务的体系结构
在部门内。
国防部管理人员作为流程所有者，指定需求并控制开发
权限和责任范围内的架构。他们选择一名建筑师
体系结构开发团队根据
他们定义的需求。
国防部各组成部分预计将符合国防部发展框架内的体系结构
部门DoDAF一致性确保了信息和体系结构的重用
工件、模型和视点可以通过共同理解共享。
DoDAF V2.0侧重于架构“数据”，而不是开发单个“产品”
如先前版本中所述。通常，可以收集、组织和存储数据
通过商业来源开发的各种架构工具。预计
这些工具将采用DM2 PES来交换架构数据。
DoDAF V2.0为DM2的每个数据组提供了数据捕获方法，以指导
建筑师收集和组织必要的建筑数据。
DoDAF使“适合目的”的体系结构内容成为体系结构
与特定项目或任务目标一致的描述。因为
体系结构描述可以应用于企业、目的或用途的无数级别
每个层次的体系结构描述的内容、结构和层次都不同
细节调整体系结构描述开发，以解决特定的、清晰的和可理解的目的，将有助于确保在
支持特定决策或目标的适当详细程度。
通过模型（例如，所描述的产品）实现体系结构数据的可视化
在DoDAF的先前版本中）。模型可以是文档、电子表格、仪表板或
其他图形表示，并用作中组织和显示数据的模板
更容易理解的格式。当数据被收集并以“已填写”的形式呈现时
模型，结果称为视图。视图的有组织集合（通常表示
过程、系统、服务、标准等）称为视点，并
适当的定义统称为架构描述。
DoDAF V2.0讨论了DoDAF描述的模型和适用视图：
DoDAF描述的模型（也称为模型）是从
用于特定目的的数据子集。一旦DoDAF被描述，模型是
这些“视图”充满数据，可作为演示目的的示例，
并且可以根据需要进行描述、修改或定制

DKH-E1201 DKH 1201 GAT532207R0101 控制主板 

DKH-E1201 DKH 1201 GAT532207R0101 控制主板 

The Department of Defense Architecture Framework (DoDAF), Version 2.0 is the
overarching, comprehensive framework and conceptual model enabling the development of
architectures to facilitate the ability of Department of Defense (DoD) managers at all levels
to make key decisions more effectively through organized information sharing across the
Department, Joint Capability Areas (JCAs), Mission, Component, and Program boundaries.
The DoDAF serves as one of the principal pillars supporting the DoD Chief Information
Officer (CIO) in his responsibilities for development and maintenance of architectures
required under the Clinger-Cohen Act. DoDAF is prescribed for the use and development of
Architectural Descriptions in the Department. It also provides extensive guidance on the
development of architectures supporting the adoption and execution of Net-centric services
within the Department.
DoD managers, as process owners, specify the requirements and control the development of
architectures within their areas of authority and responsibility. They select an architect and
an architecture development team to create the architecture in accordance with the
requirements they define.
DoD Components are expected to conform to the DoDAF developing architectures within the
Department. DoDAF Conformance ensures reuse of information and that architecture
artifacts, models, and viewpoints can be shared with common understanding.
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