Capability Viewpoint (CV)Add to favorites
The Capability Viewpoint (CV) describes the taxonomy and capability evolution. It’s provides visualizations of the evolving capabilities so that Portfolio Managers can synchronize the introduction of capability increments across a portfolio of projects. The Capability Models included within DoDAF are based on the program and capability information used by Portfolio Managers to capture the increasingly complex relationships between interdependent projects and capabilities.
There are seven (7) Capability Viewpoints:
- 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
The reason for CV is the increasing importance of transformational programs within the DoD (e.g., Global Exchange [GEX], Defense Acquisition Initiative [DAI]). These types of programs are focused on the delivery of capabilities and do not conform to the standard for project management and tend to be benefit-driven rather than capability delivery focused. An ability to view these transformational programs, and their interdependencies, provides a potentially powerful tool for DoD Enterprise Architects.
The CV’s are intended to provide support to various decision processes within the Department, one of which is portfolio management. Since the DoD has moved toward the delivery of capabilities, these models take on a more important role. Developing an architecture that includes the relationships necessary to enable a capability thread is essential to improving usability of architectures.
The concept of capability, as defined by its Meta-model Data Group allows one to answer questions such as:
- How does a particular capability or capabilities support the overall mission/vision?
- What outcomes are expected to be achieved by a particular capability or set of capabilities?
- What services are required to support a capability?
- What is the functional scope and organizational span of a capability or set of capabilities?
- What is our current set of capabilities that we are managing as part of a portfolio?
- 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 Architecture Framework Version 2.02