Integrating Testing and Operation-related Quantitative Evidences in Assurance Cases to Argue Safety of Data-Driven AI/ML Components
Michael Kl\"as, Lisa J\"ockel, Rasmus Adler, Jan Reich

TL;DR
This paper proposes a comprehensive assurance case framework that integrates testing, runtime data, and data quality considerations to quantitatively argue the safety of AI/ML components in safety-critical systems.
Contribution
It introduces a holistic argumentation structure combining multiple quantitative evidence sources, enhancing the robustness of safety claims for AI components.
Findings
Proposes new argumentation structures for AI safety assurance
Mathematically analyzes the integration of test and runtime data
Discusses practical implications for safety case development
Abstract
In the future, AI will increasingly find its way into systems that can potentially cause physical harm to humans. For such safety-critical systems, it must be demonstrated that their residual risk does not exceed what is acceptable. This includes, in particular, the AI components that are part of such systems' safety-related functions. Assurance cases are an intensively discussed option today for specifying a sound and comprehensive safety argument to demonstrate a system's safety. In previous work, it has been suggested to argue safety for AI components by structuring assurance cases based on two complementary risk acceptance criteria. One of these criteria is used to derive quantitative targets regarding the AI. The argumentation structures commonly proposed to show the achievement of such quantitative targets, however, focus on failure rates from statistical testing. Further…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsSafety Systems Engineering in Autonomy · Risk and Safety Analysis · Software Reliability and Analysis Research
