{'fraction_non_alphanumeric': 0.014517506404782237, 'fraction_numerical': 0.0, 'mean_word_length': 5.735632183908046, '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}}
A Component Model for the AUTOSAR Virtual Function Bus

To reduce cost and time to market of automotive software systems and simultaneously increase the products' quality, the component paradigm has achieved broad acceptance within the automotive industry over the last few years. This fact is reflected by upcoming domain specific software standards like AUTOSAR. In AUTOSAR application concerns are covered by software components, while infrastructural ones are handled within layered component middleware. The so obtained separation of concerns leads to an increase in application quality, reusability and maintainability, and hence to a reduction of cost and time to market. This paper contributes with the consequent application of the component paradigm to AUTOSAR's layered middleware, thereby gaining all benefits of CBSE not only for the application level, but for the whole automotive software system. The introduced component model for middleware components can flexibly be used to build resource-aware, AUTOSAR compliant, component middleware for distributed automotive software systems and can seamlessly be integrated within the AUTOSAR system architecture.