How to deal with MISRA SLSF 036 rule

Hello, I'm using Simulink and Stateflow to produce a MISRA SLSF and MISRA C compliant model, to produce an AUTOSAR SwC with Embedded Coder.

I'm using bus signals into models in different points as they are really useful for my intended implementation.

One of the required rules by MISRA SLSF is the 036. The statement "A" of this rule suggest not to use Bus inputs with Stateflow, since buses are used in Simulink to package signals together often with different types. Each data in Stateflow must have a unique type definition.

My questions are: - Is this rule still valid with R2018a? - Is there a correlated check into Model Advisor for this rule? - Is there a way to use buses and respect this rule?

Thanks in advance

[Jean Matthieu]

Most of the rules are supid. Are they still valid on release post 2019?

Few other examples:

MISRA AC SLSF 005 --> list of allowable blocks

MISRA AC SLSF 025 --> size of blocks

MISRA AC SLSF 034 --> rules on stateflow that feel Stateflow are useless

MISRA AC SLSF 035 --> it is forbidden to use truth table (?)

MISRA AC SLSF 039 --> Here are other constraining rules over stateflow --> Stateflow is clearly useless with MISRA AC

MISRA AC SLSF 040 --> Other constraints over Stateflow...

==> It seems like those who wrote this document disliked Stateflow