SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - NAF aliases > Elements > Physical architecture (UPDM - NAF aliases)
  
Physical architecture (UPDM - NAF aliases)
Creation
To create a Physical Architecture:
From an Architectural Description or Service Description: right-click the Architectural Description or Service Description, point to New, point to NAF, point to System, and then click Physical Architecture.
From a Physical Architecture: right-click the Physical Architecture, point to New, point to NAF, and then click Physical Architecture.
From an NSV-1 Resource Specification, NSV-4 Functionality Hierarchy, NSV-5 Function to Operational Activity/Service Function Definition or NSV-9 Technology and Skills Forecast Definition: click the Physical Architecture toolbar button, and then click in free space on the diagram.
Appearance
When shown on an NSV-1 Resource Specification, NSV-4 Functionality Hierarchy, NSV-5 Function to Operational Activity/Service Function Definition or NSV-9 Technology and Skills Forecast Definition, a Physical Architecture appears as follows:
When shown on an NSV-1 Resource Interaction Specification or NSV-2 System Communications Description, a Physical Architecture appears as follows:
Relationships
The following relationships are of importance to a Physical Architecture:
UML Generalizations define Physical Architecture inheritance ( NSV-1 Resource Specification).
Forecast relationships link a Physical Architecture to forecasted future Physical Architecture elements.
Implements relationships link a Physical Architecture to the Node elements it implements.
Is Capable Of Performing relationships to link a Physical Architecture to the Function elements that can be performed by the Physical Architecture.
Used as a type for Resource Port and Resource Role elements.
Used as a conveyed classifier for Operational Exchange elements.
The following sections provide information about how a Physical Architecture is used in the model.
Create a Physical Architecture from
Architectural Description
Physical Architecture
Service Description
NSV-1 Resource Specification
NSV-4 Functionality Hierarchy
NSV-5 Function to Operational Activity/Service Function Definition
NSV-9 Technology and Skills Forecast Definition
Create from a Physical Architecture
In addition to the UPDM elements that can be created from all UPDM elements ( Alias, Definition, Information and Metadata):
Desired Effect
Function
Physical Architecture
Property
Request
Resource Constraint
Resource Operation
Resource Port
Resource Role
Resource State Machine
Service
Service Policy
NSV-1 Resource Interaction Specification
NSV-2 System Communications Description
NSV-6 Systems Data Exchange Matrix
NSV-7 System Quality Requirements Description
NSV-10c Resource Event-Trace Description
Shown on these diagrams, tables and matrices
In addition to the NAV-2 Integrated Dictionary and NTV-1 Standards Profile, which can show all UPDM elements:
NAV-5 Capable Performer Matrix
NCV-3 Capability Phasing
NOV-3 Operational Information Exchange Matrix
NCV-5 Capability to Organisation Deployment Mapping
NSV-1 Resource Specification
NSV-1 Resource Interaction Specification
NSV-2 System Communications Description
NSV-3 Resource Interaction Matrix
NSV-4 Functionality Hierarchy
NSV-5 Function to Operational Activity/Service Function Definition
NSV-5 Function to Operational Activity/Service Function Traceability Matrix
NSV-6 Systems Data Exchange Matrix
NSV-7 System Quality Requirements Description
NSV-8 Systems Evolution Description
NSV-9 Technology and Skills Forecast Definition
NSV-9 Technology and Skills Forecast Table
NSV-10a Resource Constraints Specification(shows applied Resource Constraint elements)
NSV-12 Service Provision (shows used Service Interface elements)
UPDM writeable properties
The following writeable properties are available on the Physical Architecture tab of a Physical Architecture element's Property Pages:
isEncapsulated
URI