Operational context (UPDM - DoDAF aliases)

SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - DODAF aliases > Elements > Operational context (UPDM - DoDAF aliases)

Creation

To create an Operational Context:

• 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 Operational Context.

• From an Operational Context: right-click the Operational Context, point to New, point to UPDM and then click Operational Context.

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

Operational Context 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, an Operational Context appears as follows:

On an OV-2 Operational Resource Definition or OV-5 Operational Activity Decomposition Tree you can use Note Links to link an Operational Context to the Service Policy elements that apply to that Operational Context.

When shown on an Operational Context owned OV-2 Operational Resource Flow Description, an Operational Context appears as follows:

To show the owning Operational Context 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 an Operational Context:

• UML Generalizations define Operational Context inheritance ( OV-2 Operational Resource Definition).

• Used as a conveyed classifier for Operational Exchange elements.

The following sections provide information about how an Operational Context is used in the model.

Create an Operational Context from

•