DoDAF Viewpoints and Models
The Capability Viewpoint and the DoDAF-described Models within the viewpoint are introduced into DoDAF V2.0 to address the concerns of Capability Portfolio Managers. In particular, the Capability Models describe capability taxonomy and capability evolution.
The DoD increasingly employs incremental acquisition to help manage the risks of complex procurements. Consequently, there is a need to provide 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.
Another justification for the Capability Viewpoint 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.
Capability Model Descriptions
||Addresses the enterprise concerns associated with the overall vision for transformational endeavors and thus defines the strategic context for a group of capabilities.
|CV-2: Capability Taxonomy
||Captures capability taxonomies. The model presents a hierarchy of capabilities. These capabilities may be presented in context of a timeline - i.e., it can show the required capabilities for current and future capabilities.
|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.
Mappings of the Capability Viewpoint DoDAF-described Models to the DM2 Concepts, Associations, and Attributes are in DM2 Concepts, Associations, and Attributes Mapping to DoDAF-described Models. The DM2 Concepts, Associations, and Attributes are described in the DoDAF Meta-model Data Dictionary.
Use of Capability Viewpoint Models. The CV DoDAF-described Models 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, as well as increasing the value of federation.
In the above context, a capability thread is similar to the result of a query that would be run on a particular capability. For example, if an architecture were to include operational activities, rules, and systems, a capability thread would equate to the specific activities, rules, and systems that are linked to that particular capability. The CV DoDAF-described Models are used to provide the strategic perspective and context for other architectural information.
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?
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