{'fraction_non_alphanumeric': 0.018967334035827187, 'fraction_numerical': 0.0, 'mean_word_length': 5.551724137931035, '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}}
Adoption of model-based development for machine controller software

The complexity of mechatronic systems in general and their control software in particular keeps increasing. For years already, model-based development promises to ease a lot of the challenges in the development of mechatronic machine controllers. Still, its adoption by machine builder companies often remains limited to the algorithmic part of the controller, typically using tools such as Mathworks Simulink. This paper explains how model-based development can support other aspects of a mechatronic controller (such as its componentization) and how machine builders can adopt the required techniques. We present some trends observed in industrial use cases, the trade-offs the software architects are facing and the issues they have experienced. Although no silver bullet exists, some valuable guidelines are provided for developing a model-based software development strategy.