Why an Event-Chain-Centered Architecture Design Is the Right Response to the Challenges of Developing Software-Defined Vehicles

As the automotive industry moves to the software-defined vehicle and selling feature upgrades updated over the air, it is clear that the development approach used for static architectures is no longer fit for purpose.

Adding timing requirements to flowcharts enables engineers to quantify the impact of hardware changes, feature changes, and feature updates on today’s domain controllers and automotive high-performance computing (HPC) platforms.

Discover how this approach significantly reduces the issues typically arising during integration that are found late in the development process, securing the dynamism the automotive industry seeks from the software-defined vehicle.

• Why an event-chain-centered architecture design is the correct response to the challenges of developing software-defined vehicles
• Function nets cannot remain the supreme structure by which E/E architectures are organized
• How event-chain-centered architecture design solves the problem
• Why sequence diagrams quickly reach their limits
• Flowcharts are an effective tool for effective event-chain-centric architecture design
• Methods for simplifying the design of complex functions
• Modularity
• Test and Verification
• Summary