Course Outline
Background
Goals of UAF and NAF
Structure of Framework Documentation
Contents of the UAF and NAF
Operational Mechanics of UAF and NAF
NATO Network Enabled Capability
Defining Enterprise Architecture
Methods for Describing Architecture
The Importance of Architecture
Enterprise Architecture (EA) and Decision-Making
UAF and Types of NATO Architectures
Architecture Views in UAF and NAF
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 Governance
Architecture Management, Description, and Evaluation
Architecture Enablers and Life Cycle
Architectures and Architecting Activities within 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 Enterprise Architecting Activities
ARCHITECTING IN A PROJECT: Overview of Project Architecting Activities and Detailed Project Architecting Activities
FOUNDATION FOR ARCHITECTING: Architecting Principles (Establishing a Basis for Best Practices)
Correspondences between NAF Viewpoints and ArchiMate Metamodel Layers / Elements
Work in Progress on UAF v1.1 and Future Standard Development 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 : Prior knowledge of modeling with UML or SysML is beneficial but not mandatory, as each model-based view in the architecture will be illustrated using examples from the case study.
Participant Profiles : Enterprise Architects, System Architects, Business Analysts, System Analysts, Software Designers.
Testimonials (1)
Flexibility in allowing customer to identify the real-world issues impacted by the subject matter.
