NATO bodies and NATO Nations; used by allied and partner defence organisations

NATO Architecture Framework Version 4 (NAFv4)

155 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

155 controls 0 frameworks share controls with it NATO bodies and NATO Nations; used by allied and partner defence organisations verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
NAF-1.1CR capability roadmap viewpoint0
NAF-1.1.1CR capability roadmap metamodel0
NAF-1.1.2Meaning of meta-model0
NAF-1.1.3What a meta-model should show0
NAF-1.1.4Views and the viewpoints behind them0
NAF-1.1.5Versions fixed by the NISP0
NAF-1.1.6NAF viewpoint tailoring context0
NAF-1.2Methodology scope and organisational tailoring0
NAF-1.2.2Why ArchiMate counts as a meta-model0
NAF-1.3S2 service structure viewpoint0
NAF-1.3.2NAFv4 uses a UAF subset0
NAF-1.3.3Extending the NAFv4 meta-model0
NAF-13.1S2 service structure metamodel0
NAF-14.1S3 service interfaces metamodel0
NAF-15.1S4 service functions metamodel0
NAF-16.1S5 metamodel for service states0
NAF-17.1S6 service sequence metamodel0
NAF-18.1S7 service interface parameters metamodel0
NAF-19.1S8 service constraints metamodel0
NAF-2.1Core concepts of architecting and architecture0
NAF-2.1.4Viewpoint cells and information focus0
NAF-2.10Producing the architecture description0
NAF-2.11Evaluating the architecture0
NAF-2.12Enabling capabilities, services and resources0
NAF-2.13The architecture's own life cycle and fitness for purpose0
NAF-2.14.2Nested enterprise architecture scope0
NAF-2.15.1Architecture framework definition0
NAF-2.16.1Enterprise landscape coverage0
NAF-2.17.1Project architecture landscape structure0
NAF-2.18.1Data exchange between architecture landscapes0
NAF-2.19.1Reference library consistency checks0
NAF-2.2What the architecting effort covers across the life cycle0
NAF-2.2.1L1 cut-out elements0
NAF-2.20.1Architecture repository baselines0
NAF-2.21.1Purpose of architecture motivation data0
NAF-2.22.1Architecture policy content and ownership0
NAF-2.23.1Architecture management plan content0
NAF-2.24.1Migration plan content0
NAF-2.25.1Evaluation report content0
NAF-2.26.1Main architecture document baseline0
NAF-2.27.1Dashboard monitoring purpose0
NAF-2.3Stakeholder concerns, views and viewpoints0
NAF-2.3.1L2 cut-out elements0
NAF-2.4Dimensions an architecture may cover0
NAF-2.4.1Graphical notation conventions0
NAF-2.5Architecture types and baselines0
NAF-2.6Standardised architecting styles0
NAF-2.7Five architecture processes and their interplay0
NAF-2.8Architecture governance and design authority0
NAF-2.9Architecture management along the life cycle0
NAF-25.1L3 cut-out elements0
NAF-25.2How L3 relates to the earlier logical views0
NAF-26.1L4 cut-out elements0
NAF-27.1L5 cut-out elements0
NAF-28.1L6 cut-out elements0
NAF-29.1L7 cut-out elements0
NAF-3.1.1Manage motivation data and dashboard stage0
NAF-3.2.1P1 cut-out elements and relations0
NAF-3.2.2P1 notes on the cut-out0
NAF-3.2.3P1 compliant example0
NAF-3.2.4Guidance for assessment and trade-offs0
NAF-3.2.5Describing alternatives and tracing them0
NAF-3.2.6Criteria for judging alternatives0
NAF-3.2.8Iterative stages and prerequisites0
NAF-3.3.1P2 cut-out elements and relations0
NAF-3.3.2P2 notes on the cut-out0
NAF-3.3.3Governance approval of weightings0
NAF-3.3.4Patterns of architecting iteration0
NAF-3.3.5Use and update motivation data0
NAF-3.3.6Tailor architecture dynamics0
NAF-3.4.1P3 cut-out elements and relations0
NAF-3.4.2Market and customer triggers0
NAF-3.4.3Updating the landscape in both directions0
NAF-3.5.1P4 cut-out elements and relations0
NAF-3.6.1L4 to P4 cut-out elements0
NAF-3.7.1P5 cut-out elements and relations0
NAF-30.1L8 cut-out elements0
NAF-35.2P4 compliant example0
NAF-36.2L4 to P4 compliant example0
NAF-37.2P5 compliant example0
NAF-38.1P6 cut-out elements and relations0
NAF-38.2P6 compliant example0
NAF-39.1P7 cut-out elements and relations0
NAF-39.2P7 compliant example0
NAF-4.1.1Resource roadmap metamodel elements0
NAF-4.1.2Enterprise architecture systemic analysis0
NAF-4.1.3Delivery architectures for programmes and projects0
NAF-4.1.4Direction for delivery work0
NAF-4.1.5Architecture as governance input0
NAF-4.2Enterprise architecting stage overview0
NAF-4.3Setting up the enterprise architecture landscape0
NAF-40.1P8 cut-out elements and relations0
NAF-40.2P8 compliant example0
NAF-40.3P8 notes on the example0
NAF-9.2C7 and C5 criteria scope0
NAF-A1A1 metadata definitions view0
NAF-A2A2 view of architecture products0
NAF-A3A3 architecture correspondence view0
NAF-A4A4 architecture methodology view0
NAF-A5A5 view of architecture status0
NAF-A6A6 view of architecture versions0
NAF-A7A7 architecture metadata and measures view0
NAF-A8A8 architecture standards view0
NAF-ArAr architecture roadmap view0
NAF-C1C1 capability taxonomy view0
NAF-C2C2 enterprise vision view0
NAF-C3C3 capability dependencies view0
NAF-C4C4 standard processes view0
NAF-C5C5 view of capability effects0
NAF-C7C7 performance criteria view0
NAF-C8C8 planning constraints view0
NAF-CrCr capability roadmap view0
NAF-L1L1 logical taxonomy view0
NAF-L2L2 view of logical structure0
NAF-L2-L3L2-L3 logical concept view0
NAF-L3L3 logical interactions view0
NAF-L4L4 logical activities view0
NAF-L5L5 logical states view0
NAF-L6L6 logical sequence view0
NAF-L7L7 view of the information model0
NAF-L8L8 logical constraints view0
NAF-LrLr view of the logical roadmap0
NAF-P1P1 view of the resource taxonomy0
NAF-P2P2 view of resource structure0
NAF-P3P3 resource interactions view0
NAF-P4P4 view of resource functions0
NAF-P5P5 view of resource states0
NAF-P6P6 view of resource sequences0
NAF-P7P7 view of the data model0
NAF-P8P8 resource constraints view0
NAF-PrPr view of the resource roadmap0
NAF-S1S1 service taxonomy view0
NAF-S2S2 view of service structure0
NAF-S3S3 service interfaces view0
NAF-S4S4 view of service functions0
NAF-S5S5 service states view0
NAF-S6S6 service sequence view0
NAF-S7S7 service interface parameters view0
NAF-S8S8 service constraints view0
NAF-SrSr view of the service roadmap0
NAF-Table-2.10Decide on enterprise architecture change requests0
NAF-Table-2.11Enterprise motivation data and architecture dashboard0
NAF-Table-2.12Establish the project architecture landscape and capability0
NAF-Table-2.13Establish the project architecture vision0
NAF-Table-2.14Describe alternatives of project architectures0
NAF-Table-2.15Evaluate architecture alternatives and propose trade-offs0
NAF-Table-2.16Project migration plan and implementation roadmap0
NAF-Table-2.17Project conformance reviews and governance contract0
NAF-Table-2.18Controlled project architecture change management0
NAF-Table-2.19Project motivation data, dashboard and decision rationale0
NAF-Table-2.20Kinds of architecture principle0
NAF-Table-2.21Levels of principle compliance0
NAF-Table-2.8Enterprise transformation roadmap and migration plan0
NAF-Table-2.9Enterprise governance of architecture application0
NAF-Table-3.22Definitions of description and view terms0

Tell me when NATO Architecture Framework Version 4 (NAFv4) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for NATO Architecture Framework Version 4 (NAFv4), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition