{'fraction_non_alphanumeric': 0.015120967741935484, 'fraction_numerical': 0.0, 'mean_word_length': 5.755102040816326, '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}}
Towards a process and tool-chain for service-oriented automotive software engineering

The complexity of automotive software systems continues to increase at a dramatic pace. Traditionally, the interactions between the various software components of a vehicle are addressed only at the later stages in the overall development process. We advocate a fresh approach, where interaction patterns become the defining elements of automotive software services. This shifts the development focus from individual components to their interaction in the early stages of the development process; potentially reducing development and integration costs for both manufacturers and suppliers. We present a formal service notion based on interaction patterns and introduce a systematic, service-oriented development process, substantiated by means of a corresponding tool chain. We illustrate our definitions and results by modeling elements of a Central Locking System, an example from the automotive domain.