NOV-6a Operational rules model (UPDM - NAF aliases)
Creation
To create a NOV-6a Operational Rules Model:
• Right-click the
Architectural Description or
Service Description that is to own the NOV-6a Operational Rules Model, point to New, point to Matrix/Table, point to NAF, and then click NOV-6a Operational Rules Model.
When you open an NOV-6a Operational Rules Model, 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 NOV-6a Operational Rules Model, Modeler generates the product using the latest data from the model.
Purpose
On an NOV-6a Operational Rules Model:
• View which
Operational Constraint elements are applied to the operational elements that are shown in the table.
Elements Shown
The table can show the following operational elements:
Exchange Element,
Mission,
Mission Use Case,
Node,
Operational Activity,
Operational Constraint,
Security Domain and
Standard Operational Activity elements.
For each operational element, the NOV-6a Operational Rules Model shows the
Operational Constraint elements that are applied to that operational element.
For information about how to apply an Operational Constraint to an operational element, see the
Operational Constraint topic.
Analyzed Packages
By default, the NOV-6a Operational Rules Model searches for the operational elements that are contained within the Architectural Description or Service Description that owns the NOV-6a Operational Rules Model.
To search for operational elements from other Architectural Description and Service Description packages: right-click the NOV-6a Operational Rules Model, 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 operational elements.
Example
In this example, the model is set up to generate tables and matrices as Excel spreadsheets. The Architectural Description that owns NOV-6a Operational Rules Model1 contains two operational elements, Operational Activity1 and Operational Activity2. Operational Activity1 has Operational Constraint1 applied to it, Operational Activity2 does not have any Operational Constraint elements applied to it.
When the Excel spreadsheet is generated for NOV-6a Operational Rules Model1, you can see from the table that Operational Activity1 has Operational Constraint1 applied to it, and Operational Activity2 does not have any Operational Constraint elements applied to it.
The following sections provide information about how an NOV-6a Operational Rules Model is used in the model.
Create an NOV-6a Operational Rules Model from
Creates or shows these UPDM elements
