25 - 28 March, 2019
Holiday Inn Munich City Center, Munich, Germany
Holiday Inn Munich City Center, Munich, Germany
Second Conference Day
8:30 am - 9:00 am Registration and welcome coffee
9:00 am - 9:10 am Opening remarks by the conference chairman
9:10 am - 9:50 am Keynote opening | Clarity of scope between ISO & SOTIF
9:50 am - 10:30 am Panel Discussion | How to make ISO 26262 and SOTIF fit together
10:30 am - 11:00 am Morning coffee break and networking
10:30 am - 11:00 am Morning coffee break
11:00 am - 11:30 am State of the art in safely using AI and ML methods in automotive architectures
11:30 am - 12:00 pm Slow versus fast: Always up-to-date safety-critical functions in centralized E/E architectures
12:00 pm - 12:30 pm Modular contract-based safety argumentation for reused applications and higher speed on the feature level safety case
12:30 pm - 1:00 pm Impact of the increasing automation levels on risk assessment
1:00 pm - 2:30 pm Networking luncheon
2:30 pm - 3:00 pm How to combine ASIL monitoring with off the shelf QM elements to reduce ASIL development costs
3:00 pm - 3:30 pm How does product safety relate to ISO 26262
3:30 pm - 4:00 pm ISO 26262 compliant embedded software development through the model based safety software development life cycle
4:20 pm - 5:50 pm Mix & Discuss | Choose for two out of 16 deep dive topics, and elaborate each with experts from all conferences. For each topic you chose, you have 30 minutes to discuss it in your group. The results will be presented at the end.
A1 | How can you really take the safety element
out of context?
B1 | How to enhance cooperation through
best practices within departments
C1 | Data management systems: Critical aspects
and key system ingredients in automotive
D1 | Assessment and release criteria for automated
functions
A2 | Enforcing functional safety of the powerfeed
for future vehicles
B2 | Hand in hand - addressing safety concerns:
Implementation of best practices in security
C2 | System-based test verification: Strategies,
processes and methodologies
D2 | Rethinking software design from scratch
instead of cleaning up afterwards
A3 | Defining and applying tolerance times in
safety concepts
B3 | Security for connectivity: Strategies for security
– look at every device like an individual
C3 | Testing form a human (factors) perspective:
Field Findings on passenger acceptance of
autonomous vehicles
D3 | What are the requirements towards vehicle
simulation to enhance SOTIF safety analysis?
A4 | Handling failure mode distributions
for semiconductors
B4 | Security for over the air updates (SOTA)
- checking for potential vulnerabilities
C4 | A comparison of model-based validation:
Road vs. simulation-based testing
D4 | SOTIF and Functional Safety In Context
of Automated Driving