This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
start [2019/11/24 03:49] admin [UAF Grid: Information vs. Presentation] |
start [2022/02/10 08:41] (current) admin |
||
---|---|---|---|
Line 12: | Line 12: | ||
===== What is UAF? ===== | ===== What is UAF? ===== | ||
- | UAF extends | + | 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, |
- | * DoDAF 2.0.2 Domain Metamodel | + | UAFP enables the extraction of specified |
- | * MODAF ontological data exchange mechanism (MODEM) | + | |
- | * Security Views from Canada' | + | * 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 |
- | DoDAF, MODEM, and NAF v4 are all based on the International Defence Enterprise Architecture Specification | + | * support the analysis, specification, |
+ | * support cybersecurity analysis, specification, | ||
+ | * improve the ability to exchange architecture information among related tools that are SysML based and tools that are based on other standards. | ||
{{: | {{: | ||
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 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, | The UAF DMM and Profile are both normative components of the specification, | ||
Building from one of these implementations, | Building from one of these implementations, | ||
Line 37: | Line 39: | ||
{{: | {{: | ||
- | Each row in this grid represents a different domain, and each column represents a different “model kind”. The “domains” can be thought of as the different parts of the underlying information model, while the “model kinds” can be thought of as different standard ways of representing that information. Each cell in the grid is a different view specification or “viewpoint”. UAF defines a metamodel for each viewpoint- the main concepts and relationships you need to build this specific viewpoint. Although the grid is a flat view, think of the information behind each viewpoint in the grid as interrelated. | + | Each row in this grid represents a different domain, and each column represents a different “model kind”. The “domains” can be thought of as the different parts of the underlying information model, while the “model kinds” can be thought of as different standard ways of representing that information. Each cell in the grid is a different view specification or “viewpoint”. UAF defines a metamodel for each viewpoint- the main concepts and relationships you need to build this specific viewpoint. Although the grid is a flat view, think of the information behind each viewpoint in the grid as interrelated. However, this grid view doesn’t really illustrate how the information is interrelated. |
- | This section will give a brief summary of each of the different | + | ==== Information ==== |
+ | |||
+ | A better representation of how the information of each domain is interrelated can be seen below. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | In this diagram, the horizontal boxes are stacked to represent how the domain on top ties to the domain below it. For example, the Strategic view is tied to the Operational view, which is tied to the Resources view, etc. The vertical boxes indicate that that domain spans across all the domains horizontally stacked within the vertical box’s height. For example, the Security view spans across the Operational view and the Personnel and Resources views because the Operational views help define the problem in the Security domain, whereas the Personnel and Resources views help define the solution for that domain. | ||
+ | However, this diagram is a very high-level representation. If you would like to see more detail on which elements tie each of the domains together, a simplified version of the UAF information model can be seen below. | ||
+ | |||
+ | {{:: | ||
+ | |||
+ | The “Behavior” column shows a thread between Capabilities (Strategic domain), the Operational Activities (Operational domain) which break down these Capabilities into logical domains, and the Functions (Resource domain) which maps these Operational Activities onto how they might be realized in the physical domain. The “Agent” column shows who exhibits the Capabilities or performs those behaviors. | ||
+ | |||
+ | ==== Presentation ==== | ||
+ | |||
+ | The UAF model kinds can be mapped to some SysML diagrams, as seen in the table below. | ||
+ | ^ Model Kind^ SysML Diagram^ | ||
+ | | Taxonomy (Tx) | Block Definition Diagram (bdd) | | ||
+ | | Structure (Sr) | Block Definition Diagram (bdd) & Internal Block Diagram (ibd) | | ||
+ | | Connectivity (Cn) | Internal Block Diagram (ibd) | | ||
+ | | Processes (Pr) | Activity Diagram (act) | | ||
+ | | States (St) | State Machine Diagram (stm) | | ||
+ | | Interaction Scenarios (Is) | Sequence Diagram (sd) | | ||
+ | | Information (If) | Block Definition Diagram (bdd) | | ||
+ | | Parameters (Pm) | Block Definition Diagram (bdd) | | ||
+ | | Constrains (Ct) | Block Definition Diagram (bdd) & Parametric Diagram (par) | | ||
+ | | Summary & Overview (Sm-Ov) | Block Definition Diagram (bdd) | | ||
+ | | Requirements (Req) | Requirement Diagram (req) | | ||
+ | The Taxonomy (Tx), Connectivity (Cn), and Parameters (Pm) model kinds can also be thought of as tables. The rest of the model kinds do not have analogous SysML diagrams- however, the Roadmap (Rm) model kind can be thought of as a Gantt chart, the Traceability (Tr) model kind can be thought of as a matrix, and the Dictionary (Dc) model kind can be thought of as a table. | ||
+ | |||
+ | ===== UAF Domains and Model Kinds ===== | ||
+ | |||
+ | 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, | ||
+ | |||
+ | {{ : | ||
====== Upcoming Events ====== | ====== Upcoming Events ====== | ||
^Event Name^Event Date^ Event Location^ | ^Event Name^Event Date^ Event Location^ | ||
+ | | [[https:// | ||
+ | | [[https:// | ||
+ | | [[https:// | ||
| [[https:// | | [[https:// | ||
| [[https:// | | [[https:// | ||
Line 65: | Line 108: | ||
- MBSE-inspired Actionable Enterprise Architectures Summit, 2018, Ottawa, Canada https:// | - MBSE-inspired Actionable Enterprise Architectures Summit, 2018, Ottawa, Canada https:// | ||
- MBSE-inspired Actionable Enterprise Architectures Tutorials, 2018, Ottawa, Canada https:// | - MBSE-inspired Actionable Enterprise Architectures Tutorials, 2018, Ottawa, Canada https:// | ||
+ | - MBSE-inspired Actionable Enterprise Architectures Summit, 2019, Reston, US https:// | ||
+ | - UAF in the context of the NATO Architecture Framework (NAF), 2019, Amsterdam, Netherlands https:// |