SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - NAF aliases > Products > System view > NSV-9 Technology and skills forecast definition (UPDM - NAF aliases)
NSV-9 Technology and skills forecast definition (UPDM - NAF aliases)
Creation
To create an NSV-9 Technology and Skills Forecast Definition:
• Right-click the Architectural Description or Service Description that is to own the NSV-9 Technology and Skills Forecast Definition, point to New, point to Diagram, point to NAF, and then click NSV-9 Technology and Skills Forecast Definition.
Purpose
On an NSV-9 Technology and Skills Forecast Definition:
• Create Forecast Span elements and Forecast Span Literal elements for those Forecast Span elements.
• Create Forecast 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:
• Setting up default view options and compartments for a product diagram (UPDM)
• Setting up default view options and compartments for new product diagrams (UPDM)
• Working with compartments on symbols and linked callout notes (UPDM)
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).
To create an Architectural Description: click the 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.
To create an Architecture Metadata: click the 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.
Capability
To create a Capability: click the Capability button, and then click in free space on the diagram.
Use Forecast relationships to link the Capability to forecasted future Capability elements.
To create a Capability Configuration: click the Capability Configuration button, and then click in free space on the diagram.
Use Forecast relationships to link the Capability Configuration to forecasted future Capability Configuration elements.
To create a Competence: click the Competence button, and then click in free space on the diagram.
Use Forecast relationships to link the Competence to forecasted future Competence elements.
Forecast
To create a Forecast: click the Forecast button, click the source element, and then click the destination element.
The source and destination elements must be the same type and they can be as follows: Capability, Capability Configuration, Competence, Organization, Physical Architecture, Post, Resource Artifact, Responsibility, Service Access or Software elements.
To create a Forecast Span: click the Forecast Span button, and then click in free space on the diagram.
After creating a Forecast Span, you can create Forecast Span Literal elements on that Forecast Span.
To create a Forecast Span Literal: click the
Forecast Span Literal button, and then click the owning Forecast Span.
To hide Forecast Span Literal elements shown on the Forecast Span: through the View Options of the owning Forecast Span, do not show Attributes.
To create an Organization: click the Organization button, and then click in free space on the diagram.
Use Forecast relationships to link the Organization to forecasted future Organization elements.
To create a Physical Architecture: click the Physical Architecture button, and then click in free space on the diagram.
Use Forecast relationships to link the Physical Architecture to forecasted future Physical Architecture elements.
To create a Post: click the Post button, and then click in free space on the diagram.
Use Forecast relationships to link the Post to forecasted future Post elements.
To create a Resource Artifact: click the Resource Artifact button, and then click in free space on the diagram.
Use Forecast relationships to link the Resource Artifact to forecasted future Resource Artifact elements.
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.
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.
You can apply a Resource Constraint to Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Responsibility, Service Access and Software elements.
To create a Responsibility: click the Responsibility button, and then click in free space on the diagram.
Use Forecast relationships to link the Responsibility to forecasted future Responsibility elements.
To create a Service Access: click the Service Access button, and then click in free space on the diagram.
Use Forecast relationships to link the Service Access to forecasted future Service Access elements.
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.
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.
You can apply a Service Policy to Capability Configuration, Organization, Physical Architecture, Post, Resource Artifact, Responsibility, Service Access and Software elements.
To create a Software: click the Software button, and then click in free space on the diagram.
Use Forecast relationships to link the Software to forecasted future Software elements.
The following sections provide information about how an NSV-9 Technology and Skills Forecast Definition is used in the model.
Create an NSV-9 Technology and Skills Forecast Definition from
Architectural Description
Service Description
Creates or shows these UPDM elements
Architectural Description
In addition to the common UPDM elements that can be shown on all Product diagrams ( Alias, Definition, Information, Metadata, Overlap and Same As elements):
Architectural Description
Architectural Reference
Architecture Metadata
Capability
Capability Configuration
Competence
Forecast
Forecast Span
Forecast Span Literal
Organization
Physical Architecture
Post
Resource Artifact
Resource Constraint
Responsibility
Service Access
Service Policy
Software