Verifying Automotive Designs

With the increasing use of electronics in the automotive domain, there is an associated need to ensure the safety of those designs, and this has implications for Design Verification. This ranges from the verification of safety mechanisms which attempt to minimize the risk of accidents and injuries caused by hardware-related issues in vehicles, to demonstrating compliance to standards such as ISO26262.
Additionally, other concerns such as operating conditions, HW/SW co-development, mixed signal, low power and cyber security requirements (defined in ISO 21434) are also very important and specific for automotive. There are also diverse development architectural considerations too, from a server-like design supporting virtualization to a classic decentralized approach. With IVN, ADAS a lot of high-speed requirements, acceleration is yet another factor.
Finally, in spite of this increasing complexity, the market is demanding shorter development cycles from 5 years to 3 years (and even shorter!).
Challenging time and this DVClub will be an ideal opportunity to discuss potential solutions.