CV-7 Capability to Services MappingAdd to favorites
The CV-7 “Capability to Services Mapping” describes the mapping between the capabilities required and the services that enable those capabilities. It provides a bridge between capability analyzed using Capability Viewpoints (CV) and services analyzed using Service Viewpoint (SvcV). Specifically, it identifies how services can be performed using various available capability elements. It is similar in function to the SV-5a “Operational Activity to Systems Function Traceability Matrix” which maps system functions to operational activities. The capability to service mappings may include both situations where a service fully satisfies the desired capability and those where the service only partially meets the capability requirement.
The intended usage of the CV-7 includes:
- Tracing capability requirements to services
- Capability audit
A CV-7 shows which elements of capability may be utilized in support of specific services by means of a mapping matrix. If it is created as part of a strategic architecture (i.e., before the creation of supporting service models), it is recommended that the services used as part of the CV-7 are common functions. This model may be used indicate that an operational capability (perhaps reflecting a particular user requirement) does or does not fulfill the requirements for capability for a particular phase.
In principle, there could be a different CV-7 created for each phase of the capability development, or perhaps for different capability phasing scenarios. In most cases, it is considered that a single table can be constructed because the services that are most likely relevant to this model may be relatively high-level. If capabilities associated are generic (see CV-1 “Vision model”), then they should have a well understood relationship with a standard set of services and this relationship is unlikely to change over time.
This model is analogous to the SV-5a “Operational Activity to System Function Traceability Matrix” – but provides the interface between Capability and Service Models rather than Operational to System Models.
The CV-7 can have a tabular presentation. The rows can be the capabilities and the columns can be the services. An X indicates that the capability may be utilized in support of that service whereas a blank indicates that it does not. Alternatively, a date or phase can indicate that the capability may support that service by the date or phase indicated.
- The DoDAF descriptions in this website are very generic and are mostly taken from the DoDAF Architecture Framework website. Make sure you visit the actual website for the most update information and a more thorough explanation of each viewpoint.
- DoDAF Version 1.0, although outdated, has some good examples on how to construct AV’s, OV’s, and SV’s.
AcqLinks and References:
-  DoDAF Architecture Framework Version 2.02
- DoD Architecture Framework Working Group Version 1.0, Volume 1: Definition and Guideline, 9 Feb 04 (Old Version)
- DoD Architecture Framework Version 1.0, Volume 2: Product Description, 9 Feb 04 (Old Version)
- Website: DoDAF Architecture Framework – DoD Deputy Chief Information Officer
- Website: DoDAF Version 2.02 Journal
- Website: DoDAF Meta Model (DM2)
- Website: DoD Information Enterprise Architecture
- Website: OMB Enterprise Architecture Assessment Framework (EAAF)