DoD Architecture Framework Version 1.5 - Chief Information Officer

Applicable Architecture Product Data
Tech
All
Operational View (OV)
Systems and Services View (SV)
Stds
View
View
Uses of Architecture Data 1 2 1 2 3 4 5 6 7 1 2 3 4 5 6 7 8 9 10 11 1 2
Analysis & Assessment
Capabilities
- Gaps/Shortfalls • • •
- Mission Effects & Outcomes, Operational
Task Performance
• • • • • • • • • • •
- Trade-Offs • • • • • • • • • • • • • • • •
- Functional Solutions • • • • • • • • • • • • • • • •
Operations
- Process Re-engineering • • • • • •
- Personnel & Organizational Design • • • • • • • •
- Doctrine Development/Validation • • • • • • •
- Operational Planning (CONOPS and TTPs) • • • • • • • • •
Systems/Services
- Communications • • • • • •
- Interoperability and Supportability • • • • • • • • • • • •
- Evolution/Dependencies • • • • • • • • • •
- Materiel Solutions Design & Development • • • • • • • • • • • • • • •
- Facilities Packaging • • • • • • • • • •
- Performance • • • • •
Socialization/Awareness/Discovery
- Training • • • • • • • • • •
- Leadership Development • • • • • • • •
- Metadata (for federation) •
• = Data Highly Applicable
= Data is Often or Partially Applicable
= Data is Usually Not Applicable
Figure 3-1: Architecture Products by Use
Data visualization, the representation of architecture data that relates directly to decision
making architecture requirements, provides value through all tiers of the organization. It allows
one to represent data in a meaningful way for decision makers, while remaining consistent with
the CADM.
3.3 FACILITATING THE USE OF ARCHITECTURE
ASD(NII)/DoD CIO wishes to facilitate the use of integrated and federated architectures that
support decision makers in the warfighting, business, intelligence, and enterprise information
environment mission areas. The following sections provide a consistent manner in which to
facilitate the use of architecture at any tier in the organization.
3.3.1 Use the DoDAF
Architecture descriptions should use common and/or standardized terms and definitions. The
criticality of common language during architecture product creation, analysis, comparison, and
integration cannot be overemphasized. The control of vocabulary, to include the use of a
common language for product names, architecture data elements, and common system data
values, helps to minimize potential misrepresentations and misunderstanding of shared
information, and assists with architecture consistency and validation. The DoDAF defines a
standard for architecture data elements, their attributes, and their relationships. The Framework
requires that every architecture description contain an Integrated Dictionary (AV-2) that defines
terms used in the architecture to ensure semantic understanding across the enterprise.
3-5