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. The DoD Architecture Framework (DoDAF) Version facilitates the ability of Department of Defense (DoD) managers at all levels to make key decisions more . 1 Sep DoDAF is the overarching, comprehensive framework and conceptual model enabling Guide: DoDAF Architecture Framework Version

Author: Duzil Shagal
Country: Lebanon
Language: English (Spanish)
Genre: Literature
Published (Last): 27 April 2009
Pages: 26
PDF File Size: 1.32 Mb
ePub File Size: 3.19 Mb
ISBN: 675-1-58618-383-8
Downloads: 41193
Price: Free* [*Free Regsitration Required]
Uploader: Tor

Dkdaf View OV products provide descriptions of the doddaf and activities, operational elements, and information exchanges required to accomplish DoD missions. The Views described in DoDAF, including those that are legacy Views from previous versions of the Framework, are provided as pre-defined examples that can be used when developing presentations of architectural data. The approach depends on the requirements and the expected results; i. 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.

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 dodaaf views. These architecture descriptions may include families of systems FoSsystems of systems SoSand net-centric capabilities for interoperating and interacting in the non-combat environment. 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 dodac C4ISR capabilities were interoperable and met the needs of the warfighter.

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 – Wikipedia

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. There are many different approaches for creating an integrated architecture using DoDAF and for determining which products are required.

These views offer overview and details aimed to specific .202 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.


The repository is defined by the common database schema Core Architecture Data Model 2. These products are organized under four views:. DoDAF does not prescribe any particular Views, but instead concentrates on data as the necessary ingredient for architecture development. In other projects Wikimedia Commons. As one example, the DoDAF v1. The developing system must not only meet its internal data needs but also those of the operational framework into which it is set.

It broadened the applicability of architecture tenets and practices to all Mission Areas rather than just the C4ISR community.

A presentation 2.20 these viewpoints is portrayed in graphic format below: Retrieved from ” https: For the purposes of architecture development, the term integrated means that data required in more than one of the architectural models is commonly defined and understood across those models. Definitions and Guidelines”, “II: To assist decision-makers, DoDAF provides the means of abstracting essential information from the underlying complexity and presenting it in a way that maintains coherence and consistency.

DoDAF Architecting Overview – AcqNotes

It establishes a basis for semantic i. 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 dodat. The approach to the presentation of Architectural Description moves away from static and rigid one-size-fits-all templates of architecture portrayals for architects. Integrated architectures are a property or design principle for architectures at all levels: Node is a complex, logical concept that is represented with more concrete concepts.

The DoDAF deskbook provides examples in using traditional systems engineering and data engineering techniques, and secondly, UML format. doaf

The Services portion of the older Systems and Services Viewpoint is now a Services Viewpoint that addresses in more detail our net-centric or services-oriented implementations. From Wikipedia, the free encyclopedia.

Department of Defense Architecture Framework

The Project Viewpoint also details dependencies among capability and operational requirements, system engineering processes, systems design, and services design within the Defense Acquisition System process. The Capability Models describe capability taxonomy and capability evolution. The presentational aspects should not overemphasize the pictorial presentation at the expense of the underlying data.

The viewpoints categorize the models as follows: DoDAF generically describes in the representation of the artifacts to be generated, but allows considerable flexibility regarding the specific formats and modeling techniques. Otherwise there is the risk of producing products with no customers.


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

It defines the type of information exchanged, the frequency of exchanges, the tasks and activities didaf by these exchanges and the nature of the exchanges. 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.

Views Read Edit View history. 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. Each viewpoint has a particular purpose, and usually presents one or combinations of the following: One concern about the DoDAF is how well these products meet actual stakeholder concerns for any given system of interest.

Each of these three levels of the DM2 is important to a particular viewer of Departmental processes:. The OV provides textual and graphical representations of operational nodes and elements, assigned tasks and activities, and information flows between nodes.

The 202 we have coined is “Fit-for-Purpose” presentation. The three views and their interrelationships — driven by common architecture data elements — provide the basis for dodav measures such as interoperability or performance, and for measuring the impact of the values of these metrics on operational mission and task effectiveness. The actual sequence of view generation and their potential customization is a function of the application domain and the specific needs of the effort.

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