The Autosar Interface Editor is used for working with Autosar Service Interfaces and Client Server Interfaces. For more information about the Autosar standard, visit the Autosar home page.


Prerequisites

  • The Autosar Meta model containing Service Interfaces and/or Client Server Interfaces
  • An installation of the SystemWeaver Explorer client (swExplorer) version R34 or later 
  • The SystemWeaver SWExtension.AutosarInterfaceEditor extension
  • Assignment of the SW Architect role in the SystemWeaver database


Example Meta Model

Service Interface

Client Server Interface


Configuring the View

  1. Go to File > Configure the explorer
  2. On the Item views tab, select Autosar Interface Editor.


  3. Click View example XML and copy the script as a starting point for your configuration. 
  4. Click Edit configuration and paste the script in the Edit XML window.
  5. Modify the configuration to meet the needs of the use case. (See the explanation of available elements below.)
  6. When you are ready to test and make it available to users, check the Active box. Users must log out and back in to see the new option.


Explanation of the Configuration Elements

The Autosar Interface Editor view requires minimal configuration to make the view available for users. Simply follow the instructions described in How to Configure Item View Menu Label Settings. It is, however, recommended that you define Configurable Add Part Grids for the Part Types: Arguments (ARGU), Data Type ARDG), Data Type (ARDH) and Arguments (ARAR) to display the allowed Data Types to use, if such a list is available. For instructions on how to do this, see Configuring Add Part Grid.


<AutosarInterfaceEditorConfigs> is the top tag which can include one or more <AutosarInterfaceEditorConfig>.


<AutosarInterfaceEditorConfig> is the top tag of each configuration and must have an id attribute. The id attribute in <AutosarInterfaceEditorConfig> identifies the specific configuration, and should be a unique string value when multiple configurations exist. 


Note: There is no need to define more than one <AutosarInterfaceEditorConfig> even though it is possible.

<ViewSettings> enables you to set a custom view label, hover-tip, icon, etc. See How to Configure Item View Menu Button Settings

XML

Example Configuration

XML
<AutosarInterfaceEditorConfigs>
<AutosarInterfaceEditorConfig id="1">
<ViewSettings>
<Caption>Autosar Interface Editor</Caption>
<RibbonGroup>Autosar</RibbonGroup>
<Description>Editor for Autosar Client Server and Service Interfaces</Description>
<Image guiImage="2"/>
</ViewSettings>
</AutosarInterfaceEditorEditorConfig>
</AutosarInterfaceEditorEditorConfigs>