DODAF1.5VOLUMEI - CSDN文库

DODAF

5星 · 超过95%的资源需积分: 9 60 浏览量更新于2023-03-03 评论 1 收藏 1.19MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源评论

资源推荐

Volume I: Definitions and Guidelines

23 April 2007

Core Architecture Data Model

All View

Operational View

DoD Architecture Framework

Version 1.5

Text

star s

wr eath

TABLE OF CONTENTS

SECTION PAGE

EXECUTIVE SUMMARY ....................................................................................................ES-1

EVOLUTION OF THE DOD ARCHITECTURE FRAMEWORK (DODAF)................ES-3

1 INTRODUCTION..........................................................................................................1-1

1.1 VOLUME I PURPOSE AND INTENDED AUDIENCE ...........................................1-1

1.2 SCOPE OF DODAF V1.5 ...........................................................................................1-2

1.2.1 Net-Centric Architectures....................................................................................1-2

1.2.2 Integrated Architectures and Federated Architectures.........................................1-4

1.3 FRAMEWORK OVERVIEW .....................................................................................1-6

1.4 DODAF........................................................................................................................1-7

1.4.1 Data-Driven Requirements ..................................................................................1-7

1.4.2 Definition of the Operational View (OV)............................................................1-8

1.4.3 Definition of the Systems and Services View (SV).............................................1-8

1.4.4 Definition of the Technical Standards View (TV)...............................................1-9

1.4.5 Definition of the All-View (AV) .........................................................................1-9

1.5 DEFINITIONS OF BASELINE FRAMEWORK PRODUCTS .................................1-9

2 ARCHITECTURE DEVELOPMENT.........................................................................2-1

2.1 ARCHITECTURE GUIDELINES ..............................................................................2-1

2.1.1 Have a Purpose in Mind.......................................................................................2-1

2.1.2 Be Simple and Straightforward............................................................................2-1

2.1.3 Be Understandable Among Architecture Users...................................................2-1

2.1.4 Be Interoperable Across the DoD........................................................................2-1

2.1.5 Be Agile ...............................................................................................................2-2

2.2 6-STEP ARCHITECTURE DEVELOPMENT PROCESS.........................................2-2

2.3 METHODOLOGIES ...................................................................................................2-4

2.4 DEVELOPMENT OF INTEGRATED ARCHITECTURES AND FEDERATED

ARCHITECTURES ....................................................................................................2-5

2.4.1 Why Develop Architectures that Support Integration and Federation?...............2-5

2.4.2 Development Considerations for Integrated Architectures..................................2-5

2.4.3 Development Considerations for Federated Architectures..................................2-6

2.4.4 Development Considerations for Net-Centric Architectures...............................2-7

3 ARCHITECTURE USAGE..........................................................................................3-1

3.1 THE VALUE OF ARCHITECTURES – DIFFERENT USES FOR DIFFERENT

USERS.........................................................................................................................3-1

3.1.1 Federal and DoD Policy.......................................................................................3-2

3.2 HOW TO USE THE ARCHITECTURE.....................................................................3-3

3.2.1 Data Modeling and Visualization ........................................................................3-4

3.3 FACILITATING THE USE OF ARCHITECTURE...................................................3-5

3.3.1 Use the DoDAF....................................................................................................3-5

3.3.2 Use the CADM ....................................................................................................3-6

3.3.3 Use the DARS......................................................................................................3-6

4 GOVERNING, MAINTAINING, AND MANAGING ARCHITECTURES

THROUGH DATA ........................................................................................................4-1

4.1 ARCHITECTURE GOVERNANCE...........................................................................4-1

4.2 ARCHITECTURE MAINTENANCE AND MANAGEMENT.................................4-1

ANNEX A GLOSSARY ...........................................................................................................A-1

ANNEX B DICTIONARY OF TERMS.................................................................................. B-1

ANNEX C REFERENCES ......................................................................................................C-1

LIST OF FIGURES

FIGURE PAGE

FIGURE ES-1 EVOLUTION OF THE DODAF.................................................................................ES-4

FIGURE 1-1 INTEGRATED ARCHITECTURE AND FEDERATED ARCHITECTURE ............................... 1-5

FIGURE 1-2 ARCHITECTURE FRAMEWORK STRUCTURE................................................................1-7

FIGURE 1-3 LINKAGES AMONG VIEWS......................................................................................... 1-8

FIGURE 2-1 THE SIX-STEP PROCESS OF BUILDING AN ARCHITECTURE DESCRIPTION .................. 2-2

FIGURE 2-2 NCOW RM, DODAF V1.5, AND ARCHITECTURE RELATIONSHIP ............................. 2-8

FIGURE 3-1 ARCHITECTURE PRODUCTS BY USE........................................................................... 3-5

LIST OF TABLES

TABLE PAGE

ABLE 1-1: VOLUME I AUDIENCE ...............................................................................................1-1

ABLE 1-2: ORGANIZATION OF VOLUME I ...................................................................................1-1

ABLE 1-3: NEW PRODUCTS FOR V1.5 .........................................................................................1-4

TABLE 1-4: DODAF V1.5 ARCHITECTURE PRODUCTS ...............................................................1-10

TABLE 2-1: METHODOLOGIES ......................................................................................................2-4

ABLE 3-1: FEDERAL POLICY.......................................................................................................3-2

TABLE 3-2: DOD DECISION SUPPORT PROCESS............................................................................3-3

ABLE 3-3: DATA MODEL LEVELS...............................................................................................3-4

ES-1

EXECUTIVE SUMMARY

Architectures within the Department of Defense (DoD) are created for a number of reasons.

From a compliance perspective, the DoD’s development of architectures is compelled by law and

policy (i.e., Clinger-Cohen Act, Office of Management and Budget (OMB) Circular A-130).

From a practical perspective, experience has demonstrated that the management of large

organizations employing sophisticated systems and technologies in pursuit of joint missions

demands a structured, repeatable method for evaluating investments and investment alternatives,

as well as the ability to effectively implement organizational change, create new systems, and

deploy new technologies. Towards this end, the DoD Architecture Framework (DoDAF) was

established as a guide for the development of architectures. (For the purposes of this document

the terms DoDAF and framework are synonymous.)

The DoDAF provides the guidance and rules for developing, representing, and understanding

architectures based on a common denominator across DoD, Joint, and multinational boundaries.

It provides insight for external stakeholders into how the DoD develops architectures. The

DoDAF is intended to ensure that architecture descriptions can be compared and related across

programs, mission areas, and, ultimately, the enterprise, thus, establishing the foundation for

analyses that supports decision-making processes throughout the DoD.

As the Department takes appropriate strides to ensure advancement of the Information

Technology (IT) environment, it is essential for the DoDAF to transform to sufficiently support

new technologies. A significant evolution occurring today is the Department’s transformation to

a new type of information intensive warfare known as Net-Centric Warfare (NCW). NCW

focuses on generating combat power from the effective linking or networking of the warfighting

enterprise, and making essential information available to authenticated, authorized users when

and where they need it. This ability is at the heart of net-centricity and essential to achieving Net-

Centric Operations (NCO).

DoDAF v1.5 is a transitional version that responds to the DoD’s migration towards NCW. It

applies essential net-centric concepts

in transforming the DoDAF and acknowledges that the

advances in enabling technologies – such as services within a Service Oriented Architecture

(SOA) – are fundamental to realizing the Department’s Net-Centric Vision.

Version 1.5

addresses the immediate net-centric architecture development needs of the Department while

maintaining backward compatibility with DoDAF v1.0.

In addition to net-centric guidance, DoDAF v1.5 places more emphasis on architecture data,

rather than the products, introduces the concept of federated architectures, and incorporates the

Core Architecture Data Model (CADM) as an integral component of the DoDAF. These aspects

Reference DoDAF v1.5 Volume II for further information on the following net-centric concepts and their application to DoDAF: 1) Populate

the Net-Centric Environment, 2) Utilize the Net-Centric Environment, 3) Accommodate the Unanticipated User, 4) Promote the Use of

Communities of Interest (COI), 5) Support Shared Infrastructure

2005 National Defense Strategy

Architecture: the structure of components, their relationships, and the principles and

guidelines governing their design and evolution over time.

DoD Integrated Architecture Panel,

1995, based on IEEE STD 610.12

ES-2

prepare the way for more efficient and flexible use and reuse of architecture data, enabling

broader utility for decision makers and process

owners.

The DoDAF is a three-volume set that inclusively covers the concept of the architecture

framework, development of architecture descriptions, and management of architecture data.

• Volume I introduces the DoDAF framework and addresses the development,

use, governance, and maintenance of architecture data.

• Volume II outlines the essential aspects of architecture development and

applies the net-centric concepts to the DoDAF products.

• Volume III introduces the architecture data management strategy and

describes the pre-release CADM v1.5, which includes the data elements and

business rules for the relationships that enable consistent data representation

across architectures.

An Online DoDAF Journal, hosted on the DoD Architecture Registry System (DARS) website

(https://dars1.army.mil/IER/index.jsp), replaces the DoDAF v1.0 Desk Book and is designed to

capture development best practices, architecture analytical techniques, and showcase exemplar

architectures.

The DoDAF will continue to evolve (see Figure ES-1, Evolution of the DoDAF) to meet the

growing needs of decision makers in a Net-Centric Environment (NCE). Going forward,

architectures will need to capture the development of a new generation of net-centric capabilities

stemming from operational insights gained in Afghanistan and Iraq. As the maturation of the

Global Information Grid (GIG) continues through GIG Capability Increments (an incremental

time frame approach to the delivery of GIG-enabling capabilities), architectures will be a factor

in evaluating increment investments, development, and performance at the mission portfolio

levels. As the DoD increases its use of architecture data for decision-making processes,

architects will need to understand how to aggregate the data for presentation purposes at the

enterprise level. The DoDAF plays a critical role in the development of architectures and will

continue to improve its support for the increasing uses of architecture data.

CJCS Instruction 3170.01E, Joint Capabilities Integration and Development System (JCIDS); DoD Directive 7045.14, Planning,

Programming, Budgeting, and Execution (PPBE); DoD Directive 5000.1, The Defense Acquisition System (DAS); DoD Directive 8115.01,

Information Technology Portfolio Management (PfM)

剩余45页未读，继续阅读

twq1108

2012-08-09

我们老师布置的翻译作业内容是没错的

sunmolin_cn

粉丝: 2
资源: 2

会员权益专享

DODAF1.5 VOLUME I

评论2

会员权益专享

最新资源

DODAF1.5 VOLUME I

评论2

DoDAF1.5_Volume_I.pdf

Telelogic Rhapsody 7.4 crack

DoDAF V1.5 卷3

DoDAF框架和UAF框架

dodaf 微服务架构

军事领域里面向系统架构设计的重要框架有哪些，介绍一下

cameo systems modeler

DODAF1.5 第1-3卷

最新版dodaf 2-02

Xabber客户端.zip

XUI-master.zip

基于背向散射的超声骨密度仪算法研究和软件设计的任务书.docx

机械毕业设计81五自由度机械臂设计.doc

数据可视化-上海各地区风速热力图

侧边栏滑动.zip

RBF神经网络概述.doc

游戏植物大战僵尸（经典版）

社会工程优化器 (SEO) 元启发式优化算法matlab代码.zip

基于s7200自动售货机-plc-控制.doc

基于深度学习方法去评估锂电池健康状态（SOH）python源码.zip

会员权益专享

最新资源