The Department Of Defense Architecture Framework

Published Date: 02 Nov 2017

DoDAF defines a set of views that act as mechanisms for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular, structural, behavioral, ontological, pictorial, temporal or graphical means. It is especially suited to large systems with complex integration and interoperability challenges, and is apparently unique in its use of "operational views" detailing the external customer's operating domain in which the developing system will operate. Three related views of DoDAF architecture:

Operational view (OV)

Systems View (SV)

Technical Standards (TV)

-->Operational view (OV) – description of the tasks and activities, operational elements and information exchanges required to accomplish the mission

-->Systems View (SV) – a set of graphical and textual products that describes systems and interconnect- ions providing for, or supporting DoD functions

-->Technical Standards (TV) – set of rules governing the arrangement, interactions and interdependence of system parts or elements.

C:\Documents and Settings\Admin\Desktop\320px-DoD_Architecture_Framework.jpg

EVOLUTION OF THE DOD ARCHITECTURE FRAMEWORK

PAST

C4ISR Architecture Framework v1.0, 7 June 1996

The Command, Control, Communications, Computers, and Intelligence, Surveillance, and

Reconnaissance (C4ISR) Architecture Framework v1.0 was created in response to the passage of

the Clinger-Cohen Act and addressed in the 1995 Deputy Secretary of Defense directive that a

DoD-wide effort be undertaken to define and develop a better means and process for ensuring

that C4ISR capabilities were interoperable and met the needs of the warfighter.

C4ISR Architecture Framework v2.0, 18 December 1997

The C4ISR Architecture Framework v2.0 was the result of the continued development effort

by the C4ISR Architecture Working Group and was mandated for all C4ISR architecture

descriptions in a February 1998 memorandum by the Architecture Coordination Council, cochaired by the Under Secretary of Defense for Acquisition and Technology (USD[A&T]), the

Assistant Secretary of Defense for Command, Control, Communications, and Intelligence

(ASD[C3I]), and the Command, Control, Communications, and Computer Systems Directorate,

Joint Staff (J6).

DoD Architecture Framework v1.0, 30 August 2003

The DoDAF v1.0 restructured the C4ISR Framework v2.0 to offer guidance, product

descriptions, and supplementary information in two volumes and a Desk Book. It broadened the

applicability of architecture tenets and practices to all Mission Areas rather than just the C4ISR

community. This document addressed usage, integrated architectures, DoD and Federal policies,

value of architectures, architecture measures, DoD decision support processes, development

techniques, analytical techniques, and the CADM v1.01, and moved towards a repository-based

approach by placing emphasis on architecture data elements that comprise architecture products.

PRESENT

DoD Architecture Framework, v1.5, 23 April 2007

The DoDAF v1.5 is an evolution of the DoDAF v1.0 and reflects and leverages the

experience that the DoD Components have gained in developing and using architecture

descriptions. This transitional version provides additional guidance on how to reflect net-centric

concepts within architecture descriptions, includes information on architecture data management

and federating architectures through the Department, and incorporates the pre-release CADM

v1.5, a simplified model of previous CADM versions that includes net-centric elements.

FUTURE

DoD Architecture Framework v2.0, TBD

The DoDAF v2.0 is currently being scoped to include further guidance on planning,

developing, managing, maintaining, and governing architectures through a coherent semantic

and structural meta model. This version will place greater emphasis on a "data-centric" approach

that facilitates the use of architecture by a wider variety of decision makers and will include

additional information on federation for improved enterprise decisions.

C:\Documents and Settings\Admin\Desktop\800px-DoDAF_Evolution.jpg

Purpose and Scope

The DoDAF provides the guidance needed to establish a common vocabulary for architecture development, for the exchange of architecture information, and for facilitating interoperability between Architectural Descriptions. Architectures are created for a number of reasons, ---from a compliance perspective, DoD development of architectures is compelled by law and policy.

-- From a practical perspective, the management of large organizations employing sophisticated

systems, technologies, and services in pursuit of complex joint missions demands a structured, repeatable method for evaluating investments and investment alternatives, as well as the ability to implement organizational change effectively, create new systems, deploy new technologies, and offer services which add value to decisions and management practices.

Guidance provided by DoDAF V2.0 applies to all architectures developed, maintained, and used within the DoD. The DoDAF also provides the foundational constructs to support the concept of architecture federation at each tier, enabling the sharing of all pertinent architecture information, and facilitates creation of the federated version of the DoD Enterprise Architecture. DoDAF V2.0 provides guidance in all areas of the architecture lifecycle, consistent with both DoD and OMB Guidance (i.e., Development, Maintenance, and Use of Architectures).It is the foundation for long-term administration and management of architectural data, and its accompanying models , views, and consolidated viewpoints that compose the presentation capability of an architecture.

DoDAF V2.0 also supports the concept of SOA development. Volume 1 provides management guidance on development of architectural views and viewpoints, based on service requirements. Volume 2 provides the technical information needed, data views, and other supporting resources for development of services-based architectures

What is New in DoDAF V2.0

The major changes for DoDAF V2.0 Volume 1 are:

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.

• 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.

• Products have been replaced by views that represent specific types of presentation for

architectural data and derived information.

• 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 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 defined and described.

• Linkages to the Federal Enterprise Architecture are defined and described.

• Architecture constructs originally described in the UK Ministry of Defense Architecture

Framework (MODAF), the NATO Architecture Framework (NAF), and the Open Group

Architecture Framework (TOGAF) are adopted for use within DoDAF.

• A DM2, containing a CDM, a LDM, and a PES has been created.

• Approaches to SOA development are described and discussed.

Differences between (ADD) and MODAF

ADD ( Attribute-Driven design )

DODAF (Department of Defense Architecture Framework )

It’s a recursive method consists of 2 parts:

using tactics to achieve quality requirements:

make sure there is enough requirements information

decide which part of the system that will be decomposed

identify candidates architectural drivers

documenting decomposition:

instantiate architectural elements and assign responsibilities

define interfaces for the instantiated elements

verify requirements and define constraints for the instantiated elements

repeat all of the above steps for each element

DODAF consists of a set of rules and templates, known as Views that, when its established, it shows a graphical and textual visualization of the business being investigated. The Views are divided into 7 categories:

Operational view (OV) – description of the tasks and activities, operational elements and information exchanges required to accomplish the mission.

Systems View (SV) – a set of graphical and textual products that describes systems and interconnect- ions providing for, or supporting DoD functions

Technical Standards (TV) – set of rules governing the arrangement, interactions and interdependence of system parts or elements