White paper: Root of Trust in the software-defined vehicle

Checklist · Software origin

10 questions about software origin that every ECU programme has to answer

A short checklist for ECU suppliers and for the teams that buy from them. The questions are written the way a vehicle manufacturer asks them. Use the list to see which answers already exist, and which ones take time to produce.

  1. 01

    Who designed and developed each software component in the unit, and where?

    A good answer names the organisation and the location for every component, not only for the unit as a whole.

  2. 02

    Who is the supplier of the software in the contract?

    The party that supplies the software matters as much as the party that wrote it.

  3. 03

    Who maintains and updates the software after start of production, and from where?

    Maintenance counts. Software written in one place and maintained in another has two origins.

Questions 4 to 10

Leave your work email and the rest of the list opens here on the page.

We use your address to reply to you, nothing else. Privacy notice.

Want to go through the list for your programme? Talk to us.

This page describes how Diadrom works. It is not legal advice. Whether a specific vehicle programme meets a specific regulation is decided by the vehicle manufacturer and its advisers.

Nothing works until everything works.