Security domain (UPDM - MODAF aliases)
Creation
To create a Security Domain:
• From an
Architectural Description or
Service Description: right-click the Architectural Description or Service Description, point to New, point to MODAF, point to Operational, and then click Security Domain.
• From a
Security Domain: right-click the Security Domain, point to New, point to MODAF, and then click Security Domain.
Appearance
When shown on an
OV-2 Operational Node Definition or
OV-5 Operational Activity Hierarchy, a Security Domain appears as follows:
When shown on a Security Domain owned
OV-2 Operational Node Relationship Description, a Security Domain appears as follows:
To show the owning Security Domain on an OV-2 Operational Node Relationship Description diagram: right-click the background of the diagram, point to Populate, and then click Owner.
Relationships
The following relationships are of importance to a Security Domain:
•
Is Capable Of Performing relationships link a Security Domain to the
Operational Activity and
Standard Operational Activityelements that the Security Domain can perform.
•
Implements relationships link a Security Domain to the
Capability Configuration elements it implements.
• Used as a conveyed classifier for
Operational Exchange elements.
The following sections provide information about how a Security Domain is used in the model.
Create a Security Domain from
Create from a Security Domain
In addition to 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
AV-2 Integrated Dictionaryand
TV-1 Standards Profile, which can show all UPDM elements:
UPDM writeable properties
The following writeable properties are available on the Security Domain tab of a Security Domain element's Property Pages:
• isEncapsulated
• isExternal
• URI