CV-4 Capability Dependencies
Dependencies between planned capabilities and the definition of logical groupings of capabilities. Independent of diagrams.
The CV-4 model shows the dependencies between capabilities (or capability functions) which are of interest to the architecture and groups these capabilities into logical groupings based on the need for these elements to be integrated. These groupings are used to inform the acquisition process and the Capability Phasing (CV-3) model.
CV-4 Description
|
Model
|
Description
|
|---|---|
|
CV-2 - Capability Dependencies
|
The dependencies between planned capabilities and the definition of logical groupings of capabilities.
|
For a detailed description, see the DoDAF web site: CV-4: Capability Dependencies.
CV-4 HOPEX Implementation
CV-4 uses capability dependencies. For more information, see Defining business capability dependencies.
Dependencies matrix
This matrix shows dependencies between planned capabilities and the definition of logical groupings of capabilities withing the context of an enterprise stage.
Dependencies between capability components are represented by checkmarks in the lower part of the matrix.
Capability dependencies
This page lists capability dependencies together with the following information:
• dependency owner
The dependency owner corresponds to the parent capability (as opposed to the capability components of this capability). It can be a business capability map.• capabilities
• dependent capability
• required capability
• effects
• dependent effect
• required effect
The effect is the business outcome required or desired by a capability.The name of the dependency is a combination of the name of the dependent capability and of the required capability. For example, [Detection -> Observation]. You cannot change it.