SV-4 Systems functionality hierarchy (UPDM

• Right-click the Architectural Description or Service Description that is to own the SV-4 Systems Functionality Hierarchy, point to New, point to Diagram, point to DoDAF, and then click SV-4 Systems Functionality Hierarchy.

On an SV-4 Systems Functionality Hierarchy:

• Create Rule (System) and Service Policy elements and apply them to valid elements on the diagram.

For information about the creation and appearance of elements that can be shown on all Product diagrams (Representation, Definition, Information, Metadata, Overlap and Same As elements), see .

To create an Activity Action (System): click the

Activity Action (System) toolbar button, click the calling Activity (System), and then click the invoked Activity (System).

To create an Activity Maps To Capability: click the

Activity Maps To Capability toolbar button, click the Activity (System), and then click the Capability that is mapped to.

To create an Activity Performed by Performer: click the

Activity Performed by Performer toolbar button, click the source element, and then click the Activity (System) that can be performed.

The source element can be a Performer (System), Organization Type, System Context, Person Role Type, Responsibility, Service Access or Software element.

To create an Activity (System): click the

Activity (System) toolbar button, and then click in free space on the diagram.

Use Activity Performed by Performer relationships to link the Activity (System) to elements that can perform that Activity (System). The following elements can perform an Activity (System): Performer (System), Organization Type, System Context, Person Role Type, Responsibility, Service Access and Software elements.

To create an Architectural Description: click the

Architectural Description toolbar 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 toolbar button, click the source Architectural Description, and then click the destination Architectural Description.

To create an Architecture Metadata: click the

Architecture Metadata toolbar 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 toolbar button, click the Architecture Metadata, and then click the Architectural Description to which the Architecture Metadata applies.

To create a Capability: click the

Capability toolbar button, and then click in free space on the diagram.

Use Activity Maps To Capability relationships to link the Capability to Activity (System) elements that map to that Capability.

To create an Organization Type: click the

Organization Type toolbar button, and then click in free space on the diagram.

Use Activity Performed by Performer relationships to link the Organization Type to the Activity (System) elements that the Organization Type can perform.

To create a Performer (System): click the

Performer (System) toolbar button, and then click in free space on the diagram.

Use Activity Performed by Performer relationships to link the Performer (System) to the Activity (System) elements that the Performer (System) can perform.

To create a Person Role Type: click the

Person Role Type toolbar button, and then click in free space on the diagram.

Use Activity Performed by Performer relationships to link the Person Role Type to the Activity (System) elements that the Person Role Type can perform.

To create a Responsibility: click the

Responsibility toolbar button, and then click in free space on the diagram.

Use Activity Performed by Performer relationships to link the Responsibility to the Activity (System) elements that the Responsibility can perform.

To create a Rule (System): click the

Rule (System) toolbar button, and then click in free space on the diagram. Use the Full Text property to specify the text of the Rule (System).

To apply a Rule (System) to an element on the diagram: click the

Note Link toolbar button, click the Rule (System), and then click the element to which the Rule (System) applies.

You can apply a Rule (System) to Performer (System), Activity (System), Organization Type, System Context, Person Role Type, Responsibility, Service Access and Software elements.

To create a Service Access: click the

Service Access toolbar button, and then click in free space on the diagram.

Use Activity Performed by Performer relationships to link the Service Access to the Activity (System) elements that the Service Access can perform.

To create a Service Policy: click the

Service Policy toolbar 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 toolbar button, click the Service Policy, and then click the element to which the Service Policy applies.

You can apply a Service Policy to Performer (System), Organization Type, System Context, Person Role Type, Responsibility, Service Access and Software elements.

To create a Software: click the

Software toolbar button, and then click in free space on the diagram.

Use Activity Performed by Performer relationships to link the Software to the Activity (System) elements that the Software can perform.

To create a System: click the

System toolbar button, and then click in free space on the diagram.

Use Activity Performed by Performer relationships to link the System to the Activity (System) elements that the System can perform.

To create a System Context: click the

System Context toolbar button, and then click in free space on the diagram.

Use Activity Performed by Performer relationships to link the System Context to the Activity (System) elements that the System Context can perform.

The following sections provide information about how an SV-4 Systems Functionality Hierarchy is used in the model.

SV-4 Systems Functionality Hierarchy from

In addition to the common UPDM elements that can be shown on all Product diagrams ( Representation, Definition, Information, Metadata, Overlap and Same As elements):