|
Code
|
Subview Name
|
Comment
|
|
NSV-1
|
Systems Interface Description
|
Identification of systems and system connections and the information exchanges between them
|
|
NSV-2a
|
System Port Specification
|
Identifies the ports on each system and the protocols supported by each port
|
|
NSV-2b
|
System to System Port Connectivity
|
Identifies the connections between ports and shows the protocols and hardware specified for each connection.
The ports may be on different systems.
|
|
NSV-2c
|
System Connectivity Clusters
|
Shows how individual connections between system ports are grouped into logical connections between nodes
|
|
NSV-2d
|
Systems Communication Quality Requirements
|
Specifies quality requirements applicable to communications between systems
|
|
NSV-3
|
Resources-Resources Matrix
|
Describes relationships between systems in a given architecture; can be designed to show relationships of interest, for example, system-type interfaces, planned vs existing interfaces, etc.
|
|
NSV-4
|
System Functionality Description
|
Functions performed by systems and the system data flows among system functions
|
|
NSV-5
|
Systems Function to Operational Activity Traceability Matrix
|
Mapping of systems back to capabilities or operational activities
|
|
NSV-6
|
Systems Data Exchange Matrix
|
Provides details of system data elements being exchanged between systems and the attributes of this exchange
|
|
NSV-7
|
Systems Quality Requirement Description
|
Specifies the quality characteristics of systems, system hardware/software items, their interfaces and their functions as well as the current quality requirements and the expected or required quality requirements at specified times in the future.
|
|
NSV-8
|
Systems Configuration Management
|
Planned incremental step toward migrating a suite of systems to a more efficient suite, or toward evolving a current system to a future development of the architecture
|
|
NSV-9
|
Technology and Skills Forecast
|
Emerging technologies and software/hardware products that are expected to be available in a given set of time frames and that will affect future development of the architecture
|
|
NSV-10a
|
Resources Constraints Specification
|
One of three subviews used to describe system functionality - identifies constraints that are imposed on the architecture or its systems under specified conditions.
|
|
NSV-10b
|
Resources State Transition Description
|
One of three subviews used to describe system functionality - identifies responses of a system to states, events and actions
|
|
NSV-10c
|
Resources Event-Trace Description
|
One of three subviews used to describe system functionality - identifies system-specific refinements of critical sequences of events described in the NATO Operational View
|
|
NSV-11a
|
Logical Data Model
|
Allows analysis of a system‘s data definition aspect, without consideration of implementation specific or product specific issues and provides a common dictionary of data definitions to consistently express subviews wherever logical-level data elements are included in the descriptions..
|
|
NSV-11b
|
Physical Data Model
|
Physical implementation of the Logical Data Model entities, for example, message formats, file structures, physical Schema
|
|
NSV-12
|
Service Provision
|
Mapping of systems to services to identify which system contribute to the provision of which service.
|