Section 1 is the Introduction to this volume. Section 2 .. These DoDAF data groups support both DoDAF viewpoints and the DoD key processes: the Joint. DoDAF Volume 2 describes the technical aspects of data collection presentation descriptions and DoDAF-described Models in Volumes 1 and 2 provide guidance DoDAFV is intended to be methodology agnostic. DoDAF Architecture Framework Version The Department of Defense Architecture Framework (DoDAF) is an architecture framework for . OV-1 High Level Operational Concept Graphic: High level graphical and .. DoDAF V · Printable version of DoDAF V Volume 1 · Printable version of DoDAF V Volume 2.

Author: Kigakinos Mizuru
Country: Namibia
Language: English (Spanish)
Genre: Life
Published (Last): 7 April 2011
Pages: 29
PDF File Size: 1.32 Mb
ePub File Size: 18.31 Mb
ISBN: 678-5-26103-364-9
Downloads: 83522
Price: Free* [*Free Regsitration Required]
Uploader: Nikom

Each of these three levels of the DM2 is important to a particular viewer of Departmental processes:. The repository is defined by the common database schema Core Architecture Data Model 2. Systems and services view SV is a set of graphical and textual products that describe systems and services and interconnections providing for, or supporting, DoD functions.

All view AV products provide overarching descriptions of the entire architecture and define the scope and context of the architecture. In addition to graphical representation, there is typically a requirement to provide metadata to the Defense Information Technology Portfolio Repository DITPR or other architectural repositories.

Product Descriptions” and doda “Deskbook”. The actual sequence of view generation and their potential customization is a dldaf of the application domain and the specific needs of the effort. Commons category link is on Wikidata. These views relate to stakeholder requirements for producing an Architectural Description. This Architecture Framework is especially suited to large systems with complex integration and interoperability challenges, and it is apparently unique in its employment of “operational views”.

These views offer overview and details aimed to specific stakeholders within their domain and in interaction with other domains in which the system will operate. By using this site, you agree to the Terms of Use and Privacy Policy. As the DM2 matures to meet the ongoing data requirements of process owners, decision makers, architects, and new technologies, it will evolve to a resource that more completely supports the requirements for architectural data, published in a consistently understandable way, and will enable greater ease for discovering, sharing, and reusing architectural data across organizational boundaries.


The relationship between architecture data elements across the SV to the OV can be exemplified as systems are procured and fielded to support organizations and their operations.

A capability thread would equate to the specific activities, rules, and systems that are linked to that particular capability. The concept of capability, as defined by its Meta-model Data Group allows one to answer questions such as:. The approach depends on the requirements and the expected results; i. As one example, 22.0 DoDAF v1.

The three views and their interrelationships — driven by common architecture data elements — provide the basis for deriving measures such as interoperability or performance, and for measuring the impact of the values of these metrics on operational mission and task effectiveness.

The DM2 defines architectural data elements and enables the integration and federation of Architectural Descriptions.

In simpler terms, integration is seen in the connection from items common among architecture products, where items shown in one architecture product such as sites used or systems interfaced or services provided should have the identical number, name, and meaning appear in related architecture product views. DoDAF has a meta-model underpinning the framework, defining the types of modelling elements that can be used in each view and the relationships between them.

In other projects Wikimedia Commons. The developing system must not only meet its internal data needs but also those of the operational framework into which it is set.

This page was last edited on 3 Octoberat It defines the type of information exchanged, the frequency of exchanges, the tasks and activities supported by these exchanges and fodaf nature of the exchanges.

DoD weapons and information technology system acquisitions are required to develop and document an enterprise architecture EA using the views prescribed in the DoDAF.

These views are artifacts for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabularstructuralbehavioralontologicalpictorialtemporalgraphicalprobabilisticor alternative conceptual means. From Wikipedia, the free encyclopedia. In this manner, the DM2 supports the exchange and reuse didaf architectural information among JCAs, Components, and Federal and Coalition partners, thus vokume the understanding and implementation of interoperability of processes and systems.


Each view depicts certain perspectives of an architecture as described below. United States Department of Defense information technology Enterprise architecture frameworks. The DoDAF provides a foundational framework for developing and representing architecture descriptions that ensure a common denominator for understanding, comparing, and integrating architectures across organizational, joint, and multinational boundaries.

Department of Defense Architecture Framework

The Ddodaf provides textual and graphical representations of operational nodes and elements, assigned tasks and activities, and information flows between nodes. The DoDAF deskbook provides examples in using traditional systems engineering and data engineering techniques, and secondly, UML format. 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.

Views Read Edit View history. It establishes data element definitions, rules, and relationships and a baseline set of products for consistent development of systems, integrated, or federated architectures. Node is a complex, logical concept that is represented with more concrete concepts.

TRAK Community :: Wiki :: DODAF

It establishes a basis for semantic i. It addressed the 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. Definitions and Guidelines”, “II: These products are organized under four views:. There are many different approaches for creating an integrated architecture using DoDAF and for determining which products are required.

The sequence of the artifacts listed below gives a suggested order in which the artifacts could be developed.