The Architectural System Signals extension view is part of SystemWeaver's System Design solution, and is meant to replace the built-in System Signals view in SystemWeaver. It supports the creation of one architectural system signal per provided interface and ECU, whereas the built-in System Signals view only supports one architectural system signal per provided interface. The extension view is based on a workflow where the inter ECU communication is described as superset definition. The plugin lists all of the signals which have been defined to be external (going from one ECU to another in the system).


Other views that support the System Design model are: 


Prerequisites

  • Familiar with the SystemWeaver meta model building blocks (e.g., Items, Parts and Attributes)
  • Familiar with the SystemWeaver Explorer Interface and common operations
  • An installation of the SystemWeaver Explorer client (swExplorer) version R35 or later
  • Knowledge of XML
  • Assignment of the SW Architect role in the server
  • The complete Autosar Meta model for describing allocated Autosar Systems
  • The SWExtension.ArchitecturalSystemSignals.dll extension file is located in the Client's swExplorerExtensions directory


Example Meta Model

Below is an example meta model and connection example. 




Configuring the View

  1. Go to File > Configure the explorer. 
  2. On the Item views tab, select Architectural System Signals.

  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.


Example Configuration

<ArchitecturalSystemSignalConfigs>
    <ArchitecturalSystemSignalConfig id="1">
        <ViewSettings>
            <Caption>Architectural System Signals</Caption>
            <RibbonGroup>System Design</RibbonGroup>
            <Description>System signals</Description>
            <Image guiImage="5"/>
        </ViewSettings>
    </ArchitecturalSystemSignalConfig>         
</ArchitecturalSystemSignalConfigs>

Explanation of the Configuration Elements

The Architectural System Signal view requires minimal configuration to make the view available for users. 


<ArchitecturalSystemSignalConfigs> is the top tag which can include one or more <ArchitecturalSystemSignalConfig>. 


<ArchitecturalSystemSignalConfig> is the top tag of each configuration and must have an id attribute. The id attribute in 

<ArchitecturalSystemSignalConfig> identifies the specific configuration, and should be a unique string value when multiple configurations exist. 


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