Course Outline

Introduction

  • What is the NATO Architecture Framework (NAF)?
  • Comparing NAF to Other Architectural Frameworks
  • An Overview of NAF Features and Architecture

Understanding NAF

  • The Lifecycle of a NATO Architecture
  • How NAF Functions for Government

Getting Started

  • Setting Up Sparx Enterprise Architect as a Development Environment for Government
  • Installing NAF as a Framework for Government Use

Background

  • NATO Command, Control, and Communications (C3)
  • The Mission of the NATO C3 Organization
  • NAF Goals and Objectives
  • Structure of the Framework Documentation

NATO Network Enabled Capability

  • Defining an Enterprise Architecture for Government Operations
  • Describing the Architecture in Detail
  • The Importance of Architecture for Government Decision-Making
  • Architecture as a Communication Language for Government Entities
  • The Role of Enterprise Architecture (EA) in Government Decisions

Types of NATO Architectures

  • Quiz: Identify the Type of Architecture Described by the Following Statements
  • Overarching Architecture (OA)
  • Reference Architectures (RA)
  • Target Architectures (TA)
  • Baseline Architecture for Government Operations

NATO Architecture Views

  • NATO All View (NAV)
  • NATO Capability View (NCV)
  • NATO Operational View (NOV)
  • NATO Service-Oriented View (NSOV)
  • NATO Systems View (NSV)
  • NATO Technical View (NTV)
  • NATO Programme View (NPV)

Stakeholders

  • Communities of Interest for Government
  • Lifecycle Management in NAF for Government
  • Aligning Stakeholder Interests with the Architecture for Government
  • Identifying Key Stakeholders for Government Projects
  • Identifying Communities of Interest (CoIs) for Government Operations
  • Examples of CoIs in Government Contexts
  • The Relationship Between Stakeholders and CoIs in Government
  • Requirements Analysis for CoIs in Government
  • Describing the Interests of CoIs in Government
  • Impacts of CoI’s Architecture Interests on Government Operations
  • Requirements for Different Architecture Views in Government

Troubleshooting

Summary and Next Steps

Requirements

  • An understanding of enterprise architecture concepts for government
  • Familiarity with UML is beneficial but not required
  • No programming experience is necessary

Audience

  • Architects
  • Professionals in the field of enterprise architecture
 28 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories