DoD Architecture Framework Version 1.5 - Chief Information Officer

More documents

Recommendations

Info

EXECUTIVE SUMMARY 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 and policy (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 large organizations employing sophisticated systems and technologies in pursuit of joint missions demands a structured, repeatable method for evaluating investments and investment alternatives, as well as the ability to effectively implement organizational change, create new systems, and deploy new technologies. Towards this end, the DoD Architecture Framework (DoDAF) was established as a guide for the development of architectures. (For the purposes of this document the terms DoDAF and framework are synonymous.) The DoDAF provides the guidance and rules for developing, representing, and understanding architectures based on a common denominator across DoD, Joint, and multinational boundaries. It provides insight for external stakeholders into how the DoD develops architectures. The DoDAF is intended to ensure that architecture descriptions can be compared and related across programs, mission areas, and, ultimately, the enterprise, thus, establishing the foundation for analyses that supports decision-making processes throughout the DoD. As the Department takes appropriate strides to ensure advancement of the Information Technology (IT) environment, it is essential for the DoDAF to transform to sufficiently support new technologies. A significant evolution occurring today is the Department’s transformation to a new type of information intensive warfare known as Net-Centric Warfare (NCW). NCW focuses on generating combat power from the effective linking or networking of the warfighting enterprise, and making essential information available to authenticated, authorized users when and 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. It applies essential net-centric concepts 1 in transforming the DoDAF and acknowledges that the advances in enabling technologies – such as services within a Service Oriented Architecture (SOA) – are fundamental to realizing the Department’s Net-Centric Vision. 2 Version 1.5 addresses the immediate net-centric architecture development needs of the Department while maintaining 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 the Core Architecture Data Model (CADM) as an integral component of the DoDAF. These aspects 1 Reference DoDAF v1.5 Volume II for further information on the following net-centric concepts and their application to DoDAF: 1) Populate the Net-Centric Environment, 2) Utilize the Net-Centric Environment, 3) Accommodate the Unanticipated User, 4) Promote the Use of Communities of Interest (COI), 5) Support Shared Infrastructure 2 2005 National Defense Strategy ES-1
prepare the way for more efficient and flexible use and reuse of architecture data, enabling broader utility for decision makers and process 3 owners. The DoDAF is a three-volume set that inclusively covers the concept of the architecture framework, 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 to capture development best practices, architecture analytical techniques, and showcase exemplar architectures. The DoDAF will continue to evolve (see Figure ES-1, Evolution of the DoDAF) to meet the growing 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 capabilities stemming from operational insights gained in Afghanistan and Iraq. As the maturation of the Global Information Grid (GIG) continues through GIG Capability Increments (an incremental time frame approach to the delivery of GIG-enabling capabilities), architectures will be a factor in evaluating increment investments, development, and performance at the mission portfolio levels. 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 the enterprise level. The DoDAF plays a critical role in the development of architectures and will continue to improve its support for the increasing uses of architecture data. 3 CJCS Instruction 3170.01E, Joint Capabilities Integration and Development System (JCIDS); DoD Directive 7045.14, Planning, Programming, Budgeting, and Execution (PPBE); DoD Directive 5000.1, The Defense Acquisition System (DAS); DoD Directive 8115.01, Information Technology Portfolio Management (PfM) ES-2
Page 1 and 2: wreath stars Text DoD Architecture
Page 3: 3.3 FACILITATING THE USE OF ARCHITE
Page 7 and 8: C4ISR Architecture Framework, Versi
Page 9 and 10: 1.2 SCOPE OF DODAF v1.5 NCO require
Page 11 and 12: Table 1-3: New Products for v1.5 Ne
Page 13 and 14: A federated architecture is a distr
Page 15 and 16: enables the incorporation of inform
Page 17 and 18: Applicable View Framework Product F
Page 19 and 20: 2 ARCHITECTURE DEVELOPMENT 2.1 ARCH
Page 21 and 22: Step 1: Determine Intended Use of A
Page 23 and 24: architecture federation, net-centri
Page 25 and 26: associated reference models, and ca
Page 27 and 28: 3 ARCHITECTURE USAGE 3.1 THE VALUE
Page 29 and 30: DoD policies and directives call fo
Page 31 and 32: Applicable Architecture Product Dat
Page 33 and 34: 4 GOVERNING, DEVELOPING, MAINTAININ
Page 35 and 36: ANNEX A GLOSSARY A&T ABM ASD(C3I) A
Page 37 and 38: PfM PPBE SIPRNET SOA SoS SV TA TV U
Page 39 and 40: Data Data Model Data-Entity* Defens
Page 41 and 42: Needline* Net-Centric Environment N
Page 43 and 44: ANNEX C REFERENCES [ADM, 2004] Arch
Page 45 and 46: http://www.bpmmag.net/ http://www-3

DoD Architecture Framework Version 1.5 - Chief Information Officer

Create successful ePaper yourself

Delete template?

Save as template?