DoD Architecture Framework Version 1.5†
Volume I: Definitions and Guidelines†
- EAフレームワーク(EA Framework)
|Architecture: the structure of components, their relationships, and the principles and |
guidelines governing their design and evolution over time.
DoD Integrated Architecture Panel,1995, based on IEEE STD 610.12
Architectures within the Department of Defense (DoD) are created for a number of reasons.From a compliance perspective, the DoD’s development of architectures is compelled by law andpolicy (i.e., Clinger-Cohen Act, Office of Management and Budget (OMB) Circular A-130).From a practical perspective, experience has demonstrated that the management of largeorganizations employing sophisticated systems and technologies in pursuit of joint missionsdemands a structured, repeatable method for evaluating investments and investment alternatives,as well as the ability to effectively implement organizational change, create new systems, anddeploy new technologies. Towards this end, the DoD Architecture Framework (DoDAF) wasestablished as a guide for the development of architectures. (For the purposes of this documentthe terms DoDAF and framework are synonymous.)
The DoDAF provides the guidance and rules for developing, representing, and understandingarchitectures based on a common denominator across DoD, Joint, and multinational boundaries.It provides insight for external stakeholders into how the DoD develops architectures. TheDoDAF is intended to ensure that architecture descriptions can be compared and related acrossprograms, mission areas, and, ultimately, the enterprise, thus, establishing the foundation foranalyses that supports decision-making processes throughout the DoD.
As the Department takes appropriate strides to ensure advancement of the InformationTechnology (IT) environment, it is essential for the DoDAF to transform to sufficiently supportnew technologies. A significant evolution occurring today is the Department’s transformation toa new type of information intensive warfare known as Net-Centric Warfare (NCW). NCWfocuses on generating combat power from the effective linking or networking of the warfightingenterprise, and making essential information available to authenticated, authorized users whenand where they need it. This ability is at the heart of net-centricity and essential to achieving Net-Centric Operations (NCO).
DoDAF v1.5 is a transitional version that responds to the DoD’s migration towards NCW. Itapplies essential net-centric concepts in transforming the DoDAF and acknowledges that theadvances in enabling technologies – such as services within a Service Oriented Architecture(SOA) – are fundamental to realizing the Department’s Net-Centric Vision. Version 1.5addresses the immediate net-centric architecture development needs of the Department whilemaintaining backward compatibility with DoDAF v1.0.
In addition to net-centric guidance, DoDAF v1.5 places more emphasis on architecture data,rather than the products, introduces the concept of federated architectures, and incorporates theCore Architecture Data Model (CADM) as an integral component of the DoDAF. These aspectsprepare the way for more efficient and flexible use and reuse of architecture data, enablingbroader utility for decision makers and process owners.
The DoDAF is a three-volume set that inclusively covers the concept of the architectureframework, development of architecture descriptions, and management of architecture data.
- Volume I introduces the DoDAF framework and addresses the development, use, governance, and maintenance of architecture data.
- Volume II outlines the essential aspects of architecture development and applies the net-centric concepts to the DoDAF products.
- Volume III introduces the architecture data management strategy and describes the pre-release CADM v1.5, which includes the data elements and business rules for the relationships that enable consistent data representation across architectures.
An Online DoDAF Journal, hosted on the DoD Architecture Registry System (DARS) website(https://dars1.army.mil/IER/index.jsp), replaces the DoDAF v1.0 Desk Book and is designed tocapture development best practices, architecture analytical techniques, and showcase exemplararchitectures.
The DoDAF will continue to evolve (see Figure ES-1, Evolution of the DoDAF) to meet thegrowing needs of decision makers in a Net-Centric Environment (NCE). Going forward,architectures will need to capture the development of a new generation of net-centric capabilitiesstemming from operational insights gained in Afghanistan and Iraq. As the maturation of theGlobal Information Grid (GIG) continues through GIG Capability Increments (an incrementaltime frame approach to the delivery of GIG-enabling capabilities), architectures will be a factorin evaluating increment investments, development, and performance at the mission portfoliolevels. As the DoD increases its use of architecture data for decision-making processes,architects will need to understand how to aggregate the data for presentation purposes at theenterprise level. The DoDAF plays a critical role in the development of architectures and willcontinue to improve its support for the increasing uses of architecture data.