{'fraction_non_alphanumeric': 0.016408386508659983, 'fraction_numerical': 0.0, 'mean_word_length': 5.310344827586207, '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}}
The experience of auditing software for safety critical railway signalling equipment

The experience of carrying out Audit of two versions of Software for a Railway Signalling equipment, called the "Universal Fail Safe Block Interface" (UFSBI), being developed by two vendors is described. For the users and the developers, this had been the first exposure to formal development of safety critical software. The auditors were academics with IV&V experience for only aerospace software and no prior experience with railway signalling system. Prototypes of UFSBI had been operating before the auditors were formally brought in, but a full life cycle audit was undertaken due to safety criticality of the system as per the European CENELEC standard, desired to be adopted by the users. In the absence of local precedence, new paradigms of interaction had to be evolved and the role of the auditors, expanded to also include mentoring and facilitation. Initial scepticism and conflicting expectations from software audit gradually became a participatory learning activity for all the involved parties.