DoD Architecture Framework Version 1.5 - Chief Information Officer

1.2 SCOPE OF DODAF v1.5
NCO requires that information and the ability to share information when it is needed, where
it is needed, and with those who need it is critical to enabling transformation. The DoDAF V1.5
supports transformation goals by providing net-centric guidance for describing architecture
artifacts consistently across all mission operations and processes, and enabling the integration
and/or federation of architectures in support of joint capabilities. DoDAF v1.5 begins to
transition its focus away from architecture products (“product-centric”) as seen in v1.0 and aims
toward a greater emphasis on architecture data (“data-centric”). A “data-centric” approach
provides a more flexible and adaptable framework for architecting net-centric, integrated, and/or
federated architectures.
Version 1.5 is the first phase in transforming the DoDAF and is intended to address concerns
and desires from the architecture community in a timely manner, while allowing for more
revolutionary improvements in subsequent releases. More complex and substantial topics being
scoped for subsequent DoDAF versions include:
• Robust inclusion/enhancements to address SOA
• Increased guidance on describing changes in culture, doctrine, and processes
resulting from NCO
• Increased support for data-centric architecture management, including data
visualization via extractions to address decision system support and portfolio
management (PfM) activities
• Additional guidance and examples to better address the development and use
of Enterprise Architecture in aligning with the Federal and DoD Enterprise
Architectures 6
• Streamlining of the architecture development process to enable more rapid
fielding and agility
• Other fundamental architecture issues, such as security, systems engineering,
tools, and methodology recommendations
1.2.1 Net-Centric Architectures
In the March 2005 National Defense Strategy, the DoD restated its commitment towards netcentricity
and NCO. In this paradigm, the NCE, and its associated information and capabilities,
are leveraged as a key component for carrying out missions. The GIG, the “globally
interconnected, end-to-end set of information, capabilities, associated processes, and personnel
for collecting, processing, storing, disseminating, and managing information on demand to
warfighters, policy makers, and support personnel” is the foundation for this environment.
Because of this shift towards net-centricity and the need to effectively develop and manage the
GIG, it becomes necessary for architectures to consistently capture net-centric concepts so as to
afford their accountability in transition planning, implementation, and decision making.
Consistent representation of net-centric concepts aligns with the goals of integrated and/or
federated architectures.
6 Department of Defense Enterprise Architecture, http://www.army.mil/escc/cpi/refmod4b.htm
1-2