TRAK-Community

Overview

The NSV-2b System to System Port Connectivity 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.2

A System to System Port Connectivity subview is used to specify the physical, infrastructural nature of a connection between two systems. This may be an existing connection, or a specification of a connection that is to be made.

Covered by NATO release conditions.

Definition

From the NATO Architecture Framework v3, CHAPTER 4, Section 4.7.2.2

An NSV-2b product defines the protocol stack used by a connection between two ports. The ports may be on different systems.

The NSV-2b subview is closely related to the NSV-2a subview which specifies the available protocols on each port. Any connection specified in an NSV-2b subview shall conform to the protocols specified on the corresponding port definitions in the NSV-2a subview.

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-2b can include:

• System
• System Port
• Port Connection
• Protocol

Covered by NATO release conditions.

Presentation

Configuration History

References

• Section 4.7.2.2 (page 239 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

Comments

From the NATO Architecture Framework v3, CHAPTER 4, Section 4.7.2.2

• identifies which ports are connected
• port protocols and routing
• quality requirements
• any protocol identified must be defined in the NTV-1 Technical Standards Profile Subview

Covered by NATO release conditions.

Only Artefacts can expose a Port and a set of Artefacts can form a Capability Configuration. A NAF::System is a Physical Asset and an Artefact.

A NAF NSV-2b doesn’t show anything other than NAF::System having a port and you would expect Software to be able to expose a Port. As defined, however, this isn’t possible. The MODAF::SV-2b at MODAF 1.2.004 has a broader remit and allows both System Port and Software Port.

Other Frameworks

See also:

• MODAF::SV-2b System Port Connectivity Description View
• TRAK::SV-02 Solution Resource Interaction View

 

 

Category:Framework -> View
Category:NAF -> Subview
Category:Solution

Categories:

• Framework
  • View
• NAF
  • Subview
• Solution