To create an OV-6c Operational Event-Trace Description:
• Right-click the
Operational Context,
Performer (Operational) or
Security Domain that is to own the OV-6c Operational Event-Trace Description, point to New, point to DoDAF, and then click OV-6c Operational Event-Trace Description.
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.
In addition to the UML items that can be shown on a UML Sequence Diagram, the following UPDM elements can be created and shown.
• Click the Known Resource toolbar button, and then click in free space on the diagram. From the Select Type dialog, create or select a type to use for the Known Resource you are creating.
• From a Modeler pane, locate the Performer (System), Organization Type, System Context, Person Role Type, System, Responsibility, Service Access or Software element that is to be the type of the Known Resource you are creating, and then drag that element to the diagram.
• Click the Operational Exchange Message toolbar button, in line with the required Statement click the source lifeline, and then click the destination lifeline.
If the types of the source and destination elements are valid for creating an Operational Exchange, you are prompted to select a conveyed classifier for the Operational Exchange.
For more information about which elements are valid source and destination elements for an Operational Exchange, see the
Operational Exchange topic.
An Operation (Operational) message represents an Activity (Operational) or Standard Activity (Operational) on an OV-6c Operational Event-Trace Description.
To create an Operation (Operational) message:
• Click the Operation (Operational) Message toolbar button, in line with the required Statement click the source lifeline, and then click the destination lifeline. The destination lifeline must be a Performer Role or Problem Domain.
• Click the Operation (Operational) Reply Message toolbar button, in line with the required Statement click the source lifeline, and then click the destination lifeline. The source lifeline must be a Performer Role or Problem Domain.
When you create an Operation (Operational) message, you are prompted to create or select the Operation (Operational) that represents the Activity (Operational) or Standard Activity (Operational) you want to show on the OV-6c Operational Event-Trace Description.
Note that if you create a new Operation (Operational), you must select the represented Activity (Operational) or Standard Activity (Operational). Modeler sets the name of the Operation (Operational) to that of the represented Activity (Operational) or Standard Activity (Operational).
To create an Operation (Service) message: click the Operation (Service) Message or Operation (Service) Reply Message toolbar button, in line with the required Statement click the source lifeline, and then click the destination lifeline.
When you create an Operation (Service) message, you are prompted to select the Operation (Service) you want to call. The available Operation (Service) elements are those Operation (Service) elements that are available through Service Port (Requires) and Service Port (Provides) ports.
In the following example, Performer Role1 appears on the OV-6c Operational Event-Trace Description. When Performer Role1 is the target of an Operation (Service) Message, Operation (Service)1 is available for selection.
Operation (Service)1 is available because the type of Performer Role1 is Performer (Operational)2; Performer (Operational)2 owns the port Service Port (Requires)1; the type of Service Port (Requires)1 is Service Interface1; and Service Interface1 owns Operation (Service)1.
• Click the Performer Role toolbar button, and then click in free space on the diagram. From the Select Type dialog, create or select the Performer (Operational) or Security Domain to use as a type for the Performer Role you are creating.
• From a Modeler pane, locate the Performer (Operational) or Security Domain that is to be the type of the Performer Role you are creating, and then drag that element to the diagram. From the dialog that appears, select Performer Role, and then click OK.
Problem Domain elements can be created only on OV-6c Operational Event-Trace Description diagrams that are Operational Context owned.
To create a Problem Domain:
• Click the Problem Domain toolbar button, and then click in free space on the diagram. From the Select Type dialog, create or select the Performer (Operational) or Security Domain to use as a type for the Problem Domain you are creating.
• From a Modeler pane, locate the Performer (Operational) or Security Domain that is to be the type of the Problem Domain you are creating, and then drag that element to the diagram. From the dialog that appears, select Problem Domain, and then click OK.
To create a Rule (Operational): click the Rule (Operational) toolbar button, and then click in free space on the diagram.
To apply a Rule (Operational) to an Operational Exchange on the diagram: click the Note Link toolbar button, click the Rule (Operational), and then click the Operational Exchange to which the Rule (Operational) applies.
The following sections provide information about how an OV-6c Operational Event-Trace Description is used in the model.
Create an OV-6c Operational Event-Trace Description from