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.
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.
•
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 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
Create from a Physical Architecture
In addition to the UPDM elements that can be created from all UPDM elements (
Alias,
Definition,
Information and
Metadata):
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:
UPDM writeable properties
The following writeable properties are available on the Physical Architecture tab of a Physical Architecture element's Property Pages:
• isEncapsulated
• URI