SV-1 Resource definition (UPDM - MODAF aliases)
Creation
To create an SV-1 Resource Definition:
• Right-click the Architectural Description or Service Description that is to own the SV-1 Resource Definition, point to New, point to Diagram, point to MODAF, and then click SV-1 Resource Definition.
Purpose
On an SV-1 Resource Definition:
• Create Capability, Capability Configuration, Energy, Materiel, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access and Software elements.
• Create Generalizations to define inheritance between the preceding elements.
• Create Property, Request, Resource Role, Service and Resource Operation elements on the preceding elements.
• Create Exhibits relationships.
• Create Resource Constraint and Service Policy elements and apply them to valid elements on the diagram.
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:
For information about the creation and appearance of elements that can be shown on all Product diagrams (Alias, Definition, Information, Metadata, Overlap and Same As elements), click here 
.
.
To create an Architectural Description: click the 
Architectural Description button, and then click in free space on the diagram.
Architectural Description button, and then click in free space on the diagram.To populate elements from an Architectural Description: add the Architectural Description to the diagram, and then populate those elements from the Architectural Description.
To create an Architectural Reference: click the 
Architectural Reference button, click the source Architectural Description, and then click the destination Architectural Description.
Architectural Reference button, click the source Architectural Description, and then click the destination Architectural Description.
To create an Architecture Metadata: click the 
Architecture Metadata button, and then click in free space on the diagram.
Architecture Metadata button, and then click in free space on the diagram.Define the text of the Architecture Metadata through its Full Text property.
To apply an Architecture Metadata to an Architectural Description: click the 
Note Link button, click the Architecture Metadata, and then click the Architectural Description to which the Architecture Metadata applies.
Note Link button, click the Architecture Metadata, and then click the Architectural Description to which the Architecture Metadata applies.
To create a Capability: click the 
Capability button, and then click in free space on the diagram.
Capability button, and then click in free space on the diagram.Use Exhibits relationships to link the Capability to Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software elements that exhibit that Capability.
To create a Capability Configuration: click the 
Capability Configuration button, and then click in free space on the diagram.
Capability Configuration button, and then click in free space on the diagram.Create Property, Request, Resource Role, Service and Resource Operation elements on the Capability Configuration, and use Generalization relationships to define Capability Configuration inheritance.
To create a Capability Property: click the 
Composite Association button, click the owning Capability, and then click the Capability that is the type of the Capability Property.
Composite Association button, click the owning Capability, and then click the Capability that is the type of the Capability Property.Note that only UML Role based Capability Property elements can be shown as Composite Associations. Tell me more...
To hide Capability Property elements shown on the Capability: through the View Options of the owning Capability, do not show Attributes.
To create a Command: click the 
Command Link button, click the source Organization, Post or Role Type, and then click the destination Organization, Post or Role Type.
Command Link button, click the source Organization, Post or Role Type, and then click the destination Organization, Post or Role Type.On the Select Conveyed Classifier dialog, create or select the Exchange Element that is the Command element's conveyed classifier.
To create a Control: click the 
Control Link button, click the source Organization, Post or Role Type, and then click destination Resource Artifact or Software.
Control Link button, click the source Organization, Post or Role Type, and then click destination Resource Artifact or Software.On the Select Conveyed Classifier dialog, create or select the Exchange Element that is the Control element's conveyed classifier.
To create an Energy: click the 
Energy button, and then click in free space on the diagram.
Energy button, and then click in free space on the diagram.Create Property elements on the Energy, and use Generalization relationships to define Energy inheritance.
To create an Exhibits: click the 
Exhibits button, click the source element, and then click the exhibited Capability.
Exhibits button, click the source element, and then click the exhibited Capability.The source element can be a Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software element.
Generalization (UML Item)
To create a Generalization: click the 
Generalization button, click the sub element, and then click the super element. The types of the super and sub elements must be the same.
Generalization button, click the sub element, and then click the super element. The types of the super and sub elements must be the same.You can define inheritance for Capability, Capability Configuration, Energy, Materiel, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software elements.
To create a Materiel: click the 
Materiel button, and then click in free space on the diagram.
Materiel button, and then click in free space on the diagram.Create Property elements on the Materiel, and use Generalization relationships to define Materiel inheritance.
To create an Organization: click the 
Organization button, and then click in free space on the diagram.
Organization button, and then click in free space on the diagram.Create Property, Request, Resource Role, Service and Resource Operation elements on the Organization, and use Generalization relationships to define Organization inheritance.
To create a Physical Architecture: click the 
Physical Architecture button, and then click in free space on the diagram.
Physical Architecture button, and then click in free space on the diagram.Create Property, Request, Resource Role, Service and Resource Operation elements on the Physical Architecture, and use Generalization relationships to define Physical Architecture inheritance.
To create a Post: click the 
Post button, and then click in free space on the diagram.
Post button, and then click in free space on the diagram.Create Property, Request, Resource Role, Service and Resource Operation elements on the Post, and use Generalization relationships to define Post inheritance.
To create a Property: click the 
Property button, and then click the owning element. From the Select Type dialog, create or select the element that is the type of the Property, or create an untyped Property.
Property button, and then click the owning element. From the Select Type dialog, create or select the element that is the type of the Property, or create an untyped Property.The owning element for a Property can be a Capability, Capability Configuration, Energy, Materiel, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software element.
The type of the Property can be a Climate, Condition, Environment, Geo Political Extent Type, Light Condition, Location Type, Measurement Set, Physical Location or Security Attributes Group element.
To hide Property elements shown on the owning element: through the View Options of the owning element, do not show Attributes.
To create a Request: click the 
Request button, and then click the owning element. From the Select Type dialog, create or select the Service Interface that is the type of the Request, or create an untyped Request.
Request button, and then click the owning element. From the Select Type dialog, create or select the Service Interface that is the type of the Request, or create an untyped Request.The owning element for a Request can be a Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software element.
To hide Request elements shown on the owning element: through the View Options of the owning element, do not show Attributes.
To create a Resource Artifact: click the 
Resource Artifact button, and then click in free space on the diagram.
Resource Artifact button, and then click in free space on the diagram.Create Property, Request, Resource Role, Service and Resource Operation elements on the Resource Artifact, and use Generalization relationships to define Resource Artifact inheritance.
To create a Resource Constraint: click the 
Resource Constraint button, and then click in free space on the diagram. Use the Full Text property to specify the text of the Resource Constraint.
Resource Constraint button, and then click in free space on the diagram. Use the Full Text property to specify the text of the Resource Constraint.To apply a Resource Constraint to an element on the diagram: click the Note Link button, click the Resource Constraint, and then click the element to which the Resource Constraint applies.
Note Link button, click the Resource Constraint, and then click the element to which the Resource Constraint applies.You can apply a Resource Constraint to Capability Configuration, Energy, Materiel, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access and Software elements.
To create a Resource Interaction: click the Resource Interaction Link button, click the source Organization, Post or Role Type, and then click destination Resource Artifact or Software.
Resource Interaction Link button, click the source Organization, Post or Role Type, and then click destination Resource Artifact or Software.On the Select Conveyed Classifier dialog, create or select the element that is the Resource Interaction element's conveyed classifier.
To create a Resource Operation: click the 
Resource Operation button, and then click the owning element.
Resource Operation button, and then click the owning element.The owning element can be a Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software element.
To hide Resource Operation elements shown on the owning element: through the View Options of the owning element, do not show Attributes.
To create a Resource Role:
• Click the 
Resource Role button, and then click the owning element. From the Select Type dialog, create or select the element that is the type of the Resource Role, or create an untyped Resource Role.
Resource Role button, and then click the owning element. From the Select Type dialog, create or select the element that is the type of the Resource Role, or create an untyped Resource Role.• Click the Composite Association button, click the owning element, and then click the element that is the type of the Resource Role.
Composite Association button, click the owning element, and then click the element that is the type of the Resource Role.The owning element of the Resource Role can be a Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software element.
The type of the Resource Role can be a Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software element.
Note that when you create a Resource Role through the Resource Role button, the Resource Role is created as a UML Attribute, rather than a UML Role, and it cannot be shown on the diagram as a Composite Association.
Resource Role button, the Resource Role is created as a UML Attribute, rather than a UML Role, and it cannot be shown on the diagram as a Composite Association.To hide Resource Role elements shown on the owning element: through the View Options of the owning element, do not show Attributes.
To create a Role Type: click the 
Role Type button, and then click in free space on the diagram.
Role Type button, and then click in free space on the diagram.Create Property, Request, Resource Role, Service and Resource Operation elements on the Role Type, and use Generalization relationships to define Role Type inheritance.
To create a Service: click the 
Service button, and then click the owning element. From the Select Type dialog, create or select the Service Interface that is the type of the Service.
Service button, and then click the owning element. From the Select Type dialog, create or select the Service Interface that is the type of the Service.The owning element can be a Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access or Software element.
To hide Service elements shown on the owning element: through the View Options of the owning element, do not show Attributes.
To create a Service Access: click the 
Service Access button, and then click in free space on the diagram.
Service Access button, and then click in free space on the diagram.Create Property, Request, Resource Role, Service and Resource Operation elements on the Service Access, and use Generalization relationships to define Service Access inheritance.
To create a Service Policy: click the 
Service Policy button, and then click in free space on the diagram. Use the Full Text property to specify the text of the Service Policy.
Service Policy button, and then click in free space on the diagram. Use the Full Text property to specify the text of the Service Policy.To apply a Service Policy to an element on the 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.You can apply a Service Policy to Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Role Type, Service Access and Software elements.
To create a Software: click the 
Software button, and then click in free space on the diagram.
Software button, and then click in free space on the diagram.Create Property, Request, Resource Role, Service and Resource Operation elements on the Software, and use Generalization relationships to define Software inheritance.
The following sections provide information about how an SV-1 Resource Definition is used in the model.
Create an SV-1 Resource Definition from
Creates or shows these UPDM elements
In addition to the common UPDM elements that can be shown on all Product diagrams (Alias, Definition, Information, Metadata, Overlap and Same As elements):
