NCV-4 Capability Dependencies
The NCV-4 subview 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 (NCV-3) subview.
Accessing the diagram that contains a dependency
To access the Capability Structure Diagram that contain a dependency:
1. From the navigation bar, select Capability > NCV-4.
2. Right-click the dependency whose diagram you want to access.
3. In the pop-up menu that appears, select Diagrams Containing Object.
An miniature of a Capability structure diagram containing the dependency appears.
A flashing square indicates the location of the dependency in the diagram.
4. Open the diagram by clicking the Open Diagram icon at the bottom of the image.
The diagram opens in the desktop.
Creating dependencies
Dependencies are defined within the context of an upper capability. They are created in Capability Structure Diagrams and linked to capability compositions.
To create a dependency:
*Create or open an already existing capability structure diagram.
*In the navigation tree, capabilities are found under the NCV-2 capability taxonomy folder.
*In the object toolbar, select the dependency icon and draw the dependency from the source capability composition to the target capability composition.
*The target capability composition is dependent on the source capability composition.
Example of a capability structure diagram with a dependency
The name of the dependency is a combination of the name of the upper capability and those of the source and target capabilities of the dependency.
For example, in the diagram above, the name of the dependency is "Monitoring [Detection -> Observation]".
It is, however, possible to have more than one source or target capability. This could be a case where a capability composition is included in several dependencies in the same structure diagram or where a composition is part of dependencies in different structure diagrams. Whatever the case, the naming rule is the same.
*The generation of dependency names is automatic and these names cannot be changed by the user.