View DNDAF:OV-2 Operational Node Connectivity Description Subview
Title
OV-2 Operational Node Connectivity Description Subview
Version & Date
1.6 See DNDAF Release History
Introduction
The OV-2 subview is part of the DNDAF Operational View.
The Operational View-2 (OV-2): Operational Node Connectivity Description graphically depicts the operational nodes (organizational units such as a standing org, co-ordination cell, committee, matrix org, a commander, etc.) and needlines (for example, information exchange requirements). The graphic includes nodes that are both internal and external to the scope of the architecture project
Purpose
The OV-2 identified the operational nodes and the information exchanges between those nodes. OV-2 and OV-3 enables architects to develop the logical design for the architecture and sets the initial scope, requirements and constraints for the physical design in the System View.
Background
It is vital that management has the ability to visualize nodes and needlines that constitute the architecture project. The operational nodes represent logically where organizations reside, where activities are performed, where information exchanges occur. The OV-2 depict information exchanges at a higher level of abstraction. Detailed information exchange requirements will be provided in OV-3, the Operational Information Exchange Matrix.
Description
Definition
The OV-2 is a graphical depiction of operational nodes with information exchange needlines between those nodes.
Detailed Description
This sub-view identifies the operational nodes and their needlines that are necessary to conduct the corresponding operational activities that may be described in the OV-5s (OV-5a, OV-5b).
It is important to note that OV-2 depicts logical connectivity and not the physical connectivity between the nodes. The needline does not indicate how the information transfer is implemented. For example, information produced at node A that is required to be used by Node C may, in actuality, be routed via node B. However, node B would not be shown on the OV-2 sub-view diagram – the needline would simply be represented as going from node A to node C. This means that the role of the OV-2 is not to identify a solution but to identify the requirement. The solution (or what systems nodes or systems are used to execute the transfer) is developed in the Systems Interface Description (SV-1).
The OV-2 needlines document the requirement to exchange information between points of interest. The needlines identified in the OV-2 are detailed and further described in the OV-3.
Subview DADM Elements
The DADM entities and attributes provided below are the elements that this sub-view is responsible for creating:
Presentation
- graphical
Information exchange characteristics are shown as a summary on the diagram, and more comprehensively in matrix format in the OV-3.
The arrows on the diagram represent needlines only; each arrow indicates that there is a need for some kind of information transfer between the two connected nodes. There is a one-to-many relationship between needlines and information exchanges, that is, a single needline arrow on the OV-2 can represent multiple information exchanges.
The needline arrows do not indicate how the information transfer is implemented. The implementation in terms of which systems are used to effect the transfer is shown in the SV-1; the communications pathways, e.g. via Local Area Net, multiple “hops” between source node and ultimate destination node, are shown in the Systems Communications Description (SV-2).
The OV-2 diagram also illustrates connectivity with external nodes i.e. nodes that are not strictly within the scope of the architecture project but that act as important sources of information required by nodes within the architecture project. These external needlines should be labeled to show the external source or destination as well as the information exchanged.
Examples
See:
- p31 Figure 3.5.1 in DND/CF Architecture Framework (DNDAF) Volume 2: DND/CF Views and Sub-Views
- p27 Figure 2.6.1 in DND/CF Architecture Framework (DNDAF) Volume 4: DND/CF User Guide
Prerequisites
The OV-1 is the prerequisite for this sub-view:
- OV-1. Organizations, organization types, or human roles, depicted in OV-1 should be traceable to operational nodes in OV-2; relationships in OV-1 should trace to needlines in OV-2.
See DNDAF Subview Dependencies
Comments
Other Frameworks
See also:
- DODAF::OV-2 Operational Resource Flow Description Model
- MODAF::OV-2 Operational Node Relationship Description View
- NAF::NOV-2 Operational Node Connectivity Description Subview
- TRAK::CVp-01 Concept Need Viewpoint
References
- Section 3.5 (p30) of of DND/CF Architecture Framework (DNDAF) Version 1.6, Volume 2: DND/CF Views and Sub-Views. https://www.img.forces.gc.ca/pub/af-ca/vol-02/index-eng.asp
- Section 2.6 (p25) of of DND/CF Architecture Framework (DNDAF) Version 1.6, Volume 4: User Guide. https://www.img.forces.gc.ca/pub/af-ca/vol-04/index-eng.asp
Category:Framework -> Specification
Category:Framework -> Subview