SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - DODAF aliases > Products > Systems view > SV-1 Systems interaction specification (UPDM - DoDAF aliases)
  
SV-1 Systems interaction specification (UPDM - DoDAF aliases)
Creation
To create an SV-1 Systems Interaction Specification:
Right-click the Performer (System), Organization Type, System Context, Person Role Type, System, Responsibility, Service Access or Software that is to own the SV-1 Systems Interaction Specification, point to New, point to DoDAF, and then click SV-1 Systems 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 SV-1 Systems Interaction Specification:
Create Resource Role, Service Port (Requires) and Service Port (Provides) elements.
Create System Interface relationships.
Create Command, Control and Resource Exchange 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 (Representation, Definition, Information, Metadata, Overlap and Same As elements), see Creation and appearance of elements that appear on all product diagrams (UPDM - DoDAF aliases).
Command
To create a Command:
Click the Command toolbar button, and then click the System Interface that realizes the Command.
The source and destination Resource Role elements must use an Organization Type, Person Role Type 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 System Interface:
Drag the Command from a Modeler pane to the System Interface on the diagram.
Drag the Command element's conveyed classifier from a Modeler pane to the System Interface on the diagram. On the Select Command dialog, select the Command.
Right-click the System Interface, point to Links, point to Realized, and then click Command. From the dialog, select the Command elements that are realized by the System Interface.
Control
To create a Control:
Click the Control toolbar button, and then click the System Interface that realizes the Control.
The source Resource Role must use an Organization Type, Person Role Type or Responsibility as its type. The target Resource Role must use a System 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 System or Software as its type.
To define that a Control is realized by a System Interface:
Drag the Control from a Modeler pane to the System Interface on the diagram.
Drag the Control element's conveyed classifier from a Modeler pane to the System Interface on the diagram. On the Select Control dialog, select the Control.
Right-click the System Interface, point to Links, point to Realized, and then click Control. From the dialog, select the Control elements that are realized by the System Interface.
Organization Type
When you create an SV-1 Systems Interaction Specification from an Organization Type, Modeler does not add the owning Organization Type to the diagram.
To show the owning Organization Type on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
Performer (System)
When you create an SV-1 Systems Interaction Specification from a Performer (System), Modeler does not add the owning Performer (System) to the diagram.
To show the owning Performer (System) on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
Person Role Type
When you create an SV-1 Systems Interaction Specification from a Person Role Type, Modeler does not add the owning Person Role Type to the diagram.
To show the owning Person Role Type on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
Resource Exchange
To create a Resource Exchange:
Click the Resource Exchange toolbar button, and then click the System Interface that realizes the Resource Exchange.
On the Select Conveyed Classifier dialog, create or select the element that is the Resource Exchange element's conveyed classifier.
From the context menu, click either command for the destination element.
To define that a Resource Exchange is realized by a System Interface:
Drag the Resource Exchange from a Modeler pane to the System Interface on the diagram.
Drag the Resource Exchange element's conveyed classifier from a Modeler pane to the System Interface on the diagram. On the Select Resource Exchange dialog, select the Resource Exchange.
Right-click the System Interface, point to Links, point to Realized, and then click Resource Interaction. From the dialog, select the Resource Exchange elements that are realized by the System Interface.
Resource Role
To create a Resource Role:
Click the Resource Role toolbar 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 SV-1 Systems 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 Performer (System), Organization Type, System Context, Person Role Type, System, Responsibility, Service Access or Software element.
If the owner of the SV-1 Systems Interaction Specification is not shown on the diagram, create a Resource Role by dragging the element to free space.
Use System Interface relationships to link the Resource Role to other Resource Role elements.
Responsibility
When you create an SV-1 Systems 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.
Rule (System)
To create a Rule (System): click the Rule (System) toolbar button, and then click in free space on the diagram.
To apply a Rule (System) to an element on the diagram: click the Note Link toolbar button, click the Rule (System), and then click the element to which the Rule (System) applies.
You can apply a Rule (System) to Performer (System), Organization Type, System Context, Person Role Type, System, Responsibility, Service Access or Software elements.
Service Access
When you create an SV-1 Systems 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.
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 an element on the diagram: click the Note Link toolbar button, click the Service Policy, and then click the element to which the Service Policy applies.
You can apply a Service Policy to Performer (System), Organization Type, System Context, Person Role Type, System, Responsibility, Service Access or Software elements.
Service Port (Provides)
To create a Service Port (Provides):
Click the Service Port (Provides) toolbar button, and then click the diagram owner or Resource Role element that is to own the Service Port (Provides). From the Select Type dialog, create or select the Service Interface that is the type of the Service Port (Provides), or create an untyped Service Port (Provides).
If the owner of the SV-1 Systems Interaction Specification is not shown on the diagram, create a Service Port (Provides) 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 Port (Provides), 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 Port (Provides), and then click OK.
If the owner of the SV-1 Systems Interaction Specification is not shown on the diagram, create a Service Port (Provides) on the diagram owner by dragging the Service Interface to free space.
The diagram owner can be a Performer (System), Organization Type, System Context, Person Role Type, System, Responsibility, Service Access or Software element.
Service Port (Requires)
To create a Service Port (Requires):
Click the Service Port (Requires) toolbar button, and then click the diagram owner or Resource Role element that is to own the Service Port (Requires). From the Select Type dialog, create or select the Service Interface that is the type of the Service Port (Requires), or create an untyped Service Port (Requires).
If the owner of the SV-1 Systems Interaction Specification is not shown on the diagram, create a Service Port (Requires) 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 Port (Requires), 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 Port (Requires), and then click OK.
If the owner of the SV-1 Systems Interaction Specification is not shown on the diagram, create a Service Port (Requires) on the diagram owner by dragging the Service Interface to free space.
The diagram owner can be a Performer (System), Organization Type, System Context, Person Role Type, System, Responsibility, Service Access or Software element.
Software
When you create an SV-1 Systems 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.
System
When you create an SV-1 Systems Interaction Specification from a System, Modeler does not add the owning System to the diagram.
To show the owning System on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
System Context
When you create an SV-1 Systems Interaction Specification from a System Context, Modeler does not add the owning System Context to the diagram.
To show the owning System Context on the diagram: right-click the background of the diagram, point to Populate, and then click Owner.
System Interface
To create a System Interface click the Shallow System Interface or Shallow Uni-Directional System Interface toolbar button, click the source Resource Role, and then click the destination Resource Role.
The following sections provide information about how an SV-1 Systems Interaction Specification is used in the model.
Create an SV-1 Systems Interaction Specification from
Organization Type
Performer (System)
Person Role Type
Responsibility
Service Access
Software
System
System Context
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):
Command
Control
Organization Type
Performer (System)
Person Role Type
Resource Exchange
Resource Role
Responsibility
Rule (System)
Service Access
Service Policy
Service Port (Provides)
Service Port (Requires)
Software
System
System Context
System Interface