Features expected but not implemented yet
Below is a list of needs that are identified but not yet implemented.
- Not possible to save and load transformation.
- Not possible to set the name and the location of the mlcore file before its creation.
- No existing Capella model validation rule to prevent transformation errors.
Unsupported or limited support of Capella modeling patterns
Functional Exchanges with the same name in a given ARCADIA perspective
This situation leads to a name conflict in the data dictionary storing the bus definitions for Functional Exchanges. If this occurs, the bus definitions will be erased one after the others and only the last one created will remain.
It is highly recommended to avoid such situation by uniquely naming the Functional Exchanges.
Functions cannot be transformed as Subsystem Reference
The connector does not implement this option.
Two or more ports end-up to have the same name
The transformation adds a suffix "_N" to the name, where "N" is an integer number that is incremented from 1 to 9.
The first port created is not suffixed.
The next ones are suffixed.
Multiple Functional Exchanges goes out of an "Out Flow Port"
- Data typing conflict: if the Functional Exchanges carry exactly the same Exchange Items, then there is no data type conflict and the bridge can route the Functional Exchanges from the same source port to different destination port. If the Functional Exchanges carry different Exchange Items then there will be a data type mismatch between what the consuming function needs and the Functional Exchange bus definition.
- Naming conflict: If the Functional Exchanges are named different, then one of this name will be used to name the port if the port naming option defines the Functional Exchange name to be used as port name.
Multiple Functional Exchanges goes in of an "In Flow Port"
As many Inports as incoming Functional Exchanges are created. Hence, there is a mismatch regarding the number of function inports between Capella and Simulink®.