Security domain (UPDM - MODAF aliases)

SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - MODAF aliases > Elements > 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.

• From an OV-2 Operational Node Definition or OV-5 Operational Activity Hierarchy: click the

Security Domain toolbar button, and then click in free space on the diagram.

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.

• Trustline relationships link a Security Domain to trusting and trusted Nodeelements.

• Used as a type for Concept Role and Problem Domain elements.

• 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