The steps and diagrams will be created in order as described in the MBSE with Arcadia method step-by-step for Physical Architecture, and captured again below:
Transition from Logical Architecture
Transition activities from Logical Architecture to Physical Architecture model:
- Perform an automated transition of Logical Functions.
- Perform an automated transition of External Logical Actors.
- Perform an automated transition of Logical System.
- Logical Architecture Capabilities Functional Transition
Physical Architecture Activity explorer, as below:
Perform an automated transition of Logical Functions
Starting with the “Perform an automated transition of Logical Functions” and when Functional Transition window opens, all the candidate model elements will be copied to the resulting model. To copy all elements, click on “Copy all to the right”, as below:
Perform an automated transition of External Logical Actors
Next, “Perform an automated transition of External Logical Actors” and when the Actors Transition window opens, all the candidate model elements will be copied to the resulting model. To copy all elements, click on “Copy all to the right”, as below:
Perform an automated transition of Logical System
Next, “Perform an automated transition of Logical System” and LC / LA to PC / PA Transition window opens, all the candidate model elements will be copied to the resulting model. To copy all elements, click on “Copy all to the right”, as below:
Only part of the Logical Components Breakdown is possible to be shown in the figure above.
Logical Architecture Capabilities Functional Transition
For the Functional Chain transition captured at Logical Architecture to Physical Architecture, it will be used in the Functional Transition of the Logical Capability. This will show another tool capability to transition model elements. For Logical Capability Functional Transition, select from the Project Explorer “Perform Flight On-Board Announcement” Capability, then mouse right-click “Transitions” > “Functional Transitions”, as below:
When the Functional Transition window opens, expand the model packages under synthesis, and the Capability, as below:
When performing the Capability Functional Transition, it will also be transitioned the Functional Chain owned.
When all the above transitions are complete, the Physical Architecture (partly shown) should be as below:
Physical Architecture to Logical Architecture realisation links
Similarly, to Logical Architecture transition, realisation links are created during Physical Architecture transition providing traceability between model elements captured at Physical Architecture and Logical Architecture as figure below:
Realisation links types:
- A: Physical Components realise Logical Components.
- C: Physical Capabilities realise Logical Capabilities.
- F: Physical Functions realise Logical Functions.
- P: Physical Functional Chain realises Logical Functional Chain.
Capabilities Realization at Physical Architecture
Steps to create the Capability Realization Blank diagram, insert Capability Realization and Physical Actor model elements in the diagram are the same as described in section above. The Physical Capability Realisation Blank diagram, as below:
Define Physical Functions
Steps to create Physical Function Breakdown diagram, insert Physical Functions and change Functions background colour are the same as described in previous section. When completed the diagram should be like the one below:
From a design analysis, new functions can be added that are identified and related to specific technologies. New functions were added to the Functional Breakdown structure, as below:
Define Functional Exchanges
The steps and process to insert Functions and Interactions and organise the diagram is like described in the previous section. When completed the Physical Data Flow Blank diagram should be similar to diagram below:
Define Behavioural and Physical Nodes
Steps to create a new Physical Component Breakdown Diagram (PCBD) is the same for Physical as Logical. Create the new PCBD under the Structure package. Organise and change the background colour to white, as below:
From the palette click and create new Node Physical Component (PC) and Behaviour Physical Component (PC):
Create the component breakdown structure, as below:
Allocate functions to Behavioural Nodes and deploy Physical Nodes Components
Node Physical Components, allocate Behavioural Nodes Components, Behavioural Components implement Functions. To make the relationship of model elements the Physical Architecture Blank diagram will be used.
Create a new diagram under Structure package. When diagram opens
- Insert first Node PC in the diagram.
- Next from the palette click on “Manage Node PC’s Deployment” and select the Behavioural PC for each Node.
- When Behavioural PC are allocated to the correspondent node PC, Functions can be shown or allocated to the Behavioural PC.
- Create Component exchanges between Behavioural PC.
- Allocate Component to Function Ports.
When completed the Physical Architecture Blank diagram should be the same as below:
At this level Physical Links can also be captured. Physical Links connect Node PCs.
When Physical Links are defined, Components Ports should be allocated to Physical Ports and define Physical Paths.
Let’s create a first Physical Link “Audio Stream Data Cable” that will allow audio and video streaming between ASU Processor and VSU Processor. Also allocated Physical Ports to Component Ports, as below:
A Physical Link can be created that captures all the Node PC. To create a Physical Path is like creating a Functional Chain. Select all the Physical Links created previously, then mouse right-click and select “Physical Path”. When creating the Physical Path, change the name to “Audio Stream Data Path”. When completed the Audio Stream Data Path is shown in the diagram, as below:
For diagram simplicity, let’s hide Functions and functional Exchanges. To hide both Functions and Functional Exchanges there is only the need to hide Functions. To hide functions, click on the diagram “Filters”, then the “Hide Functions”.
Create the Physical Links, Port allocations and Physical Paths, as below:
Let’s create the Physical Path. Select “Audio Stream Data Path”, then mouse right-click, the “New Physical Path Description”. When completed reorganise the diagram, as below:
Keep the same name as default: [PPD] Audio Stream Data Path
Repeat the process above for the other two Physical Paths.
Describe Capability Realization with Functional Chains and Scenarios
New Physical Functions were created; hence, it is expected to have an invalid Functional Chain, previously transitioned from Logical Architecture. In this section it will be described how to correct the invalid Functional Chain. It will use the Physical Data Flow Blank diagram defined under Perform Flight On-Board Announcements Capability. The Functional Chain shows invalid, as figure blow:
To correct the Functional Chain, select the “Play Imposed Video” Functional Chain, then “New” > “Functional Chain Description”.
Keep the same default name: [PFCD] Play Imposed Video
When corrected the Functional Chain it should be similar to the diagram below:
Scenarios could be created as described in previous sections.
This document includes:
- MBSE Arcadia matrix in one slide
- MBSE with Arcadia steps and diagrams with description
- References to the MBSE with Arcadia step-by-step guide online
