As autonomous vehicles evolve from research to prototypes to real cars on the road, functional safety and ISO 26262 have become central topics in the automotive industry. Although the first edition of the standard was released seven years ago, there still are differences in opinions and actual practices on what it means to be ISO 26262 compliant. The level of diligence to which safety considerations are institutionalized, and designed into the product, could also differ for two products with the same ASIL claim. Join BlackBerry QNX, a leader in functional safety for embedded software, to explore this topic and learn:
- The differences between compliant, certified and certifiable
- How to determine if a product lives up to its ISO 26262 claim
- How to mitigate risk of non-compliance and reduce development and certification costs
Yi is responsible for BlackBerry QNX’s portfolio of safety and security products designed for the industrial, automotive, energy, and railway markets, and which are certified to standards such as IEC 61508, ISO 26262, and Common Criteria ISO/IEC 15408. Yi holds a Bachelor's in Computer Science from Carleton University, a Master's in Business Administration from Queen’s University, and is a Certified Management Accountant.
Chris specializes in the design and implementation of embedded, real-time systems for use in safety-critical applications (particularly medical, railway, industrial and automotive). He works on both the safety certification of BlackBerry QNX products against standards such as IEC61508, IEC62304 and ISO26262, and also on providing consultancy to BlackBerry QNX's customers building safety-critical devices. His book "Embedded Software Development for Safety-Critical Systems" was published in 2015.