User Tools

Site Tools


start

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
start [2019/11/24 04:00]
admin [UAF Domains and Model Kinds]
start [2022/02/10 08:41] (current)
admin
Line 12: Line 12:
 ===== What is UAF? ===== ===== What is UAF? =====
  
-UAF extends the scope of UPDM and generalizes it to make it applicable to industry, federal, and military architectures. The core concepts in the UAF are based on: +The Unified Architecture Framework (UAF) is an architecture framework that provides visualization for specific stakeholders concerns through engineering domains organized by various views. The views are artifacts for visualizing, understanding, and assimilating the broad scope and complexities of an architecture description through tabular or graphical means. 
-DoDAF 2.0.2 Domain Metamodel (DM2) +UAFP enables the extraction of specified and custom views from an integrated architecture description (AD) in support of a model-based systems engineering (MBSE) approach. The views describe a system from a set of stakeholders' concerns such as security or information. The UAFP specification supports the Department of Defense Architecture Framework (DoDAF2.02, the Ministry of Defence Architecture Framework (MODAF)Security Views from Canada's Department of National Defense Architecture Framework (DNDAF) and the North Atlantic Treaty Organization (NATO) Architecture Framework (NAF) v 4. The core concepts in the UAF domain metamodel used to specify the UAFP are based upon the DoDAF 2.0.2 Domain Metamodel (DM2) and the MODAF ontological data exchange mechanism (MODEM, which is intended to provide the basis for the next version of NAF). The intent is to provide a standard representation for AD support for Industry, Government, and Defense Organizations. ADs as part of their Systems Engineering (SE) technical processes. UAFP  supports the capability to: 
-MODAF ontological data exchange mechanism (MODEM) +  
-Security Views from Canada's Department of National Defense Architecture Framework (DNDAF) +  * model architectures for a broad range of complex systems, which may include hardware, software, data, personnel, and facility elements; 
-North Atlantic Treaty Organization (NATO) Architecture Framework (NAF) v4 +  * model consistent architectures for system-of-systems (SoSdown to lower levels of design and implementation
-DoDAF, MODEM, and NAF v4 are all based on the International Defence Enterprise Architecture Specification (IDEASontology. The IDEAS-based format for the domain meta-model (DMMallows for the implementation of UAF DMM in non-SysML based tools.+  * support the analysis, specification, design, and verification of complex systems; 
 +  * support cybersecurity analysis, specification, and mitigation of security risks from a system/infrastructure perspective and to aggregate the impact analysis to the operational perspective and cybersecurity risks' impact on the mission; and 
 +  * improve the ability to exchange architecture information among related tools that are SysML based and tools that  are based on other standards.
  
 {{:uaf_what_are_its_sources.png|}} {{:uaf_what_are_its_sources.png|}}
Line 24: Line 26:
  
 The UAF Specification consists of four parts: The UAF Specification consists of four parts:
-- UAF DMM: basis for all tool vendors +  - UAF Domain Metamodel (DMM): basis for all tool vendors 
-- UAF Profile (UAFP): implementation of UAF in SysML  +  - UAF Profile (UAFP): implementation of UAF in SysML  
-- Traceability to other architecture frameworks  +  - Traceability to other architecture frameworks  
-- Search and Rescue (SAR) Example implementation of UAF+  - Search and Rescue (SAR) Example implementation of UAF
 The UAF DMM and Profile are both normative components of the specification, while the traceability and example components are non-normative. UAF can be implemented directly using the UAF DMM, or by using UAFP (for tool vendors that support SysML/UML), or by some other proprietary implementation. The UAF DMM and Profile are both normative components of the specification, while the traceability and example components are non-normative. UAF can be implemented directly using the UAF DMM, or by using UAFP (for tool vendors that support SysML/UML), or by some other proprietary implementation.
 Building from one of these implementations, we can create either NAF v4, UAF, or DoDAF 2.0 views. Building from one of these implementations, we can create either NAF v4, UAF, or DoDAF 2.0 views.
Line 73: Line 75:
 This section will give a brief summary of each of the domains and model kinds shown in the [[start#uaf_gridinformation_vs_presentation|UAF Grid]]. This section will give a brief summary of each of the domains and model kinds shown in the [[start#uaf_gridinformation_vs_presentation|UAF Grid]].
  
 +====== Enterprise Architecture Guide for UAF ======
 +
 +UAF Guide describes a workflow for creating Enterprise Architecture (EA) views in accordance with the Unified Architecture Framework (UAF) Modeling Language (UAFML). This EA Guide for UAF is published as a non-normative component of the UAF specification. It is intended to be used in conjunction with the UAF Sample Problem that defines architecture views for a Search and Rescue Mission. The nine steps of the workflow are laid out in alignment with the stakeholder viewpoints in UAF for producing the requisite architecture views in each of those viewpoints. This underlying architecture description method is an implementation of the Architecture Elaboration process in ISO 42020 and can be used in conjunction with processes for the Conceptualization and Evaluation of an architecture specified in ISO 42020. It can also be used as the basis for an EA modeling methodology, architecture development planning, and modeling project organization and planning. The Guide covers architecting of the enterprise as well as architecting (at a high level) of major entities within the enterprise.
 +
 +{{ :dtc-21-12-13.pdf |}}
  
 ====== Upcoming Events ====== ====== Upcoming Events ======
  
 ^Event Name^Event Date^ Event Location^ ^Event Name^Event Date^ Event Location^
 +| [[https://www.omg.org/events/2022Q1/special-events/UAF-Summit.htm|UAF Summit: ACTIONABLE ARCHITECTURE IN THE 21ST CENTURY - HYBRID event]] | Mar 23, 2022 | Reston, VA USA |
 +| [[https://www.omg.org/events/va-20/special-events/UAF-Summit.htm|ACTIONABLE ARCHITECTURE IN THE 21ST CENTURY]] | Mar 26, 2020 | Reston, VA USA |
 +| [[https://www.omg.org/events/va-20/index.htm|OMG Technical Meeting]] | Mar 23-27, 2020 | Reston, VA USA |
 | [[https://www.omg.org/events/ca-19/index.htm|OMG Technical Meeting]] | Dec 9-13, 2019 | Long Beach, CA USA | | [[https://www.omg.org/events/ca-19/index.htm|OMG Technical Meeting]] | Dec 9-13, 2019 | Long Beach, CA USA |
 | [[https://www.incose.org/iw2020/home|INCOSE International Workshop 2020]] | Jan 25-28, 2020 | Torrance, CA USA | | [[https://www.incose.org/iw2020/home|INCOSE International Workshop 2020]] | Jan 25-28, 2020 | Torrance, CA USA |
Line 98: Line 108:
   - MBSE-inspired Actionable Enterprise Architectures Summit, 2018, Ottawa, Canada https://www.omg.org/events/ottawa-18/special-events/MBSE-EA-Summit.htm   - MBSE-inspired Actionable Enterprise Architectures Summit, 2018, Ottawa, Canada https://www.omg.org/events/ottawa-18/special-events/MBSE-EA-Summit.htm
   - MBSE-inspired Actionable Enterprise Architectures Tutorials, 2018, Ottawa, Canada https://www.omg.org/events/ottawa-18/special-events/MBSE-EA-Tutorials.htm   - MBSE-inspired Actionable Enterprise Architectures Tutorials, 2018, Ottawa, Canada https://www.omg.org/events/ottawa-18/special-events/MBSE-EA-Tutorials.htm
 +  - MBSE-inspired Actionable Enterprise Architectures Summit, 2019, Reston, US https://www.omg.org/events/va-19/special-events/MBSE-EA-Summit.htm
 +  - UAF in the context of the NATO Architecture Framework (NAF), 2019, Amsterdam, Netherlands https://www.omg.org/events/amsterdam-19/special-events/UAF-NATO.htm
start.1574586033.txt.gz · Last modified: 2019/11/24 04:00 by admin