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. 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 UAF grid shows how UAF is organized into different view specifications.
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 does not really illustrate how the information is interrelated.
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''s1212 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.
The 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.
The view creator is a quick way to create diagrams in a specific ArchitecturalDescription without having to access the add new menu. Select a package or element and from the UAF Toolkit menu, then select 'View Creator', this graphic then appears.
by clicking on one of the boxes you can create the relevant diagram in the selected package. The format of the diagram created depends on the aspect you choose; all are based on SysML diagram types. If you want to use this wizard to create diagrams in other areas you must select the new package or element in the model. The state-based diagrams (apart from Strategic States) can only be created under an element based upon structural element such as an OperationalPerformer, Resource, System, Software etc.
This helper is another quick way to create an element of any type in the model. Again, select the element or package that you would like to own the element to be created. Select 'Add New Model Element' from the UAF Toolkit menu.
In the box that opens up you can start typing the name of the element you want to create. You then press Spacebar and Ctrl key this will give you a drop down list of the elements that correspond to the pattern that has been typed.
When you add an InformationExchange (type of information flow) on top of some sort of Connector going between ports or performers. A realization tag is automatically added that takes on the value of the connector. In UAF this information needs to be added to the 'realizingConnector' tag. To populate this tag, you need to select the relevant IBD (containing the connector and info flows) and from the UAF Toolkit menu select 'Set Realizing Connector.' This will then populate the tag (Shown in pink in the figure below).
When using UAF a lot of information in the architecture is contained in tags that relate various elements together. A good example is the tag RealizingConnector which is located on InformationExchanges (based on InformationFlow). See above.
This helper automatically creates allocation dependencies between Activities and the elements that can perform them for each domain in the framework. E.g. Operational, Resource,Service.
If you reallocate the elements on the process diagram you can generate new dependencies, but the helper cannot delete as it has no intelligence as to what is correct. It is advised that you use Synchronize Performs Dependencies when you are sure you have allocated all your activities appropriately.
