OV-3 Operational information exchange matrix (UPDM - MODAF aliases)
Creation
To create an OV-3 Operational Information Exchange Matrix:
• Right-click the
Architectural Description or
Service Description that is to own the OV-3 Operational Information Exchange Matrix, point to New, point to Matrix/Table, point to MODAF, and then click OV-3 Operational Information Exchange Matrix.
• Right-click the
Logical Architecture,
Node or
Security Domain that is to own the OV-3 Operational Information Exchange Matrix, point to New, point to MODAF, and then click OV-3 Operational Information Exchange Matrix.
When you open an OV-3 Operational Information Exchange Matrix, Modeler can generate it as HTML for viewing in your Internet browser, or generate it as a spreadsheet for viewing in Microsoft Excel. To specify how matrices and tables are opened for a model: in the Packages pane, right-click the Model, point to > > , and then select HyperTextMarkupLanguage_HTML or Excel_XLS.
Each time you open an OV-3 Operational Information Exchange Matrix, Modeler generates the product using the latest data from the model.
Purpose
On an OV-3 Operational Information Exchange Matrix:
• View
Operational Exchange elements from the analyzed Packages in a table.
• View the conveyed classifier of each Operational Exchange.
• View
Actual Property Set elements that have been applied to the shown Operational Exchange elements.
• View
Node,
Security Domain,
Operational Activity and
Standard Operational Activity elements that produce and consume each Operational Exchange.
Elements Shown
An OV-3 Operational Information Exchange Matrix shows the following elements.
• A row is created for each Operational Exchange element that produces or consumes a Node or Security Domain that is found in the analyzed Packages.
• The table shows the Name of the Operational Exchange element's conveyed classifier in the column.
• The table shows the Name, Date Range and Intention of each Actual Property Set that is applied to the Operational Exchange.
Note that when a date has not been set, [...] is shown.
• The table shows the Needline elements that realize each Operational Exchange, and the names of the Node, Security Domain, Operational Activity and Standard Operational Activity elements that produce and consume the Operational Exchange.
• The table can also show measurements that apply to the Actual Property Set elements.
To show or hide measurements: right-click the OV-3 Operational Information Exchange Matrix, point to Set, and then click Show Measurements.
Analyzed Packages
For a Logical Architecture, Node or Security Domain owned OV-3 Operational Information Exchange Matrix, the Analyzed Packages are ignored and only the owning element is used to find Operational Exchange elements.
For an Architectural Description or Service Description owned OV-3 Operational Information Exchange Matrix, by default the OV-3 Operational Information Exchange Matrix searches for Operational Exchange elements that produce or consume elements that are contained within the Architectural Description or Service Description that owns the OV-3 Operational Information Exchange Matrix.
To search for elements from other Architectural Description and Service Description packages:
• Right-click the OV-3 Operational Information Exchange Matrix, point to Links, and then click Analyzed Packages. From the Links Editor, select the Architectural Description and Service Description packages from which you want to search for elements.
Example
In this example, the Architectural Description that owns OV-3 Operational Information Exchange Matrix1 contains Node1. Node1 owns an OV-2 Operational Node Relationship Description that defines two Node Role elements that use Node2 and Node3 as their types. Operational Exchange1 is realized by Needline and uses Capability Configuration1 as its conveyed classifier.
We create Actual Property Set1 and set its start date to 2015-01-01 and its end date to 2016-01-01, and then apply Actual Property Set1 to Operational Exchange1. To do this we right-click Operational Exchange1, point to Links, and then click Actual Property Set.
We create Operational Activity1. Operational Activity1 owns an OV-5 Operational Activity Model that defines two Operational Activity Action elements that use Operational Activity2 and Operational Activity3 as their types. We create an Operational Activity Edge (Control Flow) between the two Operational Activity Action elements.
We want Operational Exchange1 to be realized by Operational Activity Edge (Control Flow), so we drag Capability Configuration1 (the conveyed classifier of Operational Exchange1) to the Operational Activity Edge (Control Flow). From the Select Operational Exchange dialog, we select Operational Exchange1.
We now generate OV-3 Operational Information Exchange Matrix1.
from the generated table you can see the following.• A row has been created for each Operational Exchange that produces or consumes an element that is found in the analyzed Packages, that is Operational Exchange1.
• The Operational Exchange1 element's conveyed classifier is shown, that is, Capability Configuration1.
• Actual Property Set1 has been applied to Operational Exchange1, and the date range of Actual Property Set1 is 2015-01-01 to 2016-01-01, and its intent is Estimate.
• Node2 and Operational Exchange2 produce Operational Exchange1, and Node3 and Operational Activity3 consume Operational Exchange1.
The following sections provide information about how an OV-3 Operational Information Exchange Matrix is used in the model.
Create an OV-3 Operational Information Exchange Matrix from
Creates or shows these UPDM elements
