NSOV-1 Service taxonomy (UPDM - NAF aliases)
Creation
To create an NSOV-1 Service Taxonomy:
• Right-click the Architectural Description or Service Description that is to own the NSOV-1 Service Taxonomy, point to New, point to Diagram, point to NAF, and then click NSOV-1 Service Taxonomy.
Purpose
On an NSOV-1 Service Taxonomy:
• Create Service Interface elements and create Generalizations to define inheritance between them.
• Create Service Policy elements and apply them to Service Interface elements.
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), see Creation and appearance of elements that appear on all product diagrams (UPDM - NAF aliases).
Architectural Description
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.
Architectural Reference
To create an Architectural Reference: click the 
Architectural Reference button, click the source Architectural Description or Service Description, and then click the destination Architectural Description or Service Description.
Architectural Reference button, click the source Architectural Description or Service Description, and then click the destination Architectural Description or Service Description.Architecture Metadata
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 or Service Description: click the 
Note Link button, click the Architecture Metadata, and then click the Architectural Description or Service Description to which the Architecture Metadata applies.
Note Link button, click the Architecture Metadata, and then click the Architectural Description or Service Description to which the Architecture Metadata applies.Service Attribute
Service Attribute elements can be shown on their owning Service Interface. To hide Service Attribute elements: through the View Options of the owning Service Interface, do not show Attributes.
Service Description
To create a Service Description: click the 
Service Description button, and then click in free space on the diagram.
Service Description button, and then click in free space on the diagram.To populate elements from a particular Service Description: add the owning Service Description to the diagram, and then populate those elements for the Service Description.
Service Interface
To create a Service Interface: click the 
Service Interface button, and then click in free space on the diagram.
Service Interface button, and then click in free space on the diagram.Use Generalization relationships to define Service Interface inheritance.
Service Operation
Service Operation elements can be shown on their owning Service Interface. To hide Service Operation elements: through the View Options of the owning Service Interface, do not show Operations.
Service Policy
To create a Service Policy: 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.To apply a Service Policy to a Service Interface on the diagram: click the Note Link button, click the Service Policy, and then click the Service Interface to which the Service Policy applies.
Note Link button, click the Service Policy, and then click the Service Interface to which the Service Policy applies.The following sections provide information about how an NSOV-1 Service Taxonomy is used in the model.
Create an NSOV-1 Service Taxonomy 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):
