Unrealistic Validation Warnings at PA Level

Hi all.

I have been running around in circles with AI to try and resolve this matter with no success, so now I am turning to the forum as a last resort.

When I vaildate my model’s PA level, I get a series of TC_DF_10 warnings. In this warning, the validator is looking for realized function ports at the EPBS level (i.e. level below) to trace to the PA ports in the same way it does so between other layers. However, this makes absolutely no sense for the PA ↔ EPBS levels, since functional ports at the EPBS level is not even possible, let alone traceable. In fact, there are not even any functions at EPBS, let alone function ports.

I also realized that the validator also issues warnings for transition of Capabilities and Scenarios to EPBS when validating at PA level, which also does not make sense, since of these elements are neither useful nor necessary at EPBS.

Why would the validator continue to evaluate this rule between these levels if it makes no sense?

How can I prevent the validator from issuing these warnings without disabling the rule entirely? Disabling this rule disables it for all other layers as well, which is not desirable.

I did pick up on a possible halucination from AI that Capella has validation rule profiles that can be saved which would then allow a modeller to select specific rule profiles when validating, which could be helpful, but I could not locate this feature, except for the import/export function under the Preferences section, which is not ideal but could work.

Any assitance would be helpful.

Regards.
Estian.

This would have to be confirmed by an Arcadia expert by I concur with you that TC_DF_10 should not give error for the scenario you describe. Probably something to fix in Capella. Could you raise a bug.

As for sharing validation ruleset/profiles, see in the documentation the entry at Capella Guide > User Manual > Workbench Basics > Capella Configurability and Validation Profiles

Stephane

@StephaneLacrampe

Thank you for the feedback.

Can you please remind me again where Capella bugs are reported?

Regards.
E.

Yes, here: Issues · eclipse-capella/capella · GitHub