SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - MODAF aliases > Products > Operational viewpoint > OV-2 Operational node relationship description (UPDM - MODAF aliases)
  
OV-2 Operational node relationship description (UPDM - MODAF aliases)
Creation
To create an OV-2 Operational Node Relationship Description:
Right-click the Logical Architecture, Node or Security Domain that is to own the OV-2 Operational Node Relationship Description, point to New, point to MODAF, and then click OV-2 Operational Node Relationship Description.
If you want the owning element to appear on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
Purpose
On an OV-2 Operational Node Relationship Description:
Create Known Resource, Node Role and Problem Domain elements.
Create Node Port, Request and Service elements.
Create Needline and Service Channel relationships.
Create Operational Exchange elements that are realized by Needline 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:
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), click here .
Known Resource
To create a Known Resource:
Click the Known Resource toolbar button, and then click the Logical Architecture, Node, Node Role, Problem Domain or Security Domain element that is to own the Known Resource. From the Select Type dialog, create or select the element that is the type of the Known Resource, or create an untyped Known Resource.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Known Resource on the diagram owner by clicking in free space.
From an appropriate Modeler pane, locate the element that you want to use as the type of the Known Resource, and then drag that element to the owning Logical Architecture, Node, Node Role, Problem Domain or Security Domain element on the diagram. If a dialog is displayed, select Known Resource, and then click OK.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Known Resource on the diagram owner by dragging the element to free space.
The type of a Known Resource can be a Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software element.
Use Needline relationships to link the Known Resource to other elements on the diagram.
Logical Architecture
When you create an OV-2 Operational Node Relationship Description from a Logical Architecture, Modeler does not add the owning Logical Architecture to the diagram.
To show the owning Logical Architecture on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
Needline
To create a Needline: click the Shallow Needline or Shallow Uni-Directional Needline toolbar button, click the source element, and then click the destination element. The source and destination elements can be Known Resource, Node Port, Node Role or Problem Domain elements.
If you want to create the Needline and connecting Node Port elements in one operation, use the Complete Needline toolbar button. You are prompted to select the type of the Node Port elements.
Node
When you create an OV-2 Operational Node Relationship Description from a Node, Modeler does not add the owning Node to the diagram.
To show the owning Node on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
Node Port
To create a Node Port:
Click the Node Port toolbar button, and then click the Node, Node Role, Problem Domain or Security Domain element that is to own the Node Port. From the Select Type dialog, create or select the element that is the type of the Node Port.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Node Port on the diagram owner by clicking in free space.
From an appropriate Modeler pane, locate the element that you want to use as the type of the Node Port, and then drag that element to the edge of the owning Node, Node Role, Problem Domain or Security Domain element on the diagram. If a dialog is displayed, select Node Port, and then click OK.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Node Port on the diagram owner by dragging the element to free space.
The type of a Node Port can be a Capability Configuration, Energy, Exchange Element, Geo Political Extent Type, Logical Architecture, Node, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Security Domain, Service Access or Software element.
Use Needline relationships to link the Node Port to other elements on the diagram.
If you want to create a Needline and connecting Node Port elements in one operation, use the Complete Needline toolbar button. You are prompted to select the type of the Node Port elements.
Node Role
To create a Node Role:
Click the Node Role toolbar button, and then click the Logical Architecture, Node, Node Role, Problem Domain or Security Domain element that is to own the Node Role. From the Select Type dialog, create or select the Node or Security Domain that is the type of the Node Role, or create an untyped Node Role.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Node Role on the diagram owner by clicking in free space.
From an appropriate Modeler pane, locate the Node or Security Domain that you want to use as the type of the Node Role, and then drag that Node or Security Domain to the owning Logical Architecture, Node, Node Role, Problem Domain or Security Domain element on the diagram. If a dialog is displayed, select Node Role, and then click OK.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Node Role on the diagram owner by dragging the element to free space.
Use Needline relationships to link the Node Role to other elements on the diagram.
Operational Constraint
To create an Operational Constraint: click the Operational Constraint toolbar button, and then click in free space on the diagram. You cannot add an Operational Constraint to a Logical Architecture owned OV-2 Operational Node Relationship Description.
To apply an Operational Constraint to a Node or Security Domain on the diagram: click the Note Link toolbar button, click the Operational Constraint, and then click the Node or Security Domain to which the Operational Constraint applies.
Operational Exchange
To create an Operational Exchange: click the Operational Exchange toolbar button, and then click the Needline that realizes the Operational Exchange. The source and destination elements of the Needline must be either a Node Role or Problem Domain.
On the Select Conveyed Classifier dialog, create or select the Operational Exchange element's conveyed classifier. From the context menu, click the command for the destination element.
Problem Domain
To create a Problem Domain, which can be done only on a Logical Architecture owned OV-2 Operational Node Relationship Description:
Click the Problem Domain toolbar button, and then click the Logical Architecture element that is to own the Problem Domain. From the Select Type dialog, create or select the Node or Security Domain that is the type of the Problem Domain, or create an untyped Problem Domain.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Problem Domain on the diagram owner by clicking in free space.
From an appropriate Modeler pane, locate the Node or Security Domain that you want to use as the type of the Problem Domain, and then drag that Node or Security Domain to the owning Logical Architecture element on the diagram. From the dialog, select Problem Domain, and then click OK.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Problem Domain on the diagram owner by dragging the element to free space.
Use Needline relationships to link the Problem Domain to other elements on the diagram.
Request
To create a Request:
Click the Request toolbar button, and then click the Logical Architecture, Known Resource, Node, Node Role, Problem Domain or Security Domain element that is to own the Known Resource. From the Select Type dialog, create or select the Service Interface that is the type of the Request.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Request on the diagram owner by clicking in free space.
From an appropriate Modeler pane, locate the Service Interface that you want to use as the type of the Request, and then drag that Service Interface to the edge of the owning Logical Architecture, Known Resource, Node, Node Role, Problem Domain or Security Domain element on the diagram. From the dialog, select Request, and then click OK.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Request on the diagram owner by dragging Service Interface to free space.
Use Service Channel relationships to link the Request to other Request and Service elements.
Security Domain
When you create an OV-2 Operational Node Relationship Description from a Security Domain, Modeler does not add the owning Security Domain to the diagram.
To show the owning Security Domain on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
Service
To create a Service:
Click the Service toolbar button, and then click the Logical Architecture, Known Resource, Node, Node Role, Problem Domain or Security Domain element that is to own the Service. From the Select Type dialog, create or select the Service Interface that is the type of the Service.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Service on the diagram owner by clicking in free space.
From an appropriate Modeler pane, locate the Service Interface that you want to use as the type of the Service, and then drag that Service Interface to the edge of the owning Logical Architecture, Known Resource, Node, Node Role, Problem Domain or Security Domain element on the diagram. From the dialog, select Service, and then click OK.
If the owner of the OV-2 Operational Node Relationship Description is not shown on the diagram, create a Service on the diagram owner by dragging the Service Interface to free space.
Use Service Channel relationships to link the Service to other Service and Request elements.
Service Channel
To create a Service Channel: click the Shallow Service Channel or Shallow Uni-Directional Service Channel toolbar button, click the source Request or Service, and then click the destination Request or Service.
If you want to create a Service Channel and connecting port elements (Request or Service elements) in one operation, use the Complete Service Channel toolbar button. Choose whether to create source and destination Request or Service elements, and then select the type of those elements.
Service Policy
To create a Service Policy: click the Service Policy toolbar button, and then click in free space on the diagram.
To apply a Service Policy to a Logical Architecture, Node or Security Domain on the diagram: click the Note Link toolbar button, click the Service Policy, and then click the Logical Architecture, Node or Security Domain to which the Service Policy applies.
The following sections provide information about how an OV-2 Operational Node Relationship Description is used in the model.
Create an OV-2 Operational Node Relationship 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
Logical Architecture
Needline
Node
Node Port
Node Role
Operational Constraint
Operational Exchange
Problem Domain
Request
Security Domain
Service
Service Channel
Service Policy