OV-3 Operational resource flow matrix (UPDM - DoDAF aliases)
Creation
To create an OV-3 Operational Resource Flow Matrix:
• Right-click the
Architectural Description or
Service Description that is to own the OV-3 Operational Resource Flow Matrix, point to New, point to Matrix/Table, point to DoDAF, and then click OV-3 Operational Resource Flow Matrix.
• Right-click the
Operational Context,
Performer (Operational) or
Security Domain that is to own the OV-3 Operational Resource Flow Matrix, point to New, point to DoDAF, and then click OV-3 Operational Resource Flow Matrix.
When you open an OV-3 Operational Resource Flow 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 Resource Flow Matrix, Modeler generates the product using the latest data from the model.
Purpose
On an OV-3 Operational Resource Flow Matrix:
u
• View
Operational Exchange elements from the analyzed Packages in a table.
• View the conveyed classifier of each Operational Exchange.
• View
Performer (Operational),
Security Domain,
Activity (Operational) and
Standard Activity (Operational) elements that produce and consume each Operational Exchange.
Elements Shown
An OV-3 Operational Resource Flow Matrix shows the following elements.
• A row is created for each Operational Exchange element that produces or consumes a Performer (Operational) 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 Measure 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 Performer (Operational), Security Domain, Activity (Operational) and Standard Activity (Operational) elements that produce and consume the Operational Exchange.
• The table can also show measurements that apply to the Measure elements.
To show or hide measurements: right-click the OV-3 Operational Resource Flow Matrix, point to Set, and then click Show Measurements.
Analyzed Packages
For an Operational Context, Performer (Operational) or Security Domain owned OV-3 Operational Resource Flow 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 Resource Flow Matrix, by default the OV-3 Operational Resource Flow 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 Resource Flow Matrix.
To search for elements from other Architectural Description and Service Description packages:
• Right-click the OV-3 Operational Resource Flow 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 Resource Flow Matrix1 contains Performer (Operational)1. Performer (Operational)1 owns an OV-2 Operational Resource Flow Description that defines two Performer Role elements that use Performer (Operational)2 and Performer (Operational)3 as their types. Operational Exchange1 is realized by Needline and uses Performer (System)1 as its conveyed classifier.
We create Measure1 and set its start date to 2015-01-01 and its end date to 2016-01-01, and then apply Measure1 to Operational Exchange1. To do this we right-click Operational Exchange1, point to Links, and then click Actual Property Set.
We create Activity (Operational)1. Activity (Operational)1 owns an OV-5 Operational Activity Model that defines two Activity Action (Operational) elements that use Activity (Operational)2 and Activity (Operational)3 as their types. We create a Control Flow (Operational) between the two Activity Action (Operational) elements.
We want Operational Exchange1 to be realized by Control Flow (Operational), so we drag Performer (System)1 (the conveyed classifier of Operational Exchange1) to the Control Flow (Operational). From the Select Operational Exchange dialog, we select Operational Exchange1.
We now generate OV-3 Operational Resource Flow 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, Performer (System)1.
• Measure1 has been applied to Operational Exchange1, and the date range of Measure1 is 2015-01-01 to 2016-01-01, and its intent is Estimate.
• Performer (Operational)2 and Operational Exchange2 produce Operational Exchange1, and Performer (Operational)3 and Activity (Operational)3 consume Operational Exchange1.
The following sections provide information about how an OV-3 Operational Resource Flow Matrix is used in the model.
Create an OV-3 Operational Resource Flow Matrix from
Creates or shows these UPDM elements
