The NAF Subviews
Each of the seven views defined above groups subviews. In NAF vocabulary, a subview is either a graphical, textual or tabular deliverable that describes the characteristics that are relevant to the architecture product. Each subview is associated to a short name created from the abbreviation of the view to which it belongs (NAV, NCV, NOV, NSOV, NSV, NTV, NPV) and suffixed by a number.
The following tables list the subview names, coded names and a brief description of each of the different NAF subviews.
List of Subviews
NATO All View  
 
Code
Subview Name
Comment
NAV-1
Overview and Summary Information
Architecture project identification, scope, purpose, viewpoint, context tools and file formats used, analytical findings
NATO Capability View Subviews 
 
Code
Subview Name
Comment
NCV-1
Capability Vision
High-level graphical/textual description of operational concept
NCV-2
Capability Taxonomy
Structured list of capabilities required during a particular time-frame
NCV-3
Capability Phasing
Representation of available capabilities at different points in time or during specific timeframes
NCV-4
Capability Dependencies
Capabilities, capability functions, describes the dependencies between capabilities, defines logical groupings of capabilities
NCV-6
Capability to Operational Activities Mapping
Describes the mapping between capability elements and the operational activities that those capabilities support
NATO Operational View Subviews 
 
Code
Subview Name
Comment
NOV-1
High Level Operational Concept Descriptions
High-level graphical description of the operational environment of the architecture, in terms of operational elements involved, geographic regions, nodal connectivity, types of forces employed, etc., and its functionality.
NOV-2
Operational Node Connectivity Description
Operational nodes, connectivity, and information exchange needlines between nodes
NOV-3
Operational Information Requirements
Information exchanged between nodes and the relevant attributes of the exchange
NOV-4
Organizational Relationships Chart
Organizational context, role or other relationships among organizations
NOV-5
Operational Activity Model
Capabilities, operational activities/operational tasks, relationships among activities, inputs and outputs; additional data can show cost, performing nodes or other pertinent information
NOV-6a
Operational Rule Model
One of three subviews used to describe operational activity. it identifies business rules that constrain operations
NOV-6b
Operational State Transition Description
One of three subviews used to describe operational activity - identifies how an operational node or activity responds to events
NOV-6c
Operational Event-Trace Description
One of three subviews used to describe operational activity - traces actions in a scenario or sequence of events
NOV-7
Information Model
Operational object, information, business rule, used to analyze the information aspect of the operational domain and guide the design of information systems
NATO System-Oriented View Subviews 
 
Code
Subview Name
Comment
NSOV-1
Service Taxonomy
Organization and classification of services according to different criterion
NSOV-2
Service Definitions
Definitions of services: definitions could refer to service outcome, identification, properties, interfaces and policies
NSOV-4a
Service Constraints
Specification of constraints that apply to implementations of services
NSOV-4b
 
Service State Model
Specification of the possible states a service may have, and the possible transitions between those states
NSOV-4c
Service Interaction Specification
Specification of how a service interacts with external agents, and the sequence and dependencies of those interactions
NATO System View Subviews 
 
Code
Subview Name
Comment
NSV-1
Systems Interface Description
Identification of systems and system connections and the information exchanges between them
NSV-2c
System Connectivity Clusters
Shows how individual connections between system ports are grouped into logical connections between nodes
NSV-4
System Functionality Description
Functions performed by systems and the system data flows among system functions
NSV-5
Systems Function to Operational Activities 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
NATO Technical View Subviews 
 
Code
Subview Name
Comment
NTV-1
Standards Profile
Listing of standards that apply to Systems and Services View elements in a given architecture and how they need to be, or have been, implemented.
NTV-2
Standards Forecast
Description of emerging, obsolete and fragile standards and potential impact on the architecture and its constituent elements
NTV-3
Standards Configurations
Description of standard configurations that apply to or emerge from the architecture effort or that are used or encountered in any of the subviews developed in the architecture effort.
NATO Programme View Subviews 
 
Code
Subview Name
Comment
NPV-1
Programme Portfolio Relationships
Details the relationships among projects within a programme to show how these projects are grouped organizationally to form a coherent acquisition programme. It summarizes the interdependencies among projects and the linkages between project phases. It is also used to identify the level of maturity to be achieved at each stage of a programme‘s life-cycle
NPV-2
Programme to Capability Mapping
Mapping of programmes and projects to capabilities to show how the specific projects and programme elements help to achieve a NATO capability, as defined in a NATO capability package
NAF Subview Generation
According to the NAF standard, there are three kinds of deliverables: graphical, textual, tabular.
Take for example the NOV-4 subview: the NOV-4 subview graphically describes the hierarchy and relationships in the organization. This is graphically described in a HOPEX organizational chart.