Automotive User Interfaces and Interactive Vehicular Applications

The HMISL language
for modeling HMI product lines
Simon Gerlach
Volkswagen AG
HMI/Cluster, Switches
PO Box 1148
D-38436 Wolfsburg, Germany
simon.gerlach@volkswagen.de
• Domain specific language for model-driven development of Automotive HMI Software
• Designed for being combined with different GUI modeling tools available on the market
• Allows to model behavior logic modules reusable for creating different product variants
• Code of product variant is generated based on module selection and parameterization
interface gui myGui {
animation fadeSeekToManulMode;
...
scene seekScreen {
interaction manualTuning;
property string stationName;
...
}
scene manualTuningScreen {
property integer tunedFrequency;
...
}
popup temperatureWarning priority 10 {
...
}
}
module radio uses myGui {
public event manualTuning;
public variant integer defaultFrequency;
...
statemachine main start seekMode {
state seekMode {
on enter show seekScreen;
on manualTuning {
if (defaultFrequency != -1)
set tunedFrequency to defaultFrequency;
goto manualMode;
}
...
}
state manualMode {
on enter show manualTuningScreen;
...
}
}
}
Depending on Supplier/OEM
• GUI design is created externally
• GUI interface defines “remote-controlled” elements in
GUI and interaction events
• GUI interface independent of actual GUI layout
• Description of HMI behavior
• Reactive programming paradigm: combines scripting
language and high-level constructs (e.g. events, state
machines, data binding…)
• Elements of GUI interface are accessible
• Placeholders for variant specific values
• Maps supplier/OEM specific interface technology to
generic concepts like events and variables
• Specification of base function and call sequences