{'fraction_non_alphanumeric': 0.020719738276990186, 'fraction_numerical': 0.0, 'mean_word_length': 5.12, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
On the Necessity of Explicit Artifact Links in Safety Assurance Cases for Machine Learning

The perception in autonomous systems is essential for safe behavior. Machine learning (ML)-based functions play an increasingly important role in this context. The development and safety assurance of such functions is different from the development of non-ML-based functions. Traceability of the various artifacts generated for safety argumentation is challenging, as there is i.e. no longer a direct mapping from requirements to code and data cannot be directly mapped to a semantic domain model. In this work, we show that and how the links between artifacts, which are created in different stages of the development, must be established explicitly. These links enable us to build confidence in our safety argumentation. We concretize these explicit links in two examples, namely pedestrian detection and vehicle detection.