Service policy (UPDM - MODAF aliases)
Creation
To create a Service Policy:
• From an
Architectural Description or
Service Description: right-click the Architectural Description or Service Description, point to New, point to MODAF, point to Service, and then click Service Policy.
• From a
Capability Configuration,
Logical Architecture,
Node,
Organization,
Physical Architecture,
Post,
Resource Artifact,
Role Type,
Security Domain,
Service Access,
Service Interface or
Software: right-click the element, point to New, point to MODAF, and then click Service Policy.
• From an
OV-2 Operational Node Definition,
OV-2 Operational Node Relationship Description,
OV-5 Operational Activity Hierarchy,
SOV-1 Service Taxonomy,
SOV-2 Service Interface Specification,
SOV-3 Capability to Service Definition,
SOV-5 Service Functionality,
SV-1 Resource Definition,
SV-1 Resource Interaction Specification,
SV-2 Resource Communications Description,
SV-4 Functionality Hierarchy,
SV-5 Function to Operational Activity/Service Function Definition or
SV-9 Technology and Skills Forecast Definition: click the Service Policy button, and then click in free space on the diagram.
Service Policy button, and then click in free space on the diagram.After creating a Service Policy, use the Full Text property to specify the text of that Service Policy.
Applying to elements
When you create a Service Policy it is applied to the owning element, unless the owning element is an Architectural Description or Service Description. You can apply a Service Policy to many elements.
To apply a Service Policy to an element:
• From an appropriate diagram: click the 
Note Link button, click the Service Policy, and then click the element to which the Service Policy applies.
Note Link button, click the Service Policy, and then click the element to which the Service Policy applies.• From an appropriate Modeler pane:
Right-click the element, point to Links, point to Applied, and then click Service Policy. From the Links Editor, select the Service Policy elements that apply to the element.
You can apply an Operational Constraint to
Capability Configuration,
Logical Architecture,
Node,
Organization,
Physical Architecture,
Post,
Resource Artifact,
Role Type,
Security Domain,
Service Access,
Service Interface and
Software elements.
Appearance
When shown on an
OV-2 Operational Node Definition,
OV-2 Operational Node Relationship Description,
OV-5 Operational Activity Hierarchy,
SOV-1 Service Taxonomy,
SOV-2 Service Interface Specification,
SOV-3 Capability to Service Definition,
SOV-5 Service Functionality,
SV-1 Resource Definition,
SV-1 Resource Interaction Specification,
SV-2 Resource Communications Description,
SV-4 Functionality Hierarchy,
SV-5 Function to Operational Activity/Service Function Definition or
SV-9 Technology and Skills Forecast Definition diagram, a Service Policy appears as follows:
Relationships
There are no relationships that are of significant importance to a Service Policy.
The following sections provide information about how a Service Policy is used in the model.
Create a Service Policy from
Create from a Service Policy
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 Dictionaryand
TV-1 Standards Profile, which can show all UPDM elements:
UPDM writeable properties
The following writeable properties are available on the Service Policy tab of a Service Policy element's Property Pages:
• ruleKind
• URI