View NAF:NSV-2c System Connectivity Clusters Subview
Overview
The NSV-2c System Connectivity Clusters subview is part of the NATO System View and 1 of the 4 forms of the NSV-2 Systems Communication Description Subview.
It is one of the 49 NATO Architecture Framework subviews*.
Version & Date
Version 3.1
* = changed at 3.1
+ = new at 3.1
The change history is derived from the definition of each NATO Architecture view within section 5.2.6 NATO System View (NSV)
in AC/322(SC/1-WG/1)N(2009)0005-ADD2. NATO Architecture Framework Version 3.1
document from http://www.nhqc3s.nato.int/Browser.asp?Target=_docs/NAF_v3_1 .
See NAF Release History.
Purpose
From the NATO Architecture Framework v3
, CHAPTER 4, Section 4.7.2.3
A System Connectivity Clusters subview serves to define the connectivity requirements between nodes, and is used for estimating requirements for physical routing and bandwidth. An NSV-2c subview provides a different viewpoint on information already specified in the NOV-2, NOV-3, NSV-1, NSV-2a and NSV-2b subviews. An NSV-2c subview is also useful when planning physical connections and routings between nodes.
The NSV-2c subview is also intended to aid analysis of the connectivity between systems within or between nodes. In particular it is a useful way of highlighting redundancy issues, showing when too many or too few connections are used between nodes - i.e. there could be cost savings from using a common network, or there may be a need for redundancy to increase reliability.
Covered by NATO release conditions.
Definition
From the NATO Architecture Framework v3
, CHAPTER 4, Section 4.7.2.3
An NSV-2c product defines how individual connections between system ports are grouped into logical connections between nodes.
Covered by NATO release conditions.
Data Objects*
From the NATO Architecture Framework v3.1
, CHAPTER 5, Section 5.2.6.2
The data in an NSV-2c can include:
Covered by NATO release conditions.
Presentation
Full size: File:NVS-2c.jpg
Covered by NATO release conditions.
Configuration History
- 3.1 - Data object changes - Artefact replaces Physical Asset
Comments
From the NATO Architecture Framework v3
, CHAPTER 4, Section 4.7.2.3
- identifies logical links between nodes
- system to system connections
- quality requirements
Covered by NATO release conditions.
Note: the use of node
is confusing since Node is defined in the NATO Architecture Framework Metamodel and it almost certainly is a different use of the word. It appears that ‘node’ in a NSV-2 is a network node.
Only Functional Resources i.e. can exchange information via a Resource Interaction i.e. System, Role and Capability Configuration. Only System(s) can have a System Port Connection.
Derived from NOV-2, NSV-1, NSV-2a and NSV-2b subviews.
Other Frameworks
See also:
References
- Section 4.7.2.3 (page 240 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
- Section 5.2.6.2 of Chapter 5 AC/322(SC/1-WG/1)N(2009)0005-ADD2 NATO Architecture Framework Version 3.1
Category:Framework -> View
Category:NAF -> Subview
Category:Solution
Clip to Evernote
Bookmark this on Delicious
