Operational constraint (UPDM - NAF aliases)
Creation
To create an Operational Constraint:
After creating an Operational Constraint, use the Full Text property to specify the text of that Operational Constraint.
Applying to elements
When you create an Operational Constraint it is applied to the owning element, unless the owning element is an Architectural Description, Logical Data Model or Service Description. You can apply an Operational Constraint to many elements.
To apply an Operational Constraint to an element:
• From an appropriate diagram: click the
Note Link button, click the Operational Constraint, and then click the element to which the Operational Constraint applies.
• From an appropriate Modeler pane:
◦ Right-click the Operational Constraint, point to Links, and then click Operationally Constrained Element. On the Links Editor, select the elements to which the Operational Constraint applies.
Appearance
An
NOV-6a Operational Rules Model is useful for viewing which Operational Constraint elements are applied to operational elements.
Relationships
There are no relationships that are of significant importance to an Operational Constraint.
The following sections provide information about how an Operational Constraint is used in the model.
Create an Operational Constraint from
Create from an Operational Constraint
Only the UPDM elements that can be created from all UPDM elements (
Alias,
Definition,
Information and
Metadata).
Shown on these diagrams, tables and matrices
In addition to the
NAV-2 Integrated Dictionary and
NTV-1 Standards Profile, which can show all UPDM elements:
UPDM writeable properties
The following writeable properties are available on the Operational Constraint tab of an Operational Constraint element's Property Pages:
• ruleKind
• URI