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.

MBSE Arcadia step-by-step quick guide

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

Download PDF867 Downloads

The post Capella Physical Architecture practical example first appeared on Hélder Castro.

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:

The post Capella Logical Architecture practical example first appeared on Hélder Castro.

Read more: System Analysis

Transition from Operational Analysis

A Capella transition is the mechanism that enables the tool to create model elements and links (aka traceability) at one layer from another.
Model elements transitions are performed to transition model elements from Operational Analysis to System Analysis. When you transition model elements, Capella creates traceability links from System Analysis to Operational Analysis and can be explored using the Activity Explorer modelling tool. In the Activity Explorer (considering it is open) and:

• Under transition from Operational Analysis:
  • Automated transition of Operational Activities.
• Under define Actors, Missions, and Capabilities:
  • Contextually create new System Actor from Operational Entities / Actors.
  • Contextually create new System Capability or Mission from Operational Capability.
• Operational Process transition

Automated transition of Operational Analysis

To perform an automated transition of Operational Activities, click on “Automated transition of Operational Activities”, as below:

The below functional transition window shows three columns:

The below functional transition window shows three columns:

• Synthesis: this column shows the difference between candidate and resulting model.
• Candidate model: it provides the ability to select what model elements will be part of the resulting model.
• Resulting model: shows a preview of the model when performed the transition.

Click on “Copy all to the right” and then “Ok” to perform the transition and close the window.

Contextually create new System Capability or Mission from Operational Capability

Let’s do the automated transition of Operational Capabilities in context with the Operational Actors from the Activity Explorer. From the Activity Explorer click on “Contextually create new System Capability or Mission from Operational Capability”, as below:

Then select “System Capability”, as below:

From the Capability Transition window, you can see realisation and the transformation links from System Analysis to Operational Analysis:

Click on “Copy all to the right” and then “Ok” to perform the transition and close the window.

A final transition for Operational Process

The Play Imposed Video Operational Process describes the Perform Flight On-Board Announcements Operational Capability. We will perform a “Function Transition” to transition the Operational Process.

To transition, select from the Project Explorer, select Play Imposed Video Operational Process at Operational Analysis, then mouse right-click “Transitions” > “Functional Transition”, as below:

The Operational Process functional transition will create involvement links (aka references) to the System Functions referenced by the System Functional Chain. It will also create a realisation link from System Capability to Operational Capability, as below :

Contextually create new System Actor from Operational Entities / Actors

Finally, we will perform a System Actor from Operational Entities / Actors transition. Click on “Contextually create new System Actor from Operational Entities / Actors”, as below:

From the selection dialog, select the Operational Entity and the two Operational Actors (i.e., Passenger and Cabin Crew), as below:

In the Operational Entity to System Actor Transition window, it creates System Actors, System Actor realisation links, but also transformation links (i.e., Operational Entities and Actors to System Actors) and Allocation links, as below:

Click on “Copy all to the right” and then “Ok” to perform the transition and close the window. When completed the System Analysis should look like below:

System Analysis to Operational Analysis realisation links

The realisation links highlighted in sections above, create and allow traceability between model elements captured at System Analysis and Operational Analysis as captured in the figure below:

Realisation links types:

• A: System Actors realise Operational Entities and Actors.
• C: System Capabilities realise Operational Capabilities.
• F: System Functions realise Operational Activities.
• P: Functional Chain realises Operational Process.

Capture Context System Actors

To define a new Context System Actor diagram, select from the Project Explorer and under Structure “System”, then mouse click “New Diagram / Table…” > “Contextual System Actors”, as below:

For this example, the name remains as default: [CSA] System:

Define Missions and System Capabilities

To create a new Missions and System Capabilities diagram, select from Project Explorer “System”, then mouse right-click “New Diagram / Table…” > “Missions Capabilities Blank”, as below:

Let’s start to insert the transitioned Capability in the diagram. From Palette select “Capabilities”, then click on a blank area of the diagram and “Add selected element(s)”, as below:

To insert transitioned System Actor, select from the Palette “Actors”, then click on a blank area of the diagram, then select “Cabin Crew” and “Add selected element(s)”, as below:

To finish this diagram, create the “Provide Cabin Management Solutions Mission” and the Capability exploitation from the Mission to Perform Flight On-Board Announcements Capability, as below:

Define System Functions Breakdown Structure

To create a new System Function Breakdown Structure diagram, select from Project Explorer “Root System Function”, then mouse right click “New Diagram Table…” > “System Function Breakdown”, as below:

You can change the diagram name, but for this example we will keep the same diagram name as default.

We will now refine the Broadcast Movies function allocated to the Aircraft.

To create a new function, select from the Palette “System Function”, then click on the Broadcast Movies function. It creates a new function and containment link. Rename the new function to Play Audio in Cabin, as below:

Repeat the process above and create two new functions contained by Broadcast Movies, as below:

We can change the colour of the Broadcast Movies function to white. This is a proposed practise and visual reference, only, to help to identify transitioned functions and traceability.

Define Functional Exchanges

Next we will create a System Data Flow Blank diagram for the Perform Flight On-Board Announcements Capability. To create a new System Data Flow Blank diagram, select Perform Flight On-Board Announcements Capability, then mouse right-click “New Diagram / Table…” > “System Data Flow Blank”, as below:

You can keep the same default diagram name: [SDFB] Perform Flight On-Board Announcements. When diagram created select from the Palette “Functions”, then click on a blank area of the diagram. The below Transfer Dialog window will open. Select “Add all elements”:

Organise the functions and change the colour of the Broadcast Movies to white, as below:

Move the ports as below:

• From Broadcast Movies (in) to Store Digital Media.
• From Broadcast Movie (out) to Broadcast Audio Video Stream.

Create the Functional Exchange:

• Audio Stream.
• Audio Signal.
• Audio Video Media.

Rearrange the System Functions and ports. The finished System Data Flow Blank diagram, should be similar as below:

Allocate System Functions to System Components and Actors

Let’s create a System Architecture Blank diagram.

First, rename the model element System. Select “System” from Project Explorer and rename to In-flight Entertainment. To create a new System Architecture Blank diagram, select System, then mouse right-click “New Diagram / Table…” > “System Architecture Blank”, as below:

You can keep the same default name: [SAB] In-flight Entertainment.

To insert System Actors into System Architecture Blank diagram, select from the Palette “Actors” then “Add all elements”, as below:

When Actors inserted to the diagram, rearrange, and resize as below:

Let’s insert allocated System Functions to System and Actors. Start by allocating functions to System. Select from Palette “Allocated Functions” then click on In-flight Entertainment System model element. When you see the Transfer Dialog window, select the three functions and click “Add selected element(s)”, as below:

Repeat the process above for Passenger and Cabin Crew Actor. Rearrange and resize the functions as below:

Let’s reallocate system functions. Select Play Audio in Cabin function and drag from In-flight Entertainment to Aircraft, as below:

Aircraft System Actor allocates the Play Audio in Cabin function, hence, the System Data Flow Blank Diagram and System Functional Breakdown Blank diagram updates. You can visualise the function colour changes from green (functions allocated to the System) to blue (functions allocated to Actors):

We will now create the Components Exchanges between all Actors and the In-flight Entertainment. To create new Component Exchange, select from the Palette “Component Exchange”, then click on “Cabin Crew” and then “In-flight Entertainment”, as below:

Functional Exchanges allocate to Component Exchanges. Component Exchanges implement Functional Exchanges.

To create Port Allocation, select from the Palette “Port Allocation”, then click on Component Port owned by Cabin Crew, then click on Function Port owned by Cabin Crew, as below:

Repeat the process above to create the Component Exchanges and Port Allocations, and rename Component Exchanges as below:

Now that Component Exchanges and Port Allocation is complete, there is the need to make sure all Component Exchanges and Port Allocations directions are consistent. Let’s update both ports directions for Imposed Video Playing Status Component Exchange to IN OUT to reflect consistency with Functional Input and Output ports.

To change Component Port direction double click on one Component Port and when the Properties Window opens change the direction to INOUT, as below:

Repeat the process above for the other Component Port. When changed the Component Port directions the System Architecture Blank should be as below:

Use the diagram filters, as figure below to:

• Collapse Component Ports.
• Hide Component Exchanges.
• Hide Port Allocations.

When filters applied the diagram should look like above [SAB] In-flight Entertainment reallocated function figure.

Describe System Capability with Functional Chains

Functional Chains can be created in either System Architecture Blank or System Data Flow Blank diagram in a similar process to the described for the Operational Analysis is section above.

For this example, we will insert the Functional Chain transitioned from Operational Analysis. To insert the Play Imposed Video Function, select from the Palette “Functional Chain” then click on a blank area of the SDFB diagram. When the transfer dialog shows select the Functional Chain and click “Add selected element(s), as below:

Notice that when inserted the Functional Chain next to its name it is shown as invalid. The reason is the Broadcast Movies System Function was broken down and Function Ports delegated. Hence, new leaf functions are added, but not reflected on the Functional Chain.

To correct the Functional Chain there is the need to create a System Functional Chain Description diagram. To create a System Functional Chain Description diagram, select the Play Imposed Video Functional Chain, then mouse right-click “Functional Chain” > “Create a Functional Chain”, as below:

Keep the same default diagram name: [SFCD] Play Imposed Video.

When created the new Play Imposed Video System Functional Chain Description you can see there is a function with no interactions, as below.

The following updates to the System Functional Chain Description:

• Delete from diagram Broadcast Movies. As a reminder this function was initially defined at Operational Analysis, transitioned to System Analysis, and finally refined in two more functions as described in previous section. In addition, the Arcadia rule that only leaf functions should be allocated. In addition, Broadcast Movies is also part of the Operational Process. As the Operational Process was transitioned and Play Imposed Video Functional Chain was created. Hence, Broadcast video belongs to the Functional Chain, but needs to be deleted and only leaf functions should be reference in the Functional Chain
• Insert the new refined functions captured at System Analysis: Play Audio in Cabin.
• Broadcast Audio Video Stream and Store Digital Media are already part of the Functional Chain as the ports were delegated from Broadcast Movies to each function and as described previously.
• Create Exchange between:
  • Broadcast Audio Video Streams and Play Imposed Movie Functional Chain Involvement Function.
  • Play Audio in Cabin to Watch Movie Functional Chain Involvement Function.
• Create Exchange and Function:
  • From Broadcast Audio Video Streams to Play Audio in Cabin.
  • Store Digital Media and Broadcast Audio Video Streams Functional Chain Involvement Function. There is the need to add this new function as Capella prevents closed loops.

When completed the System Functional Chain Description the diagram should be similar to:

Use the Exchange and Exchange and Function from the Palette to add Functional Exchange involvement Functions and links. Functional Chains updated and inserted in System Data Flow Blank and System Architecture Blank diagrams:

Describe System Capability with Functional and Entity Scenarios

Functional and Entity Scenarios describe System Capabilities. You can create Scenarios in a similar way to Operational Scenarios described in Operational Analysis page.

MBSE Arcadia step-by-step quick guide

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

Download PDF867 Downloads

The post Capella System Analysis practical example first appeared on Hélder Castro.

Let’s get started with the example.

The steps and diagrams will be created in the same order as described in the MBSE with Arcadia method step-by-step for Operational Analysis, and captured again below:

Capture Operational Entities and Actors

As captured in the Operational analysis activities matrix, first needs to be created an Operational Entity Breakdown diagram (OEBD). New diagrams can be created from the Capella Activity Explorer; however, we will use the project explorer to create a new diagram under the package Operational Entities.

To create a new Operational Entity Breakdown diagram, select from the project explorer “Operational Entities”, then mouse right-click “New Diagram / Table…” > “Operational Entity Breakdown”, as below:

When the Operational Entity Breakdown window is open, a new name can be given to the diagram. It was chosen not to change the diagram name, as below:

With the [OEBD] open, select first from the Palette the correspondent model element and then click on the diagram to create the Operational Entity OE 1, Operational Actor OA 2 and OA 3, as below:

 Let’s rename the model elements created. To open the model element Property window, double click on an element, for example Operational Entity (OE 1) and rename to Operational Users, as below:

Repeat step above to rename Operational Actors (OA 2 and OA 3), as below:

Capture Operational Capabilities

The Operational Capabilities diagram will be created next and not renamed.

From Project Explorer, select Operational Capabilities package, then mouse right-click “New Diagram / Table” > “Operational Capabilities Blank”, as below:

Keep the same name as default: [OCB] Operational Capabilities

From the Palette, to show Operational Actor Cabin Crew, select “Operational Actors”, then click on a blank area of the diagram to open the Transfer Dialog, as below:

In the Palette, select “Operational Capability”, and click on a diagram blank area to create the Operational Capability 1.

From the Palette, select “Involvement”, then click on the previously created Operational Capability 1 in the diagram, then click on the “Cabin Crew” Operational Actor to create an involvement link between the two, as below:

Double click on the Operational Capability and rename it to: Perform Flight On-Board Announcements:

The Operational Capability diagram showing the model elements relevant to this view:

Define Operational Activities

This section will describe how to capture Operational Activities with the Operational ActivityBreakdown Diagram.

A new Operational Activity Breakdown Diagram (OABD) can be created from the project explorer and under an Operational Activity. To create an OABD, select “Root Operational Activity”, then click “New Diagram / Table…” > “Operational Activity Breakdown”, as below:

Create Operational Activity Breakdown Diagram

When the “New Operational Activity Breakdown” window opens, rename the diagram to: In-flight Operational Activity:

From the Palette create three Operational Activities in the diagram:

• Broadcast Movies.
• Watch Movie.
• Play Imposed Movie.

Define Operational Activities Interactions

Next step will be to create Operational Activities Interactions Blank (OAIB) diagram, where Operations Activities can be captured. OAIB diagrams can be created under:

• An Operational Activity.
• Operational Capability (OC). When created under the OC model element, activities are related and describe the Operational Capability.

For this example, an OAIB will be created under the Operational Capability that describes it. To create a new OAIB, select Perform Flight On-Board Announcements Operational Capability, then mouse right-click “New Diagram / Table…” > “Operational Activity Interaction Blank”:

Keep the same diagram default name: [OAIB] Perform On-Board Announcements.

When the OAIB diagram is created,  select “Operational Activities” from the Palette and then click on the blank area of the diagram to show the Transfer dialog window. In the Transfer dialog window select all three Operational Activities and then “Add All Elements” to add only the three Operational Activities, then click “Ok” to close window:

Reorganise the Operational Activities and create the first Operational Interaction. To create the Operational Interaction, select in the Palette “Interaction”, then click on the “Play Imposed Movie” then on “Broadcast Movies” Operational Activities, as below:

Repeat the process above and create a new Interaction between Broadcast Movies and Watch Movie.

Next let’s change the Interaction name. To rename the Interaction 1, double click on the “Interaction 1”. When the Properties window opens, rename interaction to Safety Instructions. Repeat the rename process for Interaction 2. When completed the OAIB diagram should be as below:

Allocate Operational Activities

Operational Activities should be allocated to Operational Entities or Actors that are responsible to execute them. For this it will be created an Operational Architecture Blank (OAB) diagram where it will be shown Operational Entities and Actors and allocated Operational Activities.

To create an Operational Architecture Blank diagram, select “Operational Entities” in the Project Explorer, then mouse right-click “New Diagram / Table…” > “Operational Architecture Blank”, as below:

When the New Operational Architecture Blank window shows, leave the name as default: [OAB] Operational Entities and click “Ok”.

Let’s insert Operational Entities and Actors to the diagram. To insert Operational Entities to the OAB diagram, select in the Palette “Operational Entities”, then click on a blank area of the OAB diagram, then “Add all Elements” > “Ok”, as bellow:

To insert Operational Actors, click on the arrow next to Operational Entities to show Operational Actors in the Palette. In the transfer dialogue click on “Add all elements” > “Ok”:

When Operational Entities and Actors are inserted into the Operational Architecture Blank diagram, it should be shown as below:

To allocate Operational Activities to Operational Actors select “Manage Activity Allocation” then click on the Passenger Operational Actor shown in the diagram, as below:

When the transfer dialogue opens, select “Play Imposed Movie”, then “Add selected element(s)” > ”Ok”:

Repeat the process above to Manage Activity Allocation for Passenger and Aircraft as below:

Interactions are also added to the diagram as they were previously defined in the OAIB diagram in the previous step. The OAB diagram can be a good diagram candidate to not only Manage Activity Allocation, but also define new Interactions now in context with structure (i.e., Operational Entities and Actors) and behaviour (i.e., Operational Activity).

Describe Operational Capabilities with Operational Process

Perform Flight On-Board Announcements Operational Capability was previously described by the relevant Operational Activities captured in the OAIB diagram under the Operational Capability. Operational Capabilities can also be described with Operational Process. Operational Process references what Operational Activities and Interactions are considered relevant to describe an Operational Capability, but also to show in diagrams the flow of Activities and Interactions.

An Operational Process could be created from this diagram; however, it will be created from the OAIB diagram instead. As the OAIB diagram is defined under the Operational Capability, any Operational Process created will also be created under the same Operational Capability promoting consistency.

To create an Operational Process, Hold Ctrl, then select all three Operational Activities and the two Interactions, then mouse right-click on a model element (e.g., Watch Movie) > “Operational Process” > “Create an Operational Process”, as below:

Rename the new Operational Process to Play Imposed Video as below:

The Play Imposed Video Operational Process defined in the Operational Architecture Interaction Blank diagram should look as below:

To create an Operational Process Description (OPD), select “Perform Imposed Video” Operational Process from the Project Explorer, then mouse right-click “New Diagram / Table…” > “Operational Process Description”, as below:

When the New Operational Process Description window shows, do not rename the diagram and confirm the default name provided as [OPD] Play Imposed Video and click “Ok”.

The below Operational Process Diagram is automatically created showing the three Operational Activities referenced by the Operational Process:

An Operational Process can also be shown in the Operational Architecture Blank diagram. Inserting an Operational Process in a diagram not only shows the flow of Operational Activities and Interactions, but also what Operational Entities and Actors are involved in a diagram. If more Operational Processes were defined a combination of insert/remove can be performed to help the analysis process.

To insert an Operational Process in the Operational Architecture Blank diagram, in the Palette select “Operational Process”, then click on a blank area of the diagram. The Transfer dialogue window will be shown, then click “Add selected elements(s)” > “Ok”, as below:

When inserted the Operational Process into the Operational Architecture Blank diagram it should be seen as below:

Describe Operational Capabilities with Operational Activity and Entity Scenarios

Operational Capabilities can be described by Operational Process that describes and involves Operational Activities and Interactions above but can also be described by Operational Activity and Entity Scenarios.

To create new Operational Activity Scenarios, select from the Project Explorer the “Perform Flight On-Board Announcements” Operational Capability, then mouse right-click “New Diagram / Table…” > “Activity Scenario”, as below:

When the New Activity Scenario is shown, keep the default name and click “Ok”.

It is created a new Operational Activity Scenario diagram under the Operational Capability, as below:

To add Operational Activities to the diagram, select Activities in the Palette, then when the Transfer Dialogue window opens select the three Operational Activities, then click “Add selected element(s)” > “Ok”. By selecting the three Operational Activities will not add the Root Operational Activity to the diagram.

Resize Operational Activities to show full name in diagram and reorder them. Operational Activity Scenario should be as below:

To add Interaction to the Operational Activity Scenario, select “Interaction” from the Palette, then click first on the Play Imposed Movie Operational Activity’ lifeline and then on the Broadcast Movies Operational Activity lifeline, as below:

When the Selection Dialog window opens, select “Safety Instructions [Play Imposed Movie -> Broadcast Movies]”, then “Ok”:

Repeat the process above for the other Interaction between Broadcast Movies and Watch Movie and add “Imposed Movies [Broadcast -> Watch Movie]”.

When completed the Operational Activity should be like as below:

An Operational Entity Scenario can also be chosen to describe an Operational Capability.

To create an Operational Entity Scenario, the steps are like above described for Operational Activity Scenario. Select Perform Flight On-Board Announcements Operational Capability from Project Explorer, then mouse right-click “New Diagram / Table…” > “Entity Scenario”, as below:

Keep the same diagram default name: [OES] Perform On-Board Announcements.

Select “Operational Entities / Actors” and “Interaction” from the Palette. When completed the diagram should be as below:

The above steps allow to create new Operational Activities and Entity Scenarios under an Operational Capability.

As the Play Imposed Video Operational Process is created, Capella does provide the capability to transition and initialise Operational Activities and Entity Scenarios, to represent time-ordered scenarios.

To create a new Operational Activity Scenario from an Operational Process, open the Operational Architecture Blank diagram, then mouse right-click on the “Play Imposed Video” Operational Process, then “Transitions” > “Operational Process to Operational Activity Scenario Initialization”, as below:

Transitions can also be done by selecting the “Play Imposed Video” Operational Process from the Project Explorer and then follow the same steps as described above.

Capella creates a new Play Imposed Video 3 Operational Activity Scenario under the Perform Flight On-Board Announcements Operational Capability, as below:

The number 3 in the name represents the third scenario created under the Operational Scenario. 

Now let’s create the Operational Activity Scenario to show model elements in a diagram.

To create Operational Activity Scenario, select Play Imposed Video 3 Operational Activity, then click “New Diagram / Table…” > “Activity Scenario”, as below:

The new Operational Activity Scenario created may need to be rearranged to show the same as the All Interaction inserted in Operational Activity Scenario described above.

To create a transition for the Operational Entity Scenario, select “Play Imposed Video 3” Operational Activity from the Project Explorer, then click “Transitions” > “Operational Activity Scenario to Operational Entity Scenario Initialization”, as below:

An Operational Entity Scenario can be created similarly to described for Operational Activity Scenario above, select “Play Imposed Video 3 (OES) in the Project Explorer, then mouse right-click “New Diagram / Table…” > “Entity Scenario”, as below:

When the New Entity Scenario window is shown, keep the same diagram as proposed: [OES] [OAS] Play Imposed Video 3 (OES).

A new diagram is created and visible in the Project Explorer: [OES] [OAS] Play Imposed Video 3 (OES) and the new Operational Entity Scenario diagram is open. The diagram model elements and display should be similar to the Operational Entity Scenario described above.

There is freedom in Capella to create the diagrams in any sequence.

Despite elements in Scenarios represent only references to model element, this means Scenarios are not synched with the model evolution, hence, consistency and completeness needs to be checked. Links created during the transition helps to verify consistency, correctness, and completeness of diagrams in a model.

For this simple example, Operational Activity and Entity Scenarios diagrams do share the same model elements and Operational Capability description. The reason was to describe the option to create Scenarios from an Operational Process using the Capella Transition capability.

Hence, the below will be performed in the model:

• Delete the Perform On-Board Announcements Operational Activity Scenario.
• Delete the Perform Flight On-Board Announcements Operational Entity Scenario.
• Rename both Scenario and diagram for Play Imposed Video 3 Operational Activity Scenario to Play Imposed Video.
• Rename Play both Scenario and diagram for Imposed Video 3 (OES) Operational Entity Scenario to Play Imposed Video. It could be left (OES) to visualise the Scenario was transitioned.

The Operational Analysis project explorer at this point should look as below:

Operational Analysis traceability flow

When completed the model for Operational Analysis Project Explorer should look like as below:

As described in sections above, the Capella tool implements the Arcadia method, and the Arcadia method owns an ontology. Arcadia ontology defines model elements and the relationship among them enabling inherent traceability. Hence, it is possible in Capella to query and navigate from one model element to another.

For this example and only for the Operational Analysis (similar analysis can be done for all the other layers), it will be described as an example of how model elements are related via their relationship and navigate from one to another model element using a combination of Project Explorer and the Semantic Browser.

Starting with the Project Explorer. The steps for the model elements navigation are captured in the figure above (yellow) and again below:

• (start) Perform Flight-Onboard Announcements Operational Capability.
• Play Imposed Video Operational Process.
• Watch Movie Operational Activity.
• (end) Passenger Operational Entity.

In the Project Explorer select the Perform Flight On-Board Announcements Operational Capability. The Operational Capability will be shown in the Semantic Browser under the current element area. Under the Referenced Elements area it can be seen the Play Imposed Video Operational Process. Select and press F8. This Capella command will navigate back Project Explorer and to the Play Imposed Video Operational Process model element.

To navigate from Play Imposed Operational Process to Watch Movie Operational Activity, select first the “Play Imposed Video” Operational Process in the Project Explorer then in the Semantic Browser, select “Watch Movie” Operational Activity and press F8 to navigate to model element as below:

Finally, let’s navigate from Watch Movie Operational Activity to Passenger Operational Actor.

Select “Watch Video” Operational Activity from the Project Explorer, then under Referencing Elements select “Passenger” and click F8 to navigate to model element in Project Explorer, as below:

Capella creates links between model elements that are going to be explored hereafter. 

By default, let’s make sure links will be visible. Click on “View Menu” > “Filters and Customisation”, as below:

When the Filters and Customisation window opens locate the following filters:

• Functional Chains involvements
• Trace

Let’s make sure the filters are not set. An example for Trace filter bellow:

Figure below, shows relevant links that allow the same navigation between model elements as described above using the semantic browser and the relationship between model elements. Links are captured and can be seen in the Project Explorer highlighted in blue in figure above.

When completed the analysis above, let’s set the filters

Set Default Filters. Click on “View Menu” > then “Set Default Filters”.

MBSE Arcadia step-by-step quick guide

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

Download PDF867 Downloads

The post Capella Operational Analysis practical example first appeared on Hélder Castro.

You can find install instructions for the Capella requirements viewpoint captured under the wiki Requirements VP.

Referencing Capella requirements viewpoint

First step, ensure requirement viewpoint is active, tool and model elements contributed by this viewpoint are available. Viewpoint Manager allows to activate the viewpoint.

Open the “Viewpoint Manager” view in Capella. Go to “Window” > “Show View” > “Other…”, open the “Kitalpha” category and select “Viewpoint Manager”. Select a model element, right click on “Capella Requirements” view and click “Reference”.

Check viewpoint works correctly. Right click on a model element, example Operational Analysis package) and verify the Requirements Viewpoint menu is available:

Filters and customisation

Capella requirements VP elements are hidden by default. First, open the Capella Project Explorer menu and choose “Filters and Customization…”:

Locate and uncheck the filters:

• Requirements VP Attributes.
• Requirements VP Relations.
• Requirements VP Types.

Trace (needed if there is the intention to view traces in the project explorer).

Capella Types Folder

In Capella, is available different types of modules:

• Module Type: allows defining module type, example, Stakeholder Requirements, System requirements.
• Relation Type: allows to define relationship between textual requirements, and textual requirements and model elements.
• Requirement Type: allows to define different types of requirements. This example, defines to types: functional and interface.

No mandatory sequence when creating Types, however, requirements are:

• Captured at a different level of abstraction, example, Stakeholder or System requirements.
• Traced to model elements or between textual requirements.
• Type, example, functional and interface.

You can create a Capella Types Folder for each of the above types. Then, creating requirements in the model is possible, associate to a Requirement Type and create relationship with other elements.

It is relevant at this point to mention, that all the Types created at Operational Analysis layer will be visible to all lower layers. Types defined at lower layers are not visible at higher layers. There may be the case where Types are better defined at lower layers, for example, Module Types when capturing system or physical requirements.

To create a Capella Types Folder, mouse right-click on the package Operational Analysis, then the menu “Add Capella Element” > “Capella Types Folder”, as shown in the figure below:

Rename the Capella Types Folder. One way to rename the Capella Types Folder is to open the Capella Types Folder properties window by double-clicking on the Capella Types Folder. The below window opens:

Rename the Capella Type Folder to Module definition.

Repeat the process above to create and rename Capella Type Folder for Relation and Requirement Type. Types shown in the Capella model:

Types definition

Creating a new Capella Type Folder, right-click followed by “Add Capella Element” > “Module Type”, as below:

Repeat the process above for Relation and Requirement Definition and create the below types:

Requirement Data Type and Attribute definition

Textual requirements normally are associated to attributes, example, status (e.g., draft, reviewed) and priority (e.g., high, medium, or low). Attributes can be tailored and defined to fulfil specific project needs.

Requirement Data Type definition

Create new model elements “Enumeration Data Types Definition” within the Requirements Definition Capella Types Folder.

Enumeration Data Type will allows to define enumeration values to set the requirements “Data Type”, as described in a section below. Create a new requirement type, mouse right-click on the Capella Types Folder and select “Add Capella Element” > “Enumeration Data Type Definition” as shown in the below figure:

Rename the Enumeration Data Type to “Status”.

Repeat the process above for a new data type: Priority.

The content within the Requirement Definition Capella Data Folder should be as below:

Requirement Definition Enumeration Data Types

For each of “Enumeration Data Types” defined above, create “Enum Value” to define the available attribute for each requirement. Create a new enumeration value, right-click on each of the “Enumeration Data Type Definition” previously created, “Add Capella Element” > “Enum Value” menu. Create the below “Enum Value” list as the figure below:

Requirements Attribute definition

Requirements attributes can be created and associated to Enumeration Data Type previously created.

Associating Enumeration Data Types to Requirement Data Type, will allow to:

• Reuse data type.
• Update data type, as needed, and reflected in all Requirement Type associated to the data type. Hence, there will be the need to update data once. This is of great value to promote data (i.e., requirements attributes) consistency.

Create new attributes, right-click on the Functional requirement type, then “Add Capella Element” > “Attribute Definition Enumeration menu”, as follows:

In the project explorer click on the created Status Attribute Definition Enumeration and rename it in the “Properties”. Click on “Browse Available Elements”. When Selection Dialogue window opens, Associate the Data Type to the Requirements Status Enumeration Data Type created previously, as below:

Repeat the process above and create the priority Attribute Definition Enumeration against the Priority Enumeration Data Type Definition.

Repeat and create the same Attributes Definition Enumeration for the interface Requirement Type. The model in project explorer should be as below:

Associate Attribute Definition Enumeration to Enumeration Data Type final

Requirement definition

The sections below will describe how to:

• Create Requirement Types and associate with data types.
• Create textual requirements.
• Allocate textual requirements to model elements.
• View textual requirements in the project explorer and diagrams
• Manage textual requirements.
• Export textual requirements.

Requirement Types definition

First create a new Requirements Capella Module. Right-click on the “Operational Analysis” > “Add Capella Element” > “Capella Module”, as below:

Requirements Capella Module can be associated to “Module Type”. Associating a set of requirements to a Module Type may be of value to ensure requirements are created and allocated at the right level of abstraction, that is, Operational Analysis, System Needs, Logical or Physical Architecture. At this point the below project Explorer should present the following:

Requirement capture

At this point textual requirements can be captured under the Requirement Capella Module. Requirements can (and should) be grouped, under a Folder (aka heading). For this example, requirements will be captured and grouped to define the expected behaviour to describe a Functional Chain: Perform Audio Announcement.

Requirements Folder

To create a new Folder, mouse right-click on the Stakeholder Requirements document Requirements Module, then “Add Capella Element” > “Folder”, as below:

Rename the Folder model element as: Perform Audio Announcement

Requirement capture

Create three textual requirements :

• The Cabin Crew shall be able to make audio announcement.
• The Aircraft shall be able to broadcast audio.
• The Passenger shall be able to listen to audio.

Create a requirement under the Folder, right-click on the Folder, then “Add Capella Element” > “Requirement”, as follows:

At this point, it can be associated the requirement types. For this example, only functional requirements are created, as below:

In addition, give a name and specify the requirement:

1. Name: Make Audio Announcement
2. Text: The Cabin Crew shall be able to make audio announcement

Repeat the process above for the additional requirements two requirements:

1. Name: Broadcast audio
2. Text: The Aircraft shall be able to broadcast audio

Finally,

1. Name: Listen to audio
2. The Passenger shall be able to listen to audio

The below requirements should be captured and seen in the project explorer, as below:

Requirement allocation

Requirements traceability links in Capella can be created between:

• Textual requirements and model elements.
• Between textual requirements at the same layer or between layers.

This section will describe how to allocate textual requirements to model elements.

Select the requirement “The Cabin shall be able to make audio announcement”, then in the requirement properties click on “Requirements Allocation” > “Add elements (+)”, as below:

In the selection dialog search for: make audio announcement Operational Activity, then select and click “Ok”, as below:

Next create:

1. Requirement relationship type: click on the requirement relationship and “satisfy”. Model elements satisfy requirements. Hence, traceability links are from a model element to a requirement.
2. Visualise requirements in a diagram: from the palette, select the “Requirements” filter, then the requirement to be shown.

When completed, the textual requirements should be traced and shown in the diagram, as below:

Repeat the process above for the other two requirements.

Requirement management

Requirements in Capella can be visualised, and attributes edited in a table format.

Requirement attributes editing

To edit requirements attributes in a table, select only the three requirements captured, then mouse right-click “Send to Mass Editing View” > “New Mass Editing View”, as below:

It is possible to select what columns to show or hide. For this example, a sub-set of columns will be shown. To select what columns to show/hide, mouse right-click in a column, then “Select columns”, as below:

Select the columns as shown in the figure below:

The Mass Editing view should look, as below:

It is possible to edit single attributes or a selection.

It will be edited a selection of attributes. To set a selection of attributes hold SHIFT and select the attributes as shown in the figure above, then select “Edit selection” and set to value to draft, as below:

Repeat the process above for the priority attribute and set value to High.

Requirements attributes viewing

Similarly, to editing requirements in a table it is possible to view requirements in a table. To view requirements in a table, select the three requirements in the project explorer, then “Send Mass to Mass Visualization View” > “New Mass Visualization View”.
As described in section above, select the columns as shown below:

In the Mass Visualization View, requirements can be sorted and grouped. This can be quite useful when reviewing requirement traceability. Several combinations and groupings can be done to satisfy a modeller needs.

For this example, there is the need to verify that only Operational Activities (i.e., functional behaviour) are traced to functional requirement. To achieve this grouping click and drag the column “Allocating Elements” and make it the first column, then click and drag “Requirement Type” to the area “Drag columns here to group by columns values” above the table. When completed a similar table should be shown as below:

Finally, requirement and attributes can be seen in the project explorer and semantic browser, but first it needs to be activated the “Show requirements in the semantic browser”, each time the Capella tool is started, as below:

Export textual requirements

Textual requirements can be exported to a .csv file. To export to a .csv file click “View Menu” > “Export to CSV”, as below:

When CSV file is created it is them possible to be imported to a requirements management tool, e.g., IBM Doors. However, there is prior work to be done in the file before importing. For example:

• Delete line 2 (empty).
• Rename and match exported attributes in columns with any already created in a Doors module.
• Delete all HTML references from the requirement text, e.g., <p>.

The post How to capture textual requirements in Capella complete step-by-step guide first appeared on Hélder Castro.