SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - NAF aliases > Products > Operational view > NOV-6c Operational event-trace description (UPDM - NAF aliases)
  
NOV-6c Operational event-trace description (UPDM - NAF aliases)
Creation
To create an NOV-6c Operational Event-Trace Description:
Right-click the Logical Architecture, Node, or Security Domain that is to own the NOV-6c Operational Event-Trace Description, point to New, point to NAF, and then click NOV-6c Operational Event-Trace Description.
Purpose
On an NOV-6c Operational Event-Trace Description:
Create Node Role, Known Resource and Problem Domain elements.
Create Node Operation messages and Service Operation messages between the preceding elements.
A Node Operation message represents an Operational Activity or Standard Operational Activity on an NOV-6c Operational Event-Trace Description.
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:
Setting up default view options and compartments for a product diagram (UPDM)
Setting up default view options and compartments for new product diagrams (UPDM)
Working with compartments on symbols and linked callout notes (UPDM)
For information about the creation and appearance of elements that can be shown on all Product diagrams (Alias, Definition, Information, Metadata, Overlap and Same As elements), see Creation and appearance of elements that appear on all product diagrams (UPDM - NAF aliases)
In addition to the UML items that can be shown on a UML Sequence Diagram, the following UPDM elements can be created and shown.
Known Resource
To create a Known Resource:
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 Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, 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.
Node Operation
A Node Operation message represents an Operational Activity or Standard Operational Activity on an NOV-6c Operational Event-Trace Description.
To create a Node Operation message:
Click the Node Operation 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 Node Role or Problem Domain.
Click the Node Operation 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 Node Role or Problem Domain.
When you create a Node Operation message, you are prompted to create or select the Node Operation that represents the Operational Activity or Standard Operational Activity you want to show on the NOV-6c Operational Event-Trace Description.
* 
If you create a new Node Operation, you must select the represented Operational Activity or Standard Operational Activity. Modeler sets the name of the Node Operation to that of the represented Operational Activity or Standard Operational Activity.
Node Role
To create a Node Role:
Click the Node Role toolbar button, and then click in free space on the diagram. From the Select Type dialog, create or select the Node or Security Domain to use as a type for the Node Role you are creating.
From a Modeler pane, locate the Node or Security Domain that is to be the type of the Node Role you are creating, and then drag that element to the diagram. From the dialog that appears, select Node Role, and then click OK.
Operational Constraint
To create an Operational Constraint: click the Operational Constraint toolbar button, and then click in free space on the diagram.
To apply an Operational Constraint to an Operational Exchange on the diagram: click the Note Link toolbar button, click the Operational Constraint, and then click the Operational Exchange to which the Operational Constraint applies.
Operational Exchange
To create an Operational Exchange message:
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.
Problem Domain
Problem Domain elements can be created only on NOV-6c Operational Event-Trace Description diagrams that are Logical Architecture 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 Node or Security Domain to use as a type for the Problem Domain you are creating.
From a Modeler pane, locate the Node 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.
Service Operation
To create a Service Operation message: click the Service Operation Message or Service Operation Reply Message toolbar button, in line with the required Statement click the source lifeline, and then click the destination lifeline.
When you create a Service Operation message, you are prompted to select the Service Operation you want to call. The available Service Operation elements are those Service Operation elements that are available through Request and Service ports.
In the following example, Node Role1 appears on the NOV-6c Operational Event-Trace Description. When Node Role1 is the target of a Service Operation Message, Service Operation1 is available for selection.
Service Operation1 is available because the type of Node Role1 is Node2; Node2 owns the port Request1; the type of Request1 is Service Interface1; and Service Interface1 owns Service Operation1.
The following sections provide information about how an NOV-6c Operational Event-Trace Description is used in the model.
Create an NOV-6c Operational Event-Trace Description from
Logical Architecture
Node
Security Domain
Creates or shows these UPDM elements
In addition to the common UPDM elements that can be shown on all Product diagrams ( Alias, Definition, Information, Metadata, Overlap and Same As elements):
Known Resource
Node Operation
Node Role
Operational Constraint
Operational Exchange
Problem Domain
Service Operation