Can’t attend live? Register anyway, and we’ll send you a link to the slides and a video of the webinar when it’s finished.

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 assumed safety contexts, partial safety claims, and Safety Elements out of Context (SEooC), emphasizing the importance of correct usage.

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 best practices for structuring a safety argument effectively from the start.

Key topics and takeaways:

• Safety is a system property, not a component attribute
• SEooC, assumed contexts, and partial safety claims shape system safety arguments
• AUTOSAR provides safety features, but correct integration is crucial
• Safety cannot be retrofitted – understanding the required safety claim early is essential