Transformation of Functional Chains

Get initialized Simulink® models implementing Capella Functional Chains.

Workflow

The generic workflow is detailed in Getting started. Below are the specific options to choose in this workflow:

1. Select in the Capella Project Explorer the Functional Chains to export.
2. Open the "Capella Export to Simulink®" tool.
3. Select the transformation type "Functional chains and all involved components".
4. Set the transformation options "Port naming strategy".
5. Import the Function in the project using the generated .mlcore file.

How are the Capella Functional Chains elements transformed?

• Functional Chain as a Simulink® model stored in the "model\<ArcadiaPerspective>" folder. The name of the Simulink® model is "<ArcadiaPerspective>_<FunctionalChainName>.slx". This model references models of all involved functions.
• Involved Functions as a model (default). See Transformation of Functions for details about how Functions are transformed.
• Involved Functional Exchanges as lines connecting involved Functions.
• A Data Dictionary is created for each Functional Chain model linked to it. The name of the data dictionary is "<ArcadiaPerspective>_<FunctionalChainName>.sldd". It is used to store potential Parameters dedicated to the transformed Functional Chain; and to reference other Data Dictionaries storing the definition of the involved Functional Exchanges.

Function models created by the bridge alway capture the full definition of the Function even if a function is created in the context of a Function Chain. Hence, when referenced by a Functional Chain model it is likely all the Function ports are not used. Then an extra work is required to robustify the generated model.

Assumptions & Known Limitations

Nothing to mention here.