Code | Subview Name | Comment |
|---|---|---|
NAV-1 | Overview and Summary Information | Architecture project identification, scope, purpose, viewpoint, context tools and file formats used, analytical findings |
NAV-2 | Integrated Dictionary | Architecture data repository with definitions of all terms used in all products |
NAV-3a | Architecture Compliance Statement (Metadata) | Certifies that architecture satisfies all applicable and imposed criteria documented in the NAF to a required degree |
NAV-3b | Metadata (Extensions) | Documents any deviations of the architecture's subviews from the standard subview guidelines of the NAF |
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-5 | Capability to Organizational Deployment Mapping | Capabilities, system connectivity, organizational structures, and programmatic information |
NCV-6 | Capability to Operational Activities Mapping | Describes the mapping between capability elements and the operational activities that those capabilities support |
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 |
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-3 | Capability to Services Mapping | Mapping between the capabilities required by an Enterprise and services as defined for SOA |
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 |
NSOV-5 | Service Functionality | Specification of the mapping between services and the functional activities that those services support |
NSOV-6 | Service Composition | Specifies how services can be combined and sequenced to provide a higher level service. |
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 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 |
NSV-12 | Service Provision | Mapping of systems to services to identify which system contribute to the provision of which service. |
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. |
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 |