Course Outline
Background
UAF and NAF Goals
Framework Documentation Structure
Contents of UAF and NAF
How UAF and NAF Function
NATO Network Enabled Capability
Defining Enterprise Architecture
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 Kinds of Architectures
Architecting Styles
Core Architecture Processes and Governance
Architecture Management, Description, and Evaluation
Architecture Enablers and Life Cycle
Architectures and Architecting Activities in the Enterprise
Architecture Framework and Repositories
Architecture Motivation Data
Managing Architecture Motivation Data and Policy
NAFv4 Architecture Management Plan and Migration Plan
ARCHITECTING ACTIVITY: Architecting Stages, Dynamics, and Multi-tier Architecting
ARCHITECTING FOR THE ENTERPRISE SCOPE: Introduction, Overview of Enterprise Architecting Stages, and Activities
ARCHITECTING IN A PROJECT: Overview and Activities of Project Architecting
FOUNDATION FOR ARCHITECTING: Architecting Principles (Foundation for Best Practices)
Correspondences between NAF Viewpoints and ArchiMate Metamodel Layers/Elements
Current Developments in UAF v1.1 and Future Standardization Plans
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: While knowledge of modeling with UML or SysML is beneficial, it is not mandatory. Each model-based view of the architecture will be explained using 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.
