{'fraction_non_alphanumeric': 0.02977667493796526, 'fraction_numerical': 0.009925558312655087, 'mean_word_length': 5.781512605042017, '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': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Model-Based Development and Formal Methods in the Railway Industry

The transition from a code-based process to a model-based process isn't easy. This is particularly true for a company that operates in a safety-critical sector, where the products must be developed according to international standards, with certified tools and controlled processes. The authors summarize the experience of a railway signaling manufacturer that decided to adopt general-purpose, model-based tools&#x2014;namely, Simulink/Stateflow and SysML&#x2014;for product development. The company faced challenges primarily concerning the verification of the software and the integration of the tools within the existing process. Structured development solutions and formal/semiformal approaches were adopted to tackle the challenges.