DoD Architecture Framework Version 1.5 - Chief Information Officer

architecture federation, net-centricity, executable architectures, and the full range of DOTMLPF
alternatives.
One critical component for the development of DoDAF v2.0 is an architecture conceptual
data model that provides a semantically complete, tool and methodology independent, holistic,
“architect’s view” for describing integrated DoD architectures. An “architect’s view” is an
architect’s view in formalizing and expressing an architecture description, and is independent of
modeling technology (structured or object-oriented) and source (i.e., commercially available
enterprise architecture tools and/or government developed applications). One example of an
approach for this architecture conceptual data model consists of a small, yet powerful, set of
descriptive concepts and a taxonomy for the DoD architecting community of interest that groups
architectural elements according to six interrogatives – WHO, WHERE, WHAT, WHY, WHEN,
and HOW. Together, these serve as a foundation for meeting new requirements and demands on
future integrated DoD architecture usage.
The goals of this next generation DoDAF are to (1) address current DoDAF limitations,
weaknesses, and deficiencies; (2) provide a data-centric approach to building, implementing, and
using integrated architectures; (3) enable “federation” of architectures; (4) capture sufficient
architectural detail for full DOTMLPF analysis; and (5) provide support for architecture-based
analysis and assessments that link directly to mission outcomes and objectives for the DoD core
processes.
2.4 DEVELOPMENT OF INTEGRATED ARCHITECTURES AND FEDERATED
ARCHITECTURES
2.4.1 Why Develop Architectures that Support Integration and Federation
The ability to integrate and/or federate architectures is essential for addressing enterprise
issues across a broad domain such as the DoD. It enables multiple groups to develop
architectures with the focus that best meets their immediate needs, while providing a means for
linking and relating those architectures to address issues that cross multiple areas. A single
architecture cannot sufficiently address the entire DoD and its diversity of missions to where all
of the various types of analyses, enabled by the architecture construct, are supported. The ability
to integrate and/or federate multiple architectures leads to a more robust construct for
understanding the enterprise. Policies pertaining to the GIG are currently being updated to
include specific direction on architecture, a portion of which reinforces this federation concept.
Integrating and/or federating architectures become necessary in a NCE. It plays a significant
role in both the development of the environment and the sharing of information. As the DoD
becomes increasingly networked, integrated and/or federated architectures become essential in
organizing the vast array of information and complex relationships. As an example, the
realization of the GIG will be accomplished through GIG Capability Increments. These
increments will define IT Capabilities to be achieved in a specific period of time. Federated
architecture data can be used to evaluate portfolios of existing systems and programs to make
decisions about changes or additions necessary to achieve the IT capabilities in each increment.
2.4.2 Development Considerations for Integrated Architectures
In order to develop integrated architecture descriptions, commonality in the entities or
objects represented in multiple views, and the relationships between those entities or objects
must be captured in the underlying data model. Examples of important commonalities include:
2-5