{'fraction_non_alphanumeric': 0.013114754098360656, 'fraction_numerical': 0.029508196721311476, 'mean_word_length': 4.990196078431373, '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}}
Using a Goal-Based Approach to Improve the IEC 61508-3 Software Safety Standard

In this paper we argue that the methods and techniques specified in the annexes in IEC 61508-3 are just sound software engineering principles. Problems when developing safety critical software are not caused by lack of adherence to the standard per se but by ignorance of sound engineering principles related to the specified techniques. Further we argue that IEC 61508-3 should be more flexible regarding the safety lifecycle requirements by mentioning the use of modern software development practices together with the V-model.