Automotive embedded software (personal views)

A colleague of mine asked me if I am into SDV (Software Defined Vehicle). I started to wonder if I am in SDV and what really SDV is all about.

Well to define SDV, it depends whom you ask this question to. A consumer may say if I am able to connect to my vehicle via an mobile app, then she/he believes their vehicle is SDV. If the same question is asked to a Tier-1, the company will likely explain on zonal architecture or High Performance architecture. An OEM is likely to give more convoluted answer which is even harder to understand.

To futher this confusion there are many SDV consortiums some with commercial interests , with open source interests and a few with both. Here is a list of SDVs which I am aware of:

1. Eclipse SDV
2. SOAFEE
3. AOSP
4. .
5. .

I am sure there are many more which I am not even aware. So coming back to the question, am I into SDV?

If an individual is working on a software which is going to be deployed into the vehcile or connects to the vehicle then she/he is in SDV. Needless to say, indiviuals involved in all phases of the software development life cycle from requirements to validation are into SDV.