SysML, UAF, UML, and UPDM Profiles > UPDM profiles > Products and elements - MODAF aliases > Elements > Physical architecture (UPDM - MODAF aliases)
  
Physical architecture (UPDM - MODAF 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 MODAF, point to System, and then click Physical Architecture.
• From a Physical Architecture : right-click the Physical Architecture, point to New, point to MODAF, and then click Physical Architecture.
• From an SV-1 Resource Definition, SV-4 Functionality Hierarchy, SV-5 Function to Operational Activity/Service Function Definition or SV-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 SV-1 Resource Definition, SV-4 Functionality Hierarchy, SV-5 Function to Operational Activity/Service Function Definition or SV-9 Technology and Skills Forecast Definition, a Physical Architecture appears as follows:
When shown on an SV-1 Resource Interaction Specification or SV-2 Resource 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 ( SV-1 Resource Definition).
• 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
SV-1 Resource Definition
SV-4 Functionality Hierarchy
SV-5 Function to Operational Activity/Service Function Definition
SV-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
SV-1 Resource Interaction Specification
SV-2 Resource Communications Description
SV-6 Systems Data Exchange Matrix
SV-7 Resource Performance Parameters Matrix
SV-10c Resource Event-Trace Description
Shown on these diagrams, tables and matrices
In addition to the AV-2 Integrated Dictionary and TV-1 Standards Profile, which can show all UPDM elements:
AV-5 Capable Performer Matrix
StV-3 Capability Phasing
OV-3 Operational Information Exchange Matrix
StV-5 Capability to Organisation Deployment Mapping
SV-1 Resource Definition
SV-1 Resource Interaction Specification
SV-2 Resource Communications Description
SV-3 Resource Interaction Matrix
SV-4 Functionality Hierarchy
SV-5 Function to Operational Activity/Service Function Definition
SV-5 Function to Operational Activity/Service Function Traceability Matrix
SV-6 Systems Data Exchange Matrix
SV-7 Resource Performance Parameters Matrix
SV-8 Systems Evolution Description
SV-9 Technology and Skills Forecast Definition
SV-9 Technology and Skills Forecast Table
SV-10a Resource Constraints Specification (shows applied Resource Constraint elements)
SV-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