DODAF - DOD Architecture Framework Version 2.02 - DOD Deputy Chief Information Officer

Models

Model List

The DoDAF-described Models that are available in DoDAF V2.0 are listed in the table below. The list provides the possible models and is not prescriptive. The decision-maker and process owners will determine the DoDAF-described Models that are required for their purposes. The DoDAF-described Models are grouped into the following viewpoints:

  • All Viewpoint (AV)
  • Capability Viewpoint (CV)
  • Data and Information Viewpoint (DIV)
  • Operational Viewpoint (OV)
  • Project Viewpoint (PV)
  • Services Viewpoint (SvcV)
  • Standard Viewpoint (StdV)
  • Systems Viewpoint (SV)

DoDAF V2.0 Models

Models Descriptions
AV-1: Overview and Summary Information Describes a Project's Visions, Goals, Objectives, Plans, Activities, Events, Conditions, Measures, Effects (Outcomes), and produced objects.
AV-2: Integrated Dictionary An architectural data repository with definitions of all terms used throughout the architectural data and presentations.
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
CV-2: Capability Taxonomy A hierarchy of capabilities which specifies all the capabilities that are referenced throughout one or more Architectural Descriptions.
CV-3: Capability Phasing The planned achievement of capability at different points in time or during specific periods of time. The CV-3 shows the capability phasing in terms of the activities, conditions, desired effects, rules complied with, resource consumption and production, and measures, without regard to the performer and location solutions.
CV-4: Capability Dependencies The dependencies between planned capabilities and the definition of logical groupings of capabilities.
CV-5: Capability to Organizational Development Mapping The fulfillment of capability requirements shows the planned capability deployment and interconnection for a particular Capability Phase. The CV-5 shows the planned solution for the phase in terms of performers and locations and their associated concepts.
CV-6: Capability to Operational Activities Mapping A mapping between the capabilities required and the operational activities that those capabilities support.
CV-7: Capability to Services Mapping A mapping between the capabilities and the services that these capabilities enable.
DIV-1:Conceptual Data Model The required high-level data concepts and their relationships.
DIV-2: Logical Data Model The documentation of the data requirements and structural business process (activity) rules. In DoDAF V1.5, this was the OV-7.
DIV-3: Physical Data Model The physical implementation format of the Logical Data Model entities, e.g., message formats, file structures, physical schema. In DoDAF V1.5, this was the SV-11.
OV-1: High-Level Operational Concept Graphic The high-level graphical/textual description of the operational concept.
OV-2: Operational Resource Flow Description A description of the Resource Flows exchanged between operational activities.
OV-3: Operational Resource Flow Matrix A description of the resources exchanged and the relevant attributes of the exchanges.
OV-4: Organizational Relationships Chart The organizational context, role or other relationships among organizations.
OV-5a: Operational Activity Decomposition Tree The capabilities and activities (operational activities) organized in a hierarchal structure.
OV-5b: Operational Activity Model The context of capabilities and activities (operational activities) and their relationships among activities, inputs, and outputs; Additional data can show cost, performers, or other pertinent information.
OV-6a: Operational Rules Model One of three models used to describe activity (operational activity). It identifies business rules that constrain operations.
OV-6b: State Transition Description One of three models used to describe operational activity (activity). It identifies business process (activity) responses to events (usually, very short activities).
OV-6c: Event-Trace Description One of three models used to describe activity (operational activity). It traces actions in a scenario or sequence of events.
PV-1: Project Portfolio Relationships It describes the dependency relationships between the organizations and projects and the organizational structures needed to manage a portfolio of projects.
PV-2: Project Timelines A timeline perspective on programs or projects, with the key milestones and interdependencies.
PV-3: Project to Capability Mapping A mapping of programs and projects to capabilities to show how the specific projects and program elements help to achieve a capability.
SvcV-1 Services Context Description The identification of services, service items, and their interconnections.
SvcV-2 Services Resource Flow Description A description of Resource Flows exchanged between services.
SvcV-3a Systems-Services Matrix The relationships among or between systems and services in a given Architectural Description.
SvcV-3b Services-Services Matrix The relationships among services in a given Architectural Description. It can be designed to show relationships of interest, (e.g., service-type interfaces, planned vs. existing interfaces).
SvcV-4 Services Functionality Description The functions performed by services and the service data flows among service functions (activities).
SvcV-5 Operational Activity to Services Traceability Matrix A mapping of services (activities) back to operational activities (activities).
SvcV-6 Services Resource Flow Matrix It provides details of service Resource Flow elements being exchanged between services and the attributes of that exchange.
SvcV-7 Services Measures Matrix The measures (metrics) of Services Model elements for the appropriate time frame(s).
SvcV-8 Services Evolution Description The planned incremental steps toward migrating a suite of services to a more efficient suite or toward evolving current services to a future implementation.
SvcV-9 Services Technology & Skills Forecast The emerging technologies, software/hardware products, and skills that are expected to be available in a given set of time frames and that will affect future service development.
SvcV-10a Services Rules Model One of three models used to describe service functionality. It identifies constraints that are imposed on systems functionality due to some aspect of system design or implementation.
SvcV-10b Services State Transition Description One of three models used to describe service functionality. It identifies responses of services to events.
SvcV-10c Services Event-Trace Description One of three models used to describe service functionality. It identifies service-specific refinements of critical sequences of events described in the Operational Viewpoint.
StdV-1 Standards Profile The listing of standards that apply to solution elements.
StdV-2 Standards Forecast The description of emerging standards and potential impact on current solution elements, within a set of time frames.
SV-1 Systems Interface Description The identification of systems, system items, and their interconnections.
SV-2 Systems Resource Flow Description A description of Resource Flows exchanged between systems.
SV-3 Systems-Systems Matrix The relationships among systems in a given Architectural Description. It can be designed to show relationships of interest, (e.g., system-type interfaces, planned vs. existing interfaces).
SV-4 Systems Functionality Description The functions (activities) performed by systems and the system data flows among system functions (activities).
SV-5a Operational Activity to Systems Function Traceability Matrix A mapping of system functions (activities) back to operational activities (activities).
SV-5b Operational Activity to Systems Traceability Matrix A mapping of systems back to capabilities or operational activities (activities).
SV-6 Systems Resource Flow Matrix Provides details of system resource flow elements being exchanged between systems and the attributes of that exchange.
SV-7 Systems Measures Matrix The measures (metrics) of Systems Model elements for the appropriate timeframe(s).
SV-8 Systems Evolution Description The planned incremental steps toward migrating a suite of systems to a more efficient suite, or toward evolving a current system to a future implementation.
SV-9 Systems Technology & Skills Forecast The emerging technologies, software/hardware products, and skills that are expected to be available in a given set of time frames and that will affect future system development.
SV-10a Systems Rules Model One of three models used to describe system functionality. It identifies constraints that are imposed on systems functionality due to some aspect of system design or implementation.
SV-10b Systems State Transition Description One of three models used to describe system functionality. It identifies responses of systems to events.
SV-10c Systems Event-Trace Description One of three models used to describe system functionality. It identifies system-specific refinements of critical sequences of events described in the Operational Viewpoint.