Version , Change 1. Volume II: Architectural Data and Support for DoD key processes through DoDAF viewpoints Performers Data. DoDAF is the overarching, comprehensive framework and conceptual model enabling Guide: DoDAF Architecture Framework Version The Department of Defense Architecture Framework (DoDAF) is an architecture framework for . The current version is DoDAF DoDAF V is published on a public website. Other derivative frameworks based on DoDAF include the NATO.

Author: Daitilar Megore
Country: Saint Kitts and Nevis
Language: English (Spanish)
Genre: Photos
Published (Last): 28 October 2007
Pages: 124
PDF File Size: 14.20 Mb
ePub File Size: 19.81 Mb
ISBN: 979-1-86758-537-4
Downloads: 88906
Price: Free* [*Free Regsitration Required]
Uploader: Gumi

Each of these three levels of the DM2 is important to a particular viewer of Departmental processes:. It establishes data element definitions, rules, and relationships and a baseline set of products for consistent development of systems, integrated, or federated architectures.

The DoDAF Architecture Framework Version 2.02

Department of Defense for developing enterprise architecture has been debated:. Otherwise there is the risk of producing products with no customers.

Definitions and Guidelines”, “II: These products are organized under four views:. From Wikipedia, the free encyclopedia. The OV provides textual and graphical representations of operational nodes and elements, assigned tasks and activities, and information flows between nodes. These views relate to stakeholder dodav for producing an Architectural Description. 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.


The figure represents the information that links the operational view, systems and services view, and technical standards view. In other projects Wikimedia Commons. Integrated architectures are a property or design principle for architectures at all levels: It broadened the applicability of architecture tenets and practices to all Mission Areas rather than just the C4ISR community.

DoDAF Architecting Overview – AcqNotes

The repository is defined by the common database schema Core Architecture Data Model 2. Views Read Edit View history. The actual sequence of view generation and their potential customization is a function of the application domain and the specific needs of the effort.

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

The DoDAF Architecture Framework Version | CSIAC

It establishes a basis for semantic i. Node is a complex, logical concept that is represented with more concrete concepts. The dodat of capability, as defined by its Meta-model Data Group allows one to answer questions such as:. 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. The DM2 defines architectural data elements and enables the integration and federation of Architectural Descriptions.

As one example, the DoDAF v1.

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. Retrieved from ” https: Each view depicts certain perspectives of an architecture as described below.


Department of Defense Architecture Framework

While it is dodf aimed at military systems, DoDAF has broad applicability across the private, public and voluntary sectors around the world, and represents one of a large number of systems architecture frameworks.

One concern about the DoDAF is how well these products meet actual stakeholder concerns for any given system of interest. Only a subset of the full DoDAF viewset is usually created for each system development.

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. The developing system must not only meet its internal data needs but also those of the operational framework into which it is set.

It defines the type of information exchanged, the frequency of exchanges, the tasks and activities supported by these exchanges dodxf the nature of the exchanges. Operational View OV products provide descriptions of the tasks and activities, operational elements, and information exchanges required to accomplish DoD missions.

In April the Version 1.