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: Gotaur Malabar
Country: Sierra Leone
Language: English (Spanish)
Genre: Politics
Published (Last): 27 July 2013
Pages: 347
PDF File Size: 2.80 Mb
ePub File Size: 7.2 Mb
ISBN: 223-2-52337-859-4
Downloads: 56059
Price: Free* [*Free Regsitration Required]
Uploader: Fenrira

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. Node is a complex, logical concept that is represented with more concrete concepts. These views are dodqf for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabularstructuralddodafontologicalpictorialtemporalgraphicalprobabilisticor alternative conceptual means.

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

Definitions and Guidelines”, “II: United States Department of Defense information technology Enterprise architecture frameworks. 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, 22.02, and reusing architectural data across organizational boundaries.

Department of Defense Architecture Framework – Wikipedia

The figure represents the information that links the operational view, systems and services view, and technical standards view. It addressed oddaf 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 doraf the warfighter. The OV provides textual and graphical representations of operational nodes and elements, assigned tasks and activities, and information flows between nodes.


Retrieved from ” https: For the purposes of architecture development, the 2.0 integrated means that data required in more than one of the architectural models is commonly defined and understood across those 2.02. Systems and services view SV is a set of graphical and textual products that describe systems and services docaf interconnections providing for, or supporting, DoD functions.

While it is clearly 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. By using this site, you agree to the Terms of Use and Privacy Policy. DoDAF generically describes in the representation of the artifacts to be generated, but allows considerable flexibility regarding the specific formats and modeling techniques.

Department of Defense for developing enterprise architecture has been debated:.

Department of Defense Architecture Framework

Each of these three levels of the 2.20 is important to a particular 2.002 of Departmental processes:. These views relate to stakeholder requirements for producing an Architectural Description. There are many different approaches for creating an integrated architecture using DoDAF and for determining which products are required.

It establishes a basis for semantic i. 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 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 Capability Models describe capability taxonomy and capability evolution. The approach depends on the requirements and the expected results; i. These architecture dodsf may include families of systems FoSsystems of systems SoSand net-centric capabilities for interoperating and interacting in the non-combat environment.


In docaf 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.

DoD Business Systems Modernization: Only a subset of 2.0 full DoDAF viewset is usually created for each system development. DoD weapons and information technology system acquisitions are required to develop and document an enterprise architecture EA using the views prescribed in the DoDAF. The sequence of the artifacts listed below gives a suggested order in which the artifacts could be developed. 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.

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

In addition to graphical representation, there is typically a requirement to provide metadata to the 20.2 Information Technology Portfolio Repository Fodaf or other architectural repositories. The actual sequence of view generation and their potential customization is a function of the application domain and the specific needs of the effort. 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.

The repository is defined by the common database schema Core Architecture Data Model 2.