{"id":18360,"date":"2021-07-05T13:03:15","date_gmt":"2021-07-05T13:03:15","guid":{"rendered":"https:\/\/arobs.com\/?p=18360"},"modified":"2021-09-27T10:35:01","modified_gmt":"2021-09-27T10:35:01","slug":"system-architecture-3-insights-from-autosarxahk-events","status":"publish","type":"post","link":"https:\/\/arobs.com\/en\/blog\/system-architecture-3-insights-from-autosarxahk-events\/","title":{"rendered":"System Architecture – 3 insights from AUTOSARxAHK events"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
AROBS Transilvania Software development<\/span><\/a><\/span><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t


What future E\/E System Architectures need? \u2013 3 insights from AUTOSARxAHK events<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t


<\/p>\n

System architecture has seen a major shift given that software development<\/a> rapidly changed the outlook of the automotive industry. After just a single decade, the conventional, distributed E\/E system architecture<\/em>, based on cross-domain functions, gradually morphed into the need for domain-centralized E\/E architecture<\/em> and, further, into the Zone-based E\/E architecture<\/em>.<\/p>\n

The major weakness of the conventional architecture is the lack of scalability since applications are created as monolithic executables. In contrast, the rapid pace of automotive development<\/a> requires reusable software<\/a>.<\/p>\n

The relevant players of the automotive industry, recognizing the need for scalability and standardization, started partnerships that develop the methodology and structure so much needed for progress.<\/p>\n

AUTOSAR<\/a> is one of the most significant partnerships that bring together stakeholders of the entire supply chain, offering a standardized software framework for the future of mobility.<\/p>\n

AUTOSAR and AHK (German-Romanian Chamber of Industry and Commerce) events<\/em><\/strong><\/h2>\n

Part of creating a common platform is incentivizing collaboration through events. One of the most recent events was organized by AUTOSAR and AHK; the Automotive Software Development for Future E\/E System Architectures<\/em> virtual event had the Romanian market in focus.<\/p>\n

What do future E\/E system architectures need from software companies?<\/em><\/strong><\/h2>\n

In the following section, we gathered three key insights from the event.<\/em><\/p>\n

1. Scaling knowledge – companies need an AUTOSAR competence center<\/em><\/strong><\/h3>\n

AROBS’ Head of Automotive, Silvan Morariu, who presented alongside representatives of top automotive developers \u2013 discussed the necessity for companies to learn from their own AUTOSAR best practices and bring the know-how to a greater level.<\/p>\n

“At AROBS we are actively working on creating an <\/span>AUTOSAR competence center to <\/span>structure and scale our know-how to all our over 400 automotive engineers to provide the <\/span>highest quality deliverables to clients.”<\/span><\/em><\/blockquote>\n

\"AROBS<\/p>\n

Scaling knowledge – the steps<\/em><\/strong><\/p>\n

The process of transforming unstructured company knowledge into a competence center is complex and gradual. First, the automotive engineers attend basic AUTOSAR (training framework) and<\/em> hands-on training<\/em> using dedicated tools; later, they get the chance to work on actual AUTOSAR projects<\/em> under the guidance of experienced engineers. Following the successful completion of these phases, they are ready to do specialized work on AUTOSAR<\/em> based projects without external guidance.<\/p>\n

2. Better understanding – zone architecture is like the human architecture<\/em><\/strong><\/h3>\n

As the industry is getting closer to the wide adoption of the 3rd level of autonomous driving, the architecture of the vehicle is starting to resemble the humans with real-time reactions to their environment.<\/p>\n

Using an insightful analogy, one of the speakers presented zone architecture differently. Zone architecture could be understood in similar ways as we are understanding the functions of humans, where:<\/p>\n