Matlab/ Simulink support for AUTOSAR naming convention

I am currently looking into ways to check/enforce the AUTOSAR naming convention for existing Simulink models. I found that in Simulink, we can configure a model as AUTOSAR Component using the "Configure AUTOSAR Interface Dialog Box". In this configuration process, the last step is to click a validate button which performs several validations including checking that the shortName attribute of elements have not exceeded their maximum allowed length (this is one of the rules in AUTOSAR's naming conventions). The command line-equivalent of this validate button is 'autosar.api.validateModel(mdlName)' ...

My question is does this button/command check for any other or even all of AUTOSAR's naming conventions (besides the maximum length of shortName)? ie., to what extent does this button/command validate AUTOSAR's naming convention in existing Simulink models?

Thanks a lot in advance

[Sam McDonald]

Which other AUTOSAR naming conventions are you referring to or looking to validate? Could you describe them?

[Gehan Selim]

Hi Sam, Basically AUTOSAR has a document named AUTOSAR_TR_SWCModelingGuide which has their naming convention for several classes. The convention gives guidelines on how to name the shortName and longName attributes of these classes. Additionally, they describe how to use the abbrName (or abbreviation) of Keywords class to build shortNames of other elements. Actually they define a list of `semantic rules ' on how to combine the abbrName of several keywords to compose a valid shortName for other elements.

Answer 1

[Sam McDonald]

As mentioned in the documentation page, the "autosar.api.validateModel" function primarily validates AUTOSAR properties and mapping of a Simulink model. Checking the shortName naming convention may also be done as a prerequisite to perform this validation. However, this could be made more clear in the documentation.

[Gehan Selim]

So in other words, the function doesn't check for everything in the naming convention I mentioned above? checking for the shortName comes as a plus, correct ?

[Sam McDonald]

It would seem so. You could create a support request to MathWorks Technical Support if knowing about this has increasing impact on your workflow.