SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - MODAF aliases > Elements > Request (UPDM - MODAF aliases)
  
Request (UPDM - MODAF aliases)
Creation
To create a Request:
From a Capability Configuration, Logical Architecture, Organization, Node, Physical Architecture, Post, Resource Artifact, Role Type, Security Domain, Service Access or Software: right-click the element, point to New, point to MODAF, and then click Request.
On the Select Type dialog, create or select the Service Interfaceto use as a type, or create an untyped Request.
From an OV-2 Operational Node Definition or SV-1 Resource Definition: click the Request 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 Request.
From an OV-2 Operational Node Relationship Description:
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 Request. On 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 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 Interfacethat you want to use as the type of the Request, and then drag that Service Interface to the owning Logical Architecture, Known Resource, Node, Node Role, Problem Domainor Security Domainelement 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 the Service Interface to free space.
From an SV-1 Resource Interaction Specification or SV-2 Resource Communications Description:
Click the Request toolbar button, and then click the diagram owner or Resource Role element that is to own the Request. On the Select Type dialog, create or select the Service Interfacethat is the type of the Request, or create an untyped Request.
If the owner of the SV-1 Resource Interaction Specification or SV-2 Resource Communications 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 diagram owner or Resource Role element on the diagram. From the dialog, select Request, and then click OK.
If the owner of the SV-1 Resource Interaction Specification or SV-2 Resource Communications Description is not shown on the diagram, create a Request on the diagram owner by dragging Service Interface to free space.
The diagram owner can be a Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software element.
Appearance
When shown on an OV-2 Operational Node Definitionor SV-1 Resource Definition, a Request appears similar to as follows:
When shown on an OV-2 Operational Node Relationship Description, SV-1 Resource Interaction Specificationor SV-2 Resource Communications Description, a Request appears similar to as follows:
Relationships
The following relationships are of importance to a Request:
Service Channel relationships link a Request to other Request and Service elements.
The following sections provide information about how a Request is used in the model.
Create a Request from
Capability Configuration
Logical Architecture
Node
Organization
Physical Architecture
Post
OV-2 Operational Node Definition
OV-2 Operational Node Relationship Description
Resource Artifact
Role Type
Security Domain
Service Access
SV-1 Resource Definition
SV-1 Resource Interaction Specification
SV-2 Resource Communications Description
Create from a Request
Only the UPDM elements that can be created from all UPDM elements ( Alias, Definition, Information and Metadata).
Shown on these diagrams, tables and matrices
In addition to the AV-2 Integrated Dictionary and TV-1 Standards Profile, which can show all UPDM elements:
OV-2 Operational Node Definition
OV-2 Operational Node Relationship Description
SV-1 Resource Definition
SV-1 Resource Interaction Specification
SV-2 Resource Communications Description
UPDM writeable properties
The following writeable properties are available on the Request tab of a Request element's Property Pages:
connectorRequired
URI