Security domain (UPDM - DoDAF aliases)

SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - DODAF aliases > Elements > Security domain (UPDM - DoDAF 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 DoDAF, point to Operational, and then click Security Domain.

• From a Security Domain: right-click the Security Domain, point to New, point to DoDAF, and then click Security Domain.

• From an OV-2 Operational Resource Definition or OV-5 Operational Activity Decomposition Tree: click the

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

Appearance

When shown on an OV-2 Operational Resource Definition or OV-5 Operational Activity Decomposition Tree, a Security Domain appears as follows:

When shown on a Security Domain owned OV-2 Operational Resource Flow Description, a Security Domain appears as follows:

To show the owning Security Domain on an OV-2 Operational Resource Flow 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:

• Activity Performed by Performer relationships link a Security Domain to the Activity (Operational) and Standard Activity (Operational) elements that the Security Domain can perform.

• Implements relationships link a Security Domain to the Performer (System) elements it implements.

• Trustline relationships link a Security Domain to trusting and trusted Performer (Operational) elements.

• 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

•