The NAF v3.0 specification is a guidance document. It does not direct which subviews are mandatory for which types of NATO architectures. The NAF is also flexible in that it allows user defined subviews and deviation from existing subviews, if so required, to achieve the objectives of the architecture effort. Consequently, an architecture compliance statement only makes a statement on:

- whether an architecture's subviews deviate from the subview descriptions in chapter 4 of the specification document (and to what degree)

- whether an architecture's subviews deviate from the NMM (and to what degree)

- whether an architecture's subviews use terminology that is inconsistent with the definitions of terms described in chapter 7 of the specification document.

The NAV-3a - Architecture Compliance Statement (Metadata) subview is used to certify (officially state) that an architecture satisfies all the applicable (externally) imposed criteria to a required degree. The criteria in question are documented in the official NAF documentation.

Its aim is also to communicate to the stakeholders of the architecture effort, and to other architects, that an architecture meets the requirements of the NAF.

 

HOPEX NAF.