7.2.3. The Use of Architecture

DEFENSE ACQUISITION GUIDEBOOK
Chapter 7 - Acquiring Information Technology

7.2.3. The Use of Architecture

7.2.3.1. Compliance with the DoD Enterprise Architecture (DoD EA)

7.2.3.2. Compliance with the DoD Information Enterprise Architecture (IEA)

7.2.3.3. DoD Chief Information Officer (CIO) Use of the DoD Information Enterprise Architecture (IEA)

7.2.3. The Use of Architecture

0. Architectures are tools to improve the operational processes, infrastructure, and materiel solutions of the Department. Architecture-enabled solutions should facilitate improved interoperability, better information sharing, tighter compliance, leaner processes, reduced costs, and more effective mission accomplishment.
0. The DoD Enterprise Architecture (EA) is a federation comprised of the DoD enterprise and DoD Component level architectures to guide investment portfolio strategies and decisions, define capability and interoperability requirements, establish and enforce standards, guide security and information assurance requirements across the Department of Defense, and provide a sound basis for transition from the existing environment to the future. Solutions should conform to the DoD EA.
0. Solution architectures should be developed for material and non-material initiatives and capabilities that deliver functionality for the DoD information enterprise.
0. All information technology investments, including those related to National Security Systems, should be reviewed for compliance with the DoD Enterprise Architecture and applicable approved solution architectures, and alignment with the Federal Enterprise Architecture (FEA).
0. An architecture is considered a strategic information asset and should be appropriately secured, shared and made available to any DoD user or mission partner to the maximum extent allowed by law and DoD policy.

7.2.3.1. Compliance with the DoD Enterprise Architecture (DoD EA)

Detailed compliance requirements for the DoD EA are contained in the DoD IEA. To comply with the DoD EA, an information technology (IT)-based initiative or an acquisition program, throughout its life cycle should:

• Follow the DoD Architecture Framework (DoDAF) guidance in creating architectural views. This guidance is met by creating an architecture that captures the specific data needed to support decision making. The specific data is predicated by explicitly identifying the intended use and scope of the architecture in question.
• Meet the DODAF Meta-model (DM2) Physical Exchange Specification (PES) requirements for sharing/reusing architecture data. This requirement is met through the program's creation of XML, based on the PES XSD for the necessary and foundational DM2 concepts and through contributing new reusable architecture data (if any) to the DM2.
• Meet the DoD Information Technology (IT) Standards Registry (DISR) requirements in selecting technologies and standards. This requirement is met by defining and implementing capabilities, based on technologies and standards contained within the DISR. Meeting this requirement should be validated at every milestone. When building systems, requests for proposals and contract statements of work should be reviewed as part of approved acquisition processes to ensure IT standards established in Initial Capabilities Documents, Capability Development Documents, and Capability Production Documents (Intelink account required) are translated into clear contractual requirements. In addition, requests for proposals and contract statements of work should contain additional requirements for contractors to identify instances where cost, schedule, or performance impacts may preclude the use of IT standards and GIG Technical Profiles mandated in DISR.
• Meet the DoD Net-Centric Data Strategy requirements and intent. Make explicit the data that is produced and used by the program's implemented operations. Provide the associated metadata, and define and document the program's data models. This requirement is met by:
  • Describing the metadata that has been registered in the DoD Data Metadata Registry for each data asset used and for each data asset produced (i.e., data for which the program is the Source Data Authority).
  • Providing the documented data models associated with the program.
• Comply with the DoD Information Enterprise Architecture (IEA).
• DTM 09-013, Registration of Architecture Description in the DoD Architecture Registry System (DARS) mandates the registration of architectures through the DARS portal so these architectures can be leveraged as information assets. Architectures developed in the DoD are more easily leveraged when they are widely visible and accessible across DoD. Widely visible and accessible architectures result in increased information sharing, reuse, and a more common understanding of the bigger picture. A fully federated EA can only be realized if all architectures in DoD are properly registered in DARS with appropriate links and relationships. DARS is located at https://intelshare.intelink.gov/sites/dars/default.aspx and includes a tutorial for the registration process.
• Mandatory Core Designated DoD Enterprise Services are common, globally-accessible services designated by the DoD CIO and mandated for use by all programs and initiatives. No capability comparable to the Mandatory Core Designated DoD ES is to be developed unless there is a waiver granted by the DoD CIO.

7.2.3.2. Compliance with the DoD Information Enterprise Architecture (IEA)

The DoD Information Enterprise Architecture (IEA) provides a common foundation to support transformation of the DoD to net-centric operations. The common foundation is presented as a set of Principles and Rules that guide and constrain operations to facilitate a coherent movement towards net-centric operations. Appendix D, Applying the DoD IEA, addresses how to apply the DoD IEA. Appendix E describes the compliance areas and content that demonstrates compliance with the DoD IEA.

7.2.3.3. DoD Chief Information Officer (CIO) Use of the DoD Information Enterprise Architecture (IEA)

The DoD CIO uses the DoD Information Enterprise Architecture (IEA) in all three of the major decision processes of the Department.

The DoD CIO uses the DoD IEA throughout the processes included in operating the Joint Capabilities Integration and Development System (JCIDS) to:

• Advise the Joint Requirements Oversight Council (JROC).
• Provide the basis for the development and refinement of joint enterprise and solution architectures by the Joint Staff and other DoD Components in support of the JCIDS.
• Develop assessments and provide recommendations to the Joint Requirements Oversight Council; the DoD IEA, including its concepts, products, data, conclusions, and implications provides a key source for these assessments.

TheDoD CIO uses the DoD IEA throughout the Planning, Programming, Budgeting and Execution (PPBE) process to:

• Review and provide recommendations for development of the Guidance for the Development of the Force and the Joint Programming Guidance.
• Provide recommendations to the Senior Level Review Group relating to Information Technology (IT) (including National Security Systems (NSS)), interoperability, and Information Assurance (IA).
• Review and evaluate Program Change Proposals and Budget Change Proposals relating to IT (including NSS), interoperability, and IA.
• Provide recommendations for Program Objective Memorandum planning and programming advice.

Finally, the DoD CIO uses the DoD IEA throughout the Defense Acquisition Process to:

• Inform and support his recommendations as a member the Defense Acquisition Board and his decisions as the Milestone Decision Authority for delegated acquisition programs.
• Review Information Support Plans and evaluate the interoperability, interoperability key performance parameters, and information assurance aspects of those plans.

Top of page