View NAF:NAV-1 Overview and Summary Information Subview



The NAV-1 Overview and Summary Information subview is part of the NATO All View and one of the 47 NATO Architecture Framework subviews.

Version & Date

Version 3.0

See NAF Release History.


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

The Overview and Summary Information subview (NAV-1) provides executive-level summary information in a consistent form that allows quick reference and comparison between architectures. NAV-1 includes assumptions, constraints, and limitations that may affect high- level decisions relating to the architecture.

Covered by NATO release conditions.


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

The NAV-1 product is a summary of a given architecture effort, documenting the following:

  • Architecture Project Identification - Identifies the architecture project name, the architects, and the organisation developing the architecture. It also includes assumptions and constraints, identifies the approving authority and the completion date, and records the level of effort and costs (projected and actual) required to develop the architecture.
  • Scope - Identifies the views and subviews that have been developed and the temporal nature of the architecture, such as the time frame covered, whether by specific years or by designations such as current, target, transitional, and so forth. Scope also identifies the organisation that fall within the scope of the architecture.
  • Purpose and viewpoint - Explains the need for the architecture, what it will demonstrate, the types of analyses (e.g., Activity-Based Costing) that will be applied to it, who is expected to perform the analyses, what decisions are expected to be made on the basis of an analysis, who is expected to make those decisions, and what actions are expected to result. The viewpoint from which the architecture is developed is identified (e.g., planner or decision maker).
  • Context - Describes the setting in which an architecture exists. Context includes such things as: mission, doctrine, relevant goals and vision statements, concepts of operation, scenarios, information assurance context (e.g. types of system data to be protected, such as classified or sensitive but unclassified, and expected information threat environment), other threats and environmental conditions, and geographical areas addressed, where applicable. Context also identifies authoritative sources for the rules, criteria, and conventions that were followed.
  • Tools and File Formats Used -Identifies the tool suite used to develop the architecture and file names and formats for the architecture and each product.
  • Findings - States the findings and recommendations that have been developed based on the architectural effort. Examples of findings include: identification of shortfalls, recommended system implementations, and opportunities for technology insertion. During the course of developing an architecture, several versions of a product may be produced. An initial version may focus the effort and document its scope, the organisation involved, and so forth. After other subviews within an an architecture’s scope have been developed and verified, another version may be produced to document adjustments to the scope and to other aspects of the architecture that may have been identified. Costing information, such as integration costs, equipment costs and other costs can be included in the findings.

After an architecture has been used for its intended purpose, and the appropriate analysis has been completed, yet another version may be produced to summarize these findings for high level decision makers.

In this version, the NAV-1 product and a corresponding graphic in the form of an NOV-1 product serve as an executive summary of the architecture.

Covered by NATO release conditions.

From the NATO Architecture Framework v3, CHAPTER 5, Section

The application of standard configurations shortens the architecture effort and provides for a better design by reusing readily available and already proven designs.

The architectures themselves must explicitly mention and describe standard configurations, or else they will not be recognized as such, and consequently, will not be available for future projects or recognized by future architects.

Covered by NATO release conditions.


Care needs to be taken to separate ‘architecture’ from ‘architecture description’ - they are not the same thing. The NAV-1 correctly identifies that this is a response to a task but it then keeps referring to ‘architecture’ rather than ‘architecture description’. The NAV-1, particularly when the analysis approach is described, is all about describing the modelling NOT the architecture. The modelling might well result in comment on the suitability of the architecture. The architecture doesn’t have findings but the task and modelling (architecture description) will produce these. Loose talk

Other Frameworks

See also:


  • Section 4.3.1 (page 181 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.
  • Section (page 443 of pdf) of APPENDIX 1 TO ANNEX 1 TO AC/322-D(2007)0048. NATO Architecture Framework Version 3.


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



© 2010 Eclectica Systems Ltd.