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: Nikor Zolobei
Country: Cyprus
Language: English (Spanish)
Genre: Travel
Published (Last): 18 March 2015
Pages: 227
PDF File Size: 9.63 Mb
ePub File Size: 13.11 Mb
ISBN: 333-2-49512-174-7
Downloads: 74015
Price: Free* [*Free Regsitration Required]
Uploader: Kazrarg

Operational View OV products provide descriptions of the tasks and activities, volme elements, and information exchanges required to accomplish DoD missions. Product Descriptions” and a “Deskbook”. One concern about the DoDAF is how well these products meet actual stakeholder concerns for any given system of interest.

Retrieved from ” https: SV products focus on specific physical systems with specific physical geographical locations.

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.

Department of Defense Architecture Framework

The concept of capability, as defined by its Meta-model Data Group allows one to answer questions such as:. There are many different approaches for creating an integrated architecture using DoDAF and for determining which products are required. These products are organized codaf four views:.

The figure represents the information that links the operational view, systems and services view, and technical standards view. The relationship between architecture data elements across dodat SV to the OV can be exemplified as systems are procured and fielded to support organizations and their operations.

To facilitate the use of information at the data layer, the DoDAF describes a set of models for visualizing data through graphic, tabular, or textual means. These architecture descriptions may include families of systems FoSsystems of systems SoSand net-centric capabilities for interoperating and interacting in the non-combat environment. 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.


As one example, the DoDAF v1. Commons category link is on Wikidata. 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.

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 rodaf enable greater ease for discovering, sharing, and reusing architectural data across organizational volkme.

The Department of Defense Architecture Framework DoDAF is an architecture framework for the United States Department of Defense DoD that provides visualization infrastructure for specific stakeholders concerns through viewpoints organized by various views.

A capability thread would equate to the specific activities, rules, and systems that are linked to that particular capability. The approach depends on the requirements and the expected results; i. The developing system must not only meet its internal data needs but also those of colume operational framework into which it is set.

In this manner, the DM2 supports the exchange and reuse of architectural information among JCAs, Components, and Federal and Coalition partners, thus facilitating the understanding and implementation of interoperability of processes volumd systems.

It defines the type of information exchanged, the frequency of exchanges, the tasks and activities supported by these exchanges and the nature of the exchanges. This document addressed usage, integrated architectures, DoD and Federal policies, value of architectures, architecture measures, DoD vklume support processes, development techniques, analytical techniques, and the CADM v1.


By using this site, you agree to the Terms of Use and Privacy Policy. Dodag sequence of the artifacts listed below gives a suggested order in which the artifacts could be developed. All view AV products provide overarching descriptions of the entire architecture and define the scope and context of the architecture.

TRAK Community :: Wiki :: DODAF

Only a subset of the full DoDAF viewset is usually created for each system development. The actual sequence of view generation and their potential customization is a function of the application domain and the specific needs of the effort.

Department of Defense for developing enterprise architecture doeaf been debated:. The DM2 defines architectural data elements and enables the integration and federation of Architectural Descriptions.

DoDAF generically describes in the representation of the artifacts to be generated, but allows considerable flexibility regarding the specific formats and modeling techniques. This Architecture Framework is especially suited dodf large systems with complex integration and interoperability challenges, and it is apparently unique in its employment of “operational views”.

It establishes data element definitions, rules, and relationships and a baseline set of products for consistent development of systems, integrated, or federated architectures. The three views and their interrelationships — driven by volumw 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.

DoD Business Systems Modernization: Integrated architectures are a property or design principle for architectures at all levels: It establishes a basis for semantic i. Definitions and Guidelines”, “II: United States Department of Defense information technology Enterprise architecture frameworks. From Wikipedia, doodaf free encyclopedia.