Course Outline
Background
UAF and NAF objectives
Framework Documentation Structure
Contents of UAF and NAF
Operational mechanics of UAF and NAF
NATO Network Enabled Capability
Defining Enterprise Architecture
Methods for Describing Architecture
The Importance of Architecture
EA and Decision-Making
UAF and Types of NATO Architectures
UAF and NAF Architecture Views
The UAF Strategic View and the NAF Concepts View
The UAF Operational View and the NAF Logical Specification View
The UAF Services View and the NAF Service-Specification View
The UAF Personnel, Resources and Security View and the NAF Physical Resource Specification View
The UAF Meta-Data View and the NAF Meta-Data View
Additional UAF views:
Projects, Standards, Actual Resources, Dictionary, Requirements, Summary and Overview, Information and Parameters
METHODOLOGY for utilizing Architecture Views
Stakeholder Concerns, Viewpoints and Perspectives,
Architecture Dimensions and Types of Architectures
Architecting Styles
Core Architecture Processes and Architecture Governance
Architecture Management, Architecture Description, Architecture Evaluation
Architecture Enablers and Architecture Life Cycle
Architectures and Architecting Activities within the Enterprise
Architecture Framework and Architecture Repositories
Architecture Motivation Data
Managing Architecture Motivation Data and Architecture Policy
NAFv4 Architecture Management Plan and the Migration Plan
ARCHITECTING ACTIVITY: Architecting Stages, Architecting dynamics, Multi-tier architecting
ARCHITECTING FOR THE ENTERPRISE SCOPE: Introduction, Overview of the Enterprise Architecting Stages, Enterprise Architecting Activities
ARCHITECTING IN A PROJECT: Overview of Project architecting activities, Project Architecting Activities
FOUNDATION FOR ARCHITECTING: Architecting Principles (Foundation for Best Practices)
Correspondences between NAF viewpoints and the ArchiMate metamodel layers / elements
Work in progress on UAF v1.1 and future development plans for the standard
NAF and ArchiMate are trademarks of NATO and The Open Group, respectively.
UAF, UML, and SoaML are trademarks of the Object Management Group (OMG).
Summary and Conclusion
Requirements
Prerequisites: Familiarity with modeling using UML or SysML is beneficial, though not strictly required, as each model-based view of the architecture will be elucidated through examples from the case study.
Participant Profiles: Enterprise Architects, System Architects, Business Analysts, System Analysts, and Software Designers.
Testimonials (1)
Flexibility in allowing customer to identify the real-world issues impacted by the subject matter.
