Course Outline
Background
UAF and NAF Goals
Framework Documentation Structure
What Is Inside UAF and NAF?
How UAF and NAF Work
NATO Network Enabled Capability
What Is Enterprise Architecture?
How to Describe the Architecture?
Why Architecture Matters
Enterprise Architecture 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
Other UAF Views:
Projects, Standards, Actual Resources, Dictionary, Requirements, Summary and Overview, Information and Parameters
METHODOLOGY for Using Architecture Views
Stakeholder Concerns, Viewpoints and Perspectives
Architecture Dimensions and Types of Architectures
Architecting Styles
Key Architecture Processes and Architecture Governance
Architecture Management, Architecture Description, Architecture Evaluation
Architecture Enablers and the Architecture Life Cycle
Architectures and Architecting Activities within the Enterprise
Architecture Frameworks and Architecture Repositories
Architecture Motivation Data
Managing Architecture Motivation Data and Architecture Policy
NAF v4 Architecture Management Plan and the Migration Plan
ARCHITECTING ACTIVITY: Architecting Stages, Architecting Dynamics, Multi-Tier Architecting
ARCHITECTING FOR THE ENTERPRISE SCOPE: Introduction, Overview of 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
Ongoing Work 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 modelling using UML or SysML is beneficial but not essential, as each model-based architecture view will be explained 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.
