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

DoDAF Viewpoints and Models

Capability Viewpoint - Capability Model Descriptions

CV-5: Capability to Organizational Development Mapping

The CV-5 addresses the fulfillment of capability requirements.

This model shows the planned capability deployment and interconnection for a particular phase. and should provide a more detailed dependency analysis than is possible using the CV-3 Capability Phasing model. The CV-5 is used to support the capability management process and, in particular, assist the planning of fielding.

The intended usage of the CV-5 includes:

  • Fielding planning.
  • Capability integration planning.
  • Capability options analysis.
  • Capability redundancy/overlap/gap analysis.
  • Identification of deployment level shortfalls.

Detailed Description:

The CV-5 shows deployment of Capabilities to specific organizations. CV-5 models are specific to a phase. If a particular Capability is/was used by (or is due to be used by) a specific organization during that phase, it should be shown on the CV-5, mapped to the organization. The CV-5 may also show interactions between them (where these have been previously defined in a SV-1 Systems Interface Description or SvcV-1 Services Context Description). The CV-5, along with SV-8 Systems Evolution Description, SvcV-8 Services Evolution Description and PV-2 Project Timelines models can be regarded as amplifying the information contained in the CV-3.

To conduct a comprehensive analysis, several CV-5s can be created to represent the different phases. Although the CV-5s are represented separately, Capabilities may exist in more than one model. The information used to create the CV-5 is drawn from other DoDAF-described Models (PV-2 Project Timelines, CV-2 Capability Taxonomy, OV-4 Organizational Relationships Chart, SV-1 Systems Interface Description, SvcV-1 Services Context Description), and the timing is based on PV-2 Project Timelines indicating delivery of Capabilities to actual organizational resources, and also the point at which those organizational resources cease to use a particular Capability.

System interaction (from the SV-1 Systems Interface Description) or Service interaction (from the SvcV-1 Services Context Description) can be shown on a CV-5. In addition, where a Capability or resources is deployed across a number of Organizations, a parent Organization can be created for context purposes, and the Capability or resource stretched across the domain of the parent Organization.

The architect should not overwhelm the diagram with capabilities and organizations. A CV-5 should be seen as a summary of the delivery schedules for capabilities (hence it could be argued that it belongs in the PV Viewpoint). To prevent constraining the solution space, CV-5 should not be produced at the time of developing capability/user requirements, but after the solution is determined. Instead, the CV-5 should be more of an informative from a programmatic standpoint.

The CV-5 is usually based on a tabular representation, with the appropriate Organizational structure represented by one axis, and the capabilities by the other axis. Graphical objects representing Capabilities or resources can be placed in the relevant positions (intersections) relative to these axes.

CV-1: Vision

CV-2: Capability Taxonomy

CV-3: Capability Phasing

CV-4: Capability Dependencies

CV-5: Capability to Organizational Development Mapping

CV-6: Capability to Operational Activities Mapping

CV-7: Capability to Services Mapping