Sehr interessanter Artikel über die Notwendigkeit einer End-to-End Softwareplattform für Automobilhersteller.
Imagine a world in which software throughout a vehicle was truly integrated end to end. A primary operating system, robust and flexible enough to cover major systems throughout the vehicle, and software modules, developed on a common code base, could anchor this integration. Such a construct would provide a solution to many of the pain points present in today’s fragmented ecosystem. First, this construct would allow automotive players to address the performance issues stemming from disparate operating systems and disjointed sets of code. Cross-domain interfaces could become far simpler, since different systems could directly “talk” to each other without translation dragging down efficiency and introducing delays. Security could greatly expand, enabling one overarching solution to monitor the full code base—not just at a handful of interfaces. And development productivity could considerably improve, with OEMs adding new cross-domain features over time, without extensive software rewrites, by leveraging a common code base throughout the vehicle. End-to-end software solutions could also lay the groundwork for a substantially enhanced human–machine interface. Fundamental user-experience constructs could easily be shared across vehicle domains, enabling output methods, such as the center screen, instrument cluster, and heads-up display, to have a consistent behavior, look, and feel. Automotive players could enhance safety, with real-time notifications triggering immediate visual, auditory, and tactile feedback, throughout the cockpit, that alerts drivers to act. As interior-design preferences evolve and user interfaces are repurposed for different vehicle models and tiers, the sensory experience could change with minimal development effort. Finally, end-to-end software platforms could make dynamic resource sharing a reality—a shift that would reduce overall hardware costs while enabling the addition of new capabilities over time. Supporting this trend, OEMs appear to be moving toward an approach in which in-vehicle communications align with an Ethernet standard. This move will allow OEMs to create vehicles with a real-time, high-bandwidth information highway that links major systems together and opens the door for dynamic sharing of the full resource pool across a car. A unified operating system could then allow processing horsepower to be allocated on the fly, dynamically enhancing performance for critical systems when needed. For instance, more resources could be allocated to ADAS during “edge cases” for which complexity is high and response speed is paramount. Overall hardware costs could be optimized, and additional processing capacity could simply be “plugged in” to the architecture to support future applications.