1. NAF Revision Syndicate Update to IDEAS Group
Derived from Presentation by Svein Olaussen
NAF Revision Syndicate Leader
Frits Broekema, NC3A
NATO UNCLASSIFIED
NATO UNCLASSIFIED

2. NAF Revision The work has been supported by
seven nations in addition to
NC3A and
representatives from the Infosec community.
Most nations responsible for developing a chapter
13 meetings
5 workshops.
Resource constraints.
THE WORK HAS BEEN SUPPORTED BY SEVEN NATIONS - BE, FIN, NL, NO, SWE, UK, US - IN ADDITION TO NC3A AND REPRESENTATIVES FROM THE INFOSEC COMMUNITY
MOST OF THESE NATIONS HAS TAKEN THE RESPONSIBILITY OF DEVELOPING A CHAPTER IN THE NEW NAF
NATO UNCLASSIFIED
NATO UNCLASSIFIED

3. NAF Perspectives and Views
NAF – MODELLING USING SEVEN VIEW SETS
NAF IS LARGELY BASED ON BEST PRACTICE – FROM NATIONAL ARCHITECTURE FRAMEWORKS
NAF HAS BEEN TAILORED TO NATO PROCESSES AND LIFECYCLES
NAF TAKES A PRAGMATIC APPROACH AND SUPPORT MODELS ALL APPROPRIATE VIEWS
WE SHOULD HOWEVER MODEL ONLY WHAT IS NEEDED (THOUGH WE ESTIMATE A MINIMUM CORE MANDATED SET)
ENHANCEMENTS INCLUDE VIEWS THAT SUPPORT CAPABILITY AND PROGRAM MANAGEMENT AND SOA
NAF DEFINES THE VARIOUS STANDARD VIEWS AND SUB-VIEWS THAT MAY BE PRODUCED USING THE UNDERLYING META-MODEL.
NAF PROVIDES A TOOLBOX OF VARIOUS ARCHITECTURE VIEWS THAT CAN BE USED TO COMMUNICATE ARCHITECTURE INFORMATION.
WE HAVECHOSEN THE TOOLBOX APPROACH WHERE WE HAVE COLLECTED OLD VIEWS AND NEW VIEWS TOGETHER WITHOUT VALIDATION ON THE ACTUAL NEED FROM THE STAKEHOLDERS.
WE BELIEVE THAT THE STAKEHOLDERS SHOULD CHOOSE THE MOST APPROPRIATE VIEWS TO SUIT THEIR NEEDS.
AFTER SOME TIME WE WILL EXPERIENCE THAT THERE ARE DIFFERENT CATEGORIES OF VIEWS BASED UPON USAGE, AND WE CAN REMOVE VIEWS FROM THE TOOLBOX WHICH DO NOT GIVE ANY ADDED VALUE.
NAF PROVIDE GUIDANCE FOR COMMUNICATING NATO ARCHITECTURES.
OTHER NATIONS ARE WATCHING WITH INTEREST – SEVERAL HAVE MADE STATEMENTS THAT THEY WIL ADOPT NAF FOR THEIR OWN USE
Provides summary information for the architecture that enables it to be indexed searched and queried
Documents the strategic picture of how military capability is evolving in order to support capability management and equipment planning
NATO
CAPABILITY
VIEW
NATO
ALL
VIEW
Documents programme dependencies, timelines and status to inform programme management and procurement synchronization
Documents the operational processes, relationships and context to support operational analyses and requirements development
NATO OPERATIONAL VIEW
NATO PROGRAM VIEW
NATO SERVICES VIEW
NATO SYSTEM VIEW
NATO TECHNICAL VIEW
Documents Services functionality, constraints and interoperability
Documents system functionality and interconnectivity to support system analysis and through life management
Documents policy, standards, guidance and constraints to specify and assure quality expectations
NATO UNCLASSIFIED
NATO UNCLASSIFIED

4. NAF v3 development schedule
Draft
NAF 3 Final
NAF Revision Syndicate Internal releases for Development and Review
Feedback from Review
Q2 07
Feb
Mar
Jul
Aug/Sep
Oct
Nov
NAF v3 Initial release for External Review
NAF v3 Final release
THIS IS THE TIMELINE WE presented at the last IPP meeting. A FIRST DRAFT WILL BE AVAILABLE MID JULY. THE DRAFT WILL BE SENT OUT FOR REVIEW TO COMMITTEES AND CENTRAL STAKEHOLDERS LIKE ACT TO HAVE THEIR COMMENTS DURING AUG/SEPT.
WE WILL THEN HAVE A FINAL VERSION LATER IN THE AUTUMN
NATO UNCLASSIFIED
NATO UNCLASSIFIED

5. NAF v3 Ed 0.9 Status
NATO UNCLASSIFIED
NATO UNCLASSIFIED

6. Chapter 1: Introduction to NATO Architecture Framework
This chapter is dependent on the content of the other chapters. It will be finalized when the other chapters have been finished. It is about 90 percent complete.
Chapter 1 is the scene setter for the NAF. It describes what is in the NAF and how the NAF is used to accomplished NATO and National architecture objectives
Some rework is needed based on missing parts within the other chapters and the harmonization needed between chapters 3, 4, and 5.
It will require about two weeks to complete this chapter once the above mentioned rework has been done.
NATO UNCLASSIFIED
NATO UNCLASSIFIED

7. Chapter 2: Architecture Stakeholders
This chapter is essentially complete. It is important that this chapter is thoroughly reviewed by the various stakeholders described in the chapter. This chapter is dependent on chapter 6 for the description of the stakeholders involved in architecture governance
Chapter 2 defines the various architecture stakeholders and communities of interest (COIs) to provide a basis for analyzing the architecture elements addressed by chapters 3, 4, 5, and 6.
Rework is expected once chapter 6 is completed and once feedback from the stakeholders has been received
The amount of time expected to incorporate the changes resulting from a review of this chapter is small
Focused on users of Architetcures
NATO UNCLASSIFIED
NATO UNCLASSIFIED

8. Chapter 3: Architecture Concepts and Elements
A full draft of Chapter 3 is included in this release of NAF
This chapter identifies and describes the things that are important and that should be designed and described in an architecture (ingredients of architecture, architecture elements), and gives some reasoning why they are important.
Significant issues were discovered during a review by the NRS and need to be resolved in the next release. The issues mainly highlight inconsistencies between chapter 3 and other chapters
Chapter 3 needs to be harmonized with chapters 4 and 5, possibly leading to further rework of these chapters.
Is very useful input for the definition of the upper-ontology
NATO UNCLASSIFIED
NATO UNCLASSIFIED

9. Chapter 4: Architecture Views and Subviews
Chapter 4 is an extensive chapter and many subviews, examples and metamodel diagrams still need to be incorporated or modified. The chapter is about 80 percent complete.
This chapter details the views and standard subviews that can be used to describe an architecture and are supported by the NATO metamodel (NMM).
An updated version of the NMM is needed to finish this chapter. Some subviews still need to be described, many examples and diagrams need to be developed or changed, and the Running Example needs to be elaborated and polished. With the chapter 3, 4, and 5 harmonization, it can be expected that several subviews will be changed or added.
The remaining 20 percent of work, not dependent on inputs from the other chapters (other than the NMM), is relatively minor. Harmonizing this chapter with chapters 3 and 5 will require a more substantial amount of rework.
NATO UNCLASSIFIED
NATO UNCLASSIFIED

10. Chapter 5: NATO Architecture Metamodel and Architecture Data Exchange Mechanism
The metamodel contained in chapter 5 is NMM v 0.8, which is based on MODAF Metamodel Version 1.0 and includes few of the NATO-derived additions. The NMM is not complete.
MOD UK sponsored development of NMM v0.8, but can no longer support NATO requirements which are “over and above” UK requirements. UK has proposed that NATO finance what is needed to complete the NMM. A Statement of Work (SOW) has been established that describes NATO NAF requirements and products.
This chapter presents the NMM in a way that allows architecture tool vendors and implementers of architecture repositories to capture and support the development of NAF compliant architectures. This chapter describes the concepts that lie underneath and are common to all views, subviews and architecture elements in chapters 3 and 4.
The remaining work essentially revolves around completing the NMM and writing it out in full. Completion of the NMM largely depends on the harmonization of chapters 3, 4, and 5. It can be expected that the NMM will be modified accordingly.
NATO UNCLASSIFIED
NATO UNCLASSIFIED

11. Chapter 6: Architecture Governance
Chapter 6 currently contains a listing of essential architecture governance elements in a bulleted format. These elements are not yet related to the main NATO life-cycle processes. This chapter is about 25% complete. There exists a two-way dependency relationship with the NID, which is currently being revised
This chapter focuses on two aspects of architecture governance: it details the essential controls, products, processes, roles and responsibilities, necessary to manage the architecture life-cycle (both products and framework), and describes how these essential elements can be embedded within the main NATO life-cycle processes.
The essential architecture governance elements need to be elaborated upon and related to the NATO life-cycle processes.
The writing out of the essential elements is a minor task. However, the description of the relationships with NATO processes requires a thorough analysis of these processes, and, as such, constitutes a major effort. Finally, this chapter needs to be synchronized with the subsequent version of the NID and chapter 2 of the NAF.
NATO UNCLASSIFIED
NATO UNCLASSIFIED

12. Chapter 7: Architecture Definitions, Terminology, Ontology
Chapter 7 currently includes a comprehensive list of architecture-related definitions, abbreviations and acronyms.
The architecture ontology and taxonomy have not yet been addressed
It has been recognized that an ontology is needed to ensure consistency across architectures.
The International Defence Enterprise Architecture Exchange Specification (IDEAS) working group is currently developing, among other things, a defence enterprise architecture ontology to support exchange of architecture information between nations. The aim is to have an international standard which the NAF can incorporate, once it is finished.
The list of definitions, abbreviations and acronyms must be updated once the chapters are completed. This does not require much effort.
NATO UNCLASSIFIED
NATO UNCLASSIFIED

13. Annexes
ANNEX A: NC3A Architecture Engineering Methodology. The existing version of the AEM is specific to the Bi-SC AIS Target Architectures. It is currently being revised and will not be available until later this year. It will not be included in this release of the NAF.
ANNEX B: Transition Guidance NAF v2 to NAF v3. Describes a process for converting a NAF Version 2-developed architecture into one that is compliant with NAF Version 3. This ANNEX will be developed once the NAF Version 3 has been completed. ANNEX B will be provided in a subsequent release of NAF Version 3.
ANNEX C: NATO Architectures. Lists the architecture products suggested by the NATO Interoperability Directive (NID) to describe the various types of NATO architectures. The NID is currently under revision and ANNEX C will be developed in synchronization with the NID. ANNEX C will not be provided in this release.
Annex C is being discussed.
NATO UNCLASSIFIED
NATO UNCLASSIFIED

14. NAF Meta-Model
The first version of the NAF Meta-Model is developed from MODAF Meta-Model (M3) version 1.0, and does not contain any of the remaining elements needed to support a comprehensive NAF.
NATO UNCLASSIFIED
NATO UNCLASSIFIED

15. Contacting NC3A NC3A Brussels NC3A The Hague Visiting address:
Bâtiment Z Avenue du Bourget 140 B-1110 Brussels Telephone +32 (0) Fax +32 (0)
Postal address: NATO C3 Agency Boulevard Leopold III B-1110 Brussels - Belgium
NC3A The Hague
Oude Waalsdorperweg AK The Hague Telephone +31 (0) Fax +31 (0)
Postal address: NATO C3 Agency P.O. Box CD The Hague The Netherlands
NATO UNCLASSIFIED
NATO UNCLASSIFIED