SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - NAF aliases > Products > System view > NSV-1 Resource interaction specification (UPDM - NAF aliases)
NSV-1 Resource interaction specification (UPDM - NAF aliases)
Creation
To create an NSV-1 Resource Interaction Specification:
Right-click the Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Responsibility, Service Access or Software that is to own the NSV-1 Resource Interaction Specification, point to New, point to NAF, and then click NSV-1 Resource Interaction Specification.
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 NSV-1 Resource Interaction Specification:
Create Resource Role, Request and Service elements.
Create Resource Interface relationships.
Create Command, Control and Resource Interaction elements.
Diagram Elements
For information about showing compartments on diagram symbols, setting up default view options and adding existing elements to the diagram, click here
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
When you create an NSV-1 Resource Interaction Specification from a Capability Configuration, Modeler does not add the owning Capability Configuration to the diagram.
To show the owning Capability Configuration on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
To create a Command:
Click the Command button, and then click the Resource Interface that realizes the Command.
The source and destination Resource Role elements must use an Organization, Post or Responsibility as their type.
On the Select Conveyed Classifier dialog, create or select the Exchange Element that is the Command element's conveyed classifier.
On the context menu, click the command for the destination element.
To define that a Command is realized by a Resource Interface:
Drag the Command from a Modeler pane to the Resource Interface on the diagram.
Drag the Command element's conveyed classifier from a Modeler pane to the Resource Interface on the diagram. On the Select Command dialog, select the Command.
Right-click the Resource Interface, point to Links, point to Realized, and then click Command. From the dialog, select the Command elements that are realized by the Resource Interface.
To create a Control:
Click the Control button, and then click the Resource Interface that realizes the Control.
The source Resource Role must use an Organization, Post or Responsibility as its type. The target Resource Role must use a Resource Artifact as its type.
On the Select Conveyed Classifier dialog, create or select the Exchange Element that is the Control element's conveyed classifier.
From the context menu, click either command for the destination element. Irrespective of which command you click, the destination Control will always be the Resource Role that uses a Resource Artifact or Software as its type.
To define that a Control is realized by a Resource Interface:
Drag the Control from a Modeler pane to the Resource Interface on the diagram.
Drag the Control element's conveyed classifier from a Modeler pane to the Resource Interface on the diagram. On the Select Control dialog, select the Control.
Right-click the Resource Interface, point to Links, point to Realized, and then click Control. From the dialog, select the Control elements that are realized by the Resource Interface.
When you create an NSV-1 Resource Interaction Specification from an Organization, Modeler does not add the owning Organization to the diagram.
To show the owning Organization on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
When you create an NSV-1 Resource Interaction Specification from a Physical Architecture, Modeler does not add the owning Physical Architecture to the diagram.
To show the owning Physical Architecture on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
When you create an NSV-1 Resource Interaction Specification from a Post, Modeler does not add the owning Post to the diagram.
To show the owning Post on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
To create a Request:
Click the Request button, and then click the diagram owner or Resource Role element that is to own the Request. From the Select Type dialog, create or select the Service Interface that is the type of the Request, or create an untyped Request.
If the owner of the NSV-1 Resource Interaction Specification 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 diagram owner or Resource Role element on the diagram. From the dialog, select Request, and then click OK.
If the owner of the NSV-1 Resource Interaction Specification is not shown on the diagram, create a Request on the diagram owner by dragging the Service Interface to free space.
The diagram owner can be a Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Responsibility, Service Access or Software element.
When you create an NSV-1 Resource Interaction Specification from a Resource Artifact, Modeler does not add the owning Resource Artifact to the diagram.
To show the owning Resource Artifact on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
To create a Resource Constraint: click the Resource Constraint button, and then click in free space on the diagram.
To apply a Resource Constraint to an element on the diagram: click the Note Link button, click the Resource Constraint, and then click the element to which the Resource Constraint applies.
You can apply a Resource Constraint to Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Responsibility, Service Access or Software elements.
To create a Resource Interaction:
Click the
Resource Interaction button, and then click the Resource Interface that realizes the Resource Interaction.
On the Select Conveyed Classifier dialog, create or select the element that is the Resource Interaction element's conveyed classifier.
From the context menu, click either command for the destination element.
To define that a Resource Interaction is realized by a Resource Interface:
Drag the Resource Interaction from a Modeler pane to the Resource Interface on the diagram.
Drag the Resource Interaction element's conveyed classifier from a Modeler pane to the Resource Interface on the diagram. On the Select Resource Interaction dialog, select the Resource Interaction.
Right-click the Resource Interface, point to Links, point to Realized, and then click Resource Interaction. From the dialog, select the Resource Interaction elements that are realized by the Resource Interface.
To create a Resource Interface: click the Shallow Resource Interface or Shallow Uni-Directional Resource Interface button, click the source Resource Role, and then click the destination Resource Role.
To create a Resource Role:
Click the Resource Role button, and then click the diagram owner or Resource Role element that is to own the Resource Role. From the Select Type dialog, create or select the element that is the type of the Resource Role, or create an untyped Resource Role.
If the owner of the NSV-1 Resource Interaction Specification is not shown on the diagram, create a Resource Role by clicking in free space.
From an appropriate Modeler pane, locate the element that you want to use as the type of the Resource Role, and then drag that element to the diagram owner or Resource Role element on the diagram.
The type of a Resource Role can be a Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Responsibility, Service Access or Software element.
If the owner of the NSV-1 Resource Interaction Specification is not shown on the diagram, create a Resource Role by dragging the element to free space.
Use Resource Interface relationships to link the Resource Role to other Resource Role elements.
When you create an NSV-1 Resource Interaction Specification from a Responsibility, Modeler does not add the owning Responsibility to the diagram.
To show the owning Responsibility on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
To create a Service:
Click the Service button, and then click the diagram owner or Resource Role 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, or create an untyped Service.
If the owner of the NSV-1 Resource Interaction Specification 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 diagram owner or Resource Role element on the diagram. From the dialog, select Service, and then click OK.
If the owner of the NSV-1 Resource Interaction Specification is not shown on the diagram, create a Service on the diagram owner by dragging the Service Interface to free space.
The diagram owner can be a Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Responsibility, Service Access or Software element.
When you create an NSV-1 Resource Interaction Specification from a Service Access, Modeler does not add the owning Service Access to the diagram.
To show the owning Service Access on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
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 element on the diagram: click the Note Link button, click the Service Policy, and then click the element to which the Service Policy applies.
You can apply a Service Policy to Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Responsibility, Service Access or Software elements.
When you create an NSV-1 Resource Interaction Specification from a Software, Modeler does not add the owning Software to the diagram.
To show the owning Software on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
The following sections provide information about how an NSV-1 Resource Interaction Specification is used in the model.
Create an NSV-1 Resource Interaction Specification from
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):