The steps and diagrams will be created in order as described in the MBSE with Arcadia method step-by-step for Logical Architecture, and captured again below:
Transition from System Analysis
Transition activities from System Analysis to Logical Architecture model:
- Perform an automated transition of System Functions.
- Perform an automated transition of System Actors.
- Perform an automated transition System Analysis Capabilities.
- Transition of the Functional Chain.
Logical Architecture Activity explorer, as below:
Starting with the Perform an automated transition of System Functions and when the 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:
Note in the figure above that when in the transition it is also transitioned the allocated component ports to functional ports under the structure package.
Repeat the process above for the other two automated transitions.
When completed the activity explorer automated transition the Logical Architecture package should be as below:
Finally, it will be transitioned to the Functional Chain that describes the Perform Flight On-Board Announcements Capability Realisation. To perform a Functional Chain transition, select from the Project Explorer and under “System Analysis > Capabilities” the Play Imposed Video Functional Chain, as below:
Functional Chain transitioned to Logical Architecture:
Functional Chain transitioned to Logical Architecture:
Logical Architecture to System Analysis realisation links
Similarly, to System Analysis transition, realisation links are created during Logical Architecture transition providing traceability between model elements captured at Logical Architecture and System Analysis as figure below:
Realisation links types:
- A: Logical Components (Actors) realise System Actors.
- C: Logical Capabilities realise System Capabilities.
- F: Logical Functions realise System Functions.
- P: Logical Functional Chain realises System Functional Chain.
Capabilities Realization at Logical Architecture
Let’s start creating a new Capability Realization diagram. To create a new Capability Realization diagram, select from the Project Explorer “Capabilities”, then “New Diagram / Table…” > “Capability Realization Blank”, as below:
Keep the same name as default: [CRB] Capabilities.
Insert Actor to Capability Realisation Blank diagram. To insert Actor, select from the Palette and under Tools “Actors”. When the transfer dialog window is shown select only “Cabin Crew”, then “Add selected element(s)” > “Ok”, as below:
Insert Capability Realisation in the diagram, as below:
When completed the Capability Realisation Blank Diagram should be similar as below:
This diagram will not be changed at Logical Architecture; however, it is represented in a diagram what Capability realises the Capability defined at System Analysis, which realises an Operational Capability at Operational Analysis.
Define Logical Functions
The process to define Logical Functions is very similar to System Analysis. To create a Logical Functional Breakdown Diagram, select “Root Logical Function”, then mouse right-click “New Diagram / Table” > “Logical Function Breakdown”, as below:
Keep the same default diagram name: [LFBD] Root Logical Function.
When the Logical Function Breakdown diagram opens change the fill colour to white. This is a good practice that allows to identify what functions were transitioned from System Analysis and that may be refined. Also note that function icon shows “LF”, whilst at System Analysis it was “SF”. When completed the Logical Function Breakdown diagram should be, as below:
Add, resize, and move functions, as Function Breakdown diagram below:
Define Functional Exchanges
Next it will be created a Logical Data Flow Blank diagram that describes the Perform Flight On-Board Announcement Capability Realisation. Select from the Project Explorer “Perform Flight On-Board Announcements”, then mouse right-click “New Diagram / Table…” > “Logical Data Flow Blank”, as below:
Keep the same diagram name as default: [LDFB] Perform Flight On-Board Announcements.
When the diagram opens insert Logical Functions in Logical Data Flow Blank diagram. To insert Logical Functions, select from the Palette “Functions”, then click in a blank area of the diagram. When the transfer dialogue window opens click on “Add all elements” > “Ok”, as below:
When functions are inserted into the diagram, functions will need to resize and moved to make the diagram readable.
Diagram colours are unique to each diagram, hence, there is the need to identify what functions were transitioned and change the fill background to white. After initial rework on the diagram, it should be like the diagram below:
New Functional Exchanges will be created, and some functional ports moved. Creating Functional Exchanges at Logical Architecture is the same as described at System Analysis. Hence, it will not be described again. Create the Logical Data Flow Blank diagram, as bellow:
Define Logical Components
At this point, it will be created a Logical Components Breakdown diagram. To create Logical Breakdown Blank diagram, select from the Project Explorer “Structure” package, then mouse right-click “New Diagram / Table…” > “Logical Component Breakdown”, as below:
Keep the same diagram default name as [LCBD] Structure.
When created and opened the diagram it shows the Logical System and Logical Actors as below:
New Logical Components will be created. To create new Logical Component, select on the Palette “Logical Components”, then click on the Logical System. A new Logical Component will be created. Rename the Logical Component to Aircraft Front Servers, as below:
Repeat the process above and create the Logical Component Breakdown Diagram, as below:
Allocate Logical Functions to Logical Components
To allocate Logical Functions to Logical Components previously created, it will be created the Logical Architecture Blank diagram. To create a new Logical Architecture Blank diagram, select “Logical System” under Structure package, then mouse right-click “New Diagram / Table…” > “Logical Architecture Blank”, as below:
Keep the diagram name as default: [LAB] Logical System
When Logical Architecture Blank diagram is open from the Palette: Insert Components and Actors, as below:
Rearrange and resize Logical Components and Actors as below:
Rearrange and resize Logical Components and Actors as below:
We can now allocate functions to Logical Components. To allocate functions to Logical Components, select from the Palette “Manage Function Allocation”, then click on a Logical Component, select, and add the correspondent Logical Function, as diagram below:
Finally, Component Exchanges and Functional Ports need to be created. To create Components Exchanges and Functional Port allocations, is a similar process as described at System Analysis. When the diagram is complete it should be as below:
Describe Capability Realisation with Functional Chains and Scenarios
The Play Imposed Video Functional Chain was transitioned from System Analysis. It can now be inserted and shown in diagrams. From the palette select “Functional Chain” and click on a blank area of the Logical Architecture Blank diagram, as bellow:
In the diagram next to the Functional Chain name is shown as invalid. Again, the reason is that functions transitioned from System Analysis were refined at Logical Architecture and only leaf functions were allocated to Logical Components. Hence, there is the need to correct the Functional Chain. To correct the functional similarly to what was described at System Analysis, there is the need to create a new Logical Functional Chain Description diagram. To create a new Logical Functional Description diagram, select from the Project Explorer Play Imposed Video Functional Chain, then mouse right-click “New Diagram / Table…” > “Functional Chain Description”, as bellow:
Keep the same diagram name as default: [LFCD] Play Imposed Video.
The Logical Functional Chain Description diagram first time opened should be like below:
When complete the Logical Functional Chain Description diagram should be like the below:
Logical Architecture Blank and Logical Data Flow Blank diagram below showing corrected Functional Chain:
