Integrating Ecosystems:
How to Support the Development of Software-Defined Vehicles
In the race to build and bring next-generation vehicles to market, efficiency and flexibility matters. Using the right architecture is critical for software-defined vehicles, which are rapidly gaining traction for their ability to deliver increased software reuse, faster integration and time to market. A great example of this trend is Next-Generation Electrical/Electronic (Next Gen E/E) Zonal Architecture, a design approach that calls for broad integration across the many different subsystems in a common architecture.
This focus on integration paves the way for collaborative ecosystems such as DDSTM, AUTOSAR or ROS 2 to be used and optimized for building software-defined vehicles. Being able to leverage the familiar unique capabilities of DDS should not be limited to native development, but should be available across the complete ecosystem. AUTOSAR and ROS 2 toolkits can help provide a rapid start and solid foundation within fully integrated systems, while leveraging the many benefits of data-centric architectures. Being free to develop vehicle architectures using software and hardware from multiple vendors provides a clear advantage, making it easier to maintain compliance with evolving standards and platforms and get access to continuous feature and performance improvements.
When it comes to Next-Gen E/E development, vehicle data connectivity is equally important. Integrated systems must provide flexibility, scalability, compatibility and portability to different hardware components. In addition, rigorous — and continuously evolving — safety and cybersecurity requirements add yet another level of complexity to be addressed.
What is the best approach to modeling and configuration workflows? How do you achieve rapid, scalable communication within embedded, real-time, and safe systems?
Success-Plan Services
