SysML, SysML 2.0, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - DODAF aliases > Products > Operational view > OV-5 Operational activity decomposition tree (UPDM - DoDAF aliases)
OV-5 Operational activity decomposition tree (UPDM - DoDAF aliases)
Creation
To create an OV-5 Operational Activity Decomposition Tree:
Right-click the Architectural Description or Service Description that is to own the OV-5 Operational Activity Decomposition Tree, point to New, point to Diagram, point to DoDAF, and then click OV-5 Operational Activity Decomposition Tree.
Purpose
On an OV-5 Operational Activity Decomposition Tree:
Create Rule (Operational) elements and apply them to Performer (Operational) and Security Domain elements.
Create Service Policy elements and apply them to Operational Context, Performer (Operational) and Security Domain elements.
Diagram Elements
For information about showing compartments on diagram symbols, setting up default view options and adding existing elements to the diagram, see the following topics:
For information about the creation and appearance of elements that can be shown on all Product diagrams (Representation, Definition, Information, Metadata, Overlap and Same As elements), see Notation of Elements that Appear on All Product Diagrams.
To create an Activity Action (Operational): click the Activity Action (Operational) button, click the source Activity (Operational) or Standard Activity (Operational), and then click the destination Activity (Operational) or Standard Activity (Operational).
To create an Activity Maps To Capability: click the Activity Maps To Capability button, click the Activity (Operational) or Standard Activity (Operational), and then click the Capability that is mapped to.
To create an Activity (Operational): click the Activity (Operational) button, and then click in free space on the diagram.
Use Activity Action (Operational) relationships to link the Activity (Operational) to the other Activity (Operational) and Standard Activity (Operational) elements that are invoked by the Activity (Operational).
To create an Activity Performed by Performer: click the Activity Performed by Performer button, click the Performer (Operational) or Security Domain, and then click the Activity (Operational) or Standard Activity (Operational) that can be performed.
To create an Architectural Description: click the Architectural Description button, and then click in free space on the diagram.
To populate elements from an Architectural Description: add the Architectural Description to the diagram, and then populate those elements from the Architectural Description.
To create an Architectural Reference: click the Architectural Reference button, click the source Architectural Description, and then click the destination Architectural Description.
To create an Architecture Metadata: click the Architecture Metadata button, and then click in free space on the diagram.
Define the text of the Architecture Metadata through its Full Text property.
To apply an Architecture Metadata to an Architectural Description: click the Note Link button, click the Architecture Metadata, and then click the Architectural Description to which the Architecture Metadata applies.
To create a Capability: click the Capability button, and then click in free space on the diagram.
Use Activity Maps To Capability relationships to link the Capability to the Activity (Operational) and Standard Activity (Operational) elements that map to that Capability.
To create an Operational Context: click the Operational Context button, and then click in free space on the diagram.
Use Note Links to link the Operational Context to Service Policy elements that apply to the Operational Context.
To create a Performer (Operational): click the Performer (Operational) button, and then click in free space on the diagram.
Use Activity Performed by Performer relationships to link the Performer (Operational) to the Activity (Operational) and Standard Activity (Operational) elements that the Performer (Operational) can perform.
To create a Rule (Operational): click the Rule (Operational) button, and then click in free space on the diagram.
To apply a Rule (Operational) to a Performer (Operational), Activity (Operational) or Standard Activity (Operational) on the diagram: click the Note Link button, click the Rule (Operational), and then click the Performer (Operational), Activity (Operational) or Standard Activity (Operational) to which the Rule (Operational) applies.
To create a Security Domain: click the Security Domain button, and then click in free space on the diagram.
Use Activity Performed by Performer relationships to link the Security Domain to the Activity (Operational) and Standard Activity (Operational) elements that the Security Domain can perform.
To create a Service Policy: click the Service Policy button, and then click in free space on the diagram.
To apply a Service Policy to an Operational Context or Performer (Operational) on the diagram: click the Note Link button, click the Service Policy, and then click the Operational Context or Performer (Operational) to which the Service Policy applies.
To create a Standard Activity (Operational): click the Standard Activity (Operational) button, and then click in free space on the diagram.
Use Activity Action (Operational) relationships to link the Standard Activity (Operational) to the other Standard Activity (Operational) and Activity (Operational) elements that are invoked by the Standard Activity (Operational).
The following sections provide information about how an OV-5 Operational Activity Decomposition Tree is used in the model.
Create an OV-5 Operational Activity Decomposition Tree from
Creates or shows these UPDM elements
In addition to the common UPDM elements that can be shown on all Product diagrams (Representation, Definition, Information, Metadata, Overlap and Same As elements):
Was this helpful?