SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - DODAF aliases > Elements > Service port (requires) (UPDM - DoDAF aliases)
  
Service port (requires) (UPDM - DoDAF aliases)
Creation
To create a Service Port (Requires):
From a Performer (System), Operational Context, Organization Type, Performer (Operational), System Context, Person Role Type, System, Responsibility, Security Domain, Service Access or Software: right-click the element, point to New, point to DoDAF, and then click Service Port (Requires).
On the Select Type dialog, create or select the Service Interface to use as a type, or create an untyped Service Port (Requires).
From an OV-2 Operational Resource Definition or SV-1 Systems Interface Definition: click the Service Port (Requires) toolbar button, and then click in free space on the diagram.
On the Select Type dialog, create or select the Service Interface to use as a type, or create an untyped Service Port (Requires).
From an OV-2 Operational Resource Flow Description:
click the Service Port (Requires) toolbar button, and then click the Operational Context, Known Resource, Performer (Operational), Performer Role, Problem Domain or Security Domain element that is to own the Service Port (Requires). On 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 OV-2 Operational Resource Flow Description 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 owning Operational Context, Known Resource, Performer (Operational), Performer Role, Problem Domain or Security Domain element on the diagram. From the dialog, select Service Port (Requires), and then click OK.
If the owner of the OV-2 Operational Resource Flow Description is not shown on the diagram, create a Service Port (Requires) on the diagram owner by dragging the Service Interface to free space.
From an SV-1 Systems Interaction Specification or SV-2 Systems Resource Flow Description:
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). On 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 or SV-2 Systems Resource Flow Description 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 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 or SV-2 Systems Resource Flow Description is not shown on the diagram, create a Service Port (Requires) on the diagram owner by dragging 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.
Appearance
When shown on an OV-2 Operational Resource Definition or SV-1 Systems Interface Definition, a Service Port (Requires) appears similar to as follows:
When shown on an OV-2 Operational Resource Flow Description, SV-1 Systems Interaction Specification or SV-2 Systems Resource Flow Description, a Service Port (Requires) appears similar to as follows:
Relationships
The following relationships are of importance to a Service Port (Requires):
Service Channel relationships link a Service Port (Requires) to other Service Port (Requires) and Service Port (Provides) elements.
The following sections provide information about how a Service Port (Requires) is used in the model.
Create a Service Port (Requires) from
Operational Context
Organization Type
OV-2 Operational Resource Definition
OV-2 Operational Resource Flow Description
Performer (Operational)
Performer (System)
Person Role Type
Responsibility
Security Domain
Service Access
SV-1 Systems Interface Definition
SV-1 Systems Interaction Specification
SV-2 Systems Resource Flow Description
System
System Context
Create from a Service Port (Requires)
Only the UPDM elements that can be created from all UPDM elements ( Representation, Definition, Information, and Metadata).
Shown on these diagrams, tables and matrices
In addition to the AV-2 Integrated Dictionary and StdV-1 Standards Profile, which can show all UPDM elements:
OV-2 Operational Resource Definition
OV-2 Operational Resource Flow Description
SV-1 Systems Interface Definition
SV-1 Systems Interaction Specification
SV-2 Systems Resource Flow Description
UPDM writeable properties
The following writeable properties are available on the Service Port (Requires) tab of a Service Port (Requires) element's Property Pages:
connectorRequired
URI