Service (UPDM - MODAF aliases)
Creation
To create a Service:
• From a Capability Configuration, Logical Architecture, Node, Organization, 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 Service.
On the Select Type dialog, create or select the Service Interface to use as a type, or create an untyped Service.
• From an OV-2 Operational Node Definition: click the Service button, and then click the owning Node, Logical Architecture or Security Domain element. On the Select Type dialog, create or select the Service Interface to use as a type, or create an untyped Service.
Service button, and then click the owning Node, Logical Architecture or Security Domain element. On the Select Type dialog, create or select the Service Interface to use as a type, or create an untyped Service.• From an SV-1 Resource Definition: click the Service button, and then click the owning Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software.
Service button, and then click the owning Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software.On the Select Type dialog, create or select the Service Interface to use as a type, or create an untyped Service.
◦ Click the Service button, and then click the Logical Architecture, Known Resource, Node, Node Role, Problem Domainor Security Domain element that is to own the Service. On the Select Type dialog, create or select the Service Interface that is the type of the Service.
Service button, and then click the Logical Architecture, Known Resource, Node, Node Role, Problem Domainor Security Domain element that is to own the Service. On 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 Interfacethat you want to use as the type of the Service, and then drag that Service Interface to 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.
◦ Click the Service button, and then click the diagram owner or Resource Role element that is to own the Service. On the Select Type dialog, create or select the Service Interface that is the type of the Service, or create an untyped Service.
Service button, and then click the diagram owner or Resource Role element that is to own the Service. On 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 SV-1 Resource Interaction Specification or SV-2 Resource Communications 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 diagram owner or Resource Role element on the diagram. From the dialog, select Service, 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 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, Role Type, Service Access or Software element.
Appearance
When shown on an OV-2 Operational Node Definition or SV-1 Resource Definition, a Service appears similar to as follows:
When shown on an OV-2 Operational Node Relationship Description, SV-1 Resource Interaction Specification or SV-2 Resource Communications Description, a Service appears similar to as follows:
Relationships
The following relationships are of importance to a Service:
The following sections provide information about how a Service is used in the model.
Create a Service from
Create from a Service
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:
SV-12 Service Provision(shows in context of system resource elements using Service Interface elements)UPDM writeable properties
The following writeable properties are available on the Service tab of a Service element's Property Pages:
• connectorRequired
• URI