Published: 12 August 2022
Summary
Continuous integration/continuous deployment of code has become key to enabling effective life cycle management of software-defined cars. This research discusses Step 3 of how CIOs achieve this — by creating a digital twin 2.0 to simulate code behavior and validate the safety of updates.
Included in Full Research
Overview
Key Findings
Vehicle software, firmware and parameter updates will move from large-scale, infrequent batched changes to more regular, ongoing updates to perform preventative maintenance and to deliver ongoing improvements to systems’ functionality.
Simulating the behavior of planned software updates to check for any unexpected changes in vehicle functionality or the emergence of faults will become a core element of continuous integration/continuous delivery (CI/CD) — speeding up the deployment of over the air (OTA) updates.
Recommendations
CIOs working to optimize and modernize their IT systems to manage the software and firmware deployed on vehicles through their life cycle must:
Clients can log in to view the entire
document.