Functional Safety with RTA-CAR & AUTOSAR Classic

Keyvisual - Functional Safety with RTA-CAR: Making the case for your AUTOSAR Classic application

Proving the safety of an application built on RTA-CAR generated AUTOSAR software requires a system-level approach. Safety is not an inherent property of individual components but emerges from their integration. This session explores key concepts such as safety cases for AUTOSAR based systems, ISO 26262 applied to model-based code generation, and Safety Elements out of Context (SEooC).

Practical aspects include idiomatic safety features in AUTOSAR, the role of RTA-CAR generated code in safety, and integrator obligations—highlighting that safe components alone do not guarantee a safe system. The session concludes with actionable best practices for crafting a compelling and effective safety argument—starting from day one of the development lifecycle.

Watch webcast

Key topics and takeaways

Safety is a system property, not a component attribute.
Concepts like SEooC, assumed context, and partial safety claims are essential tools in structuring a credible safety case.
AUTOSAR offers safety mechanisms, but their effectiveness depends on correct and intentional integration.
Safety cannot be retrofitted—understanding the required safety claim early is essential.

Webinar highlights

webinar teaser: Functional safety for your AUTOSAR Classic application

YouTube

Loading the video requires your consent. If you agree by clicking on the Play icon, the video will load and data will be transmitted to Google as well as information will be accessed and stored by Google on your device. Google may be able to link these data or information with existing data.

Speaker

Subash Scindia, Business Development Manager, ETAS
Alex Burn, Product Manager, ETAS

Functional Safety with RTA-CAR: Making the case for your AUTOSAR Classic application

Key topics and takeaways

Webinar highlights

Speaker

Contact us