Since the IEEE Spectrum article "This Car Runs on Code" back in February 2009, my interest in the requirements for software and system-level development in automotive applications has grown quite a bit. And after recently having reviewed in previous blog posts requirements for wireless and industrial applications, automotive seems to be a great next topic.
According to market data provided by dataBeans in July this year, the automotive segment is actually expected to be in 2011 the smallest segment in the $2.1 trillion electronics market. It grows at a 6% CAGR from 2011 to 2016 and is served by a $25 billion semiconductor market, growing at a 9% CAGR.
The 11th EDA Forum in Berlin earlier this year was a good opportunity to better understand automotive. Dr. Erich Biermann, senior vice president of engineering for Bosch Automotive Electronics, gave an interesting talk about "Challenges and Chances for Power and Microelectronics in Automotive." According to Bosch, the worldwide production of 70.9 Million cars in 2010 is expected to grow to 100.6 Million cars in 2015. That means that the average semiconductor content per car is close to $350.
Comparing a couple of studies, Dr. Biermann concluded that volume predictions for alternative drive trains are uncertain at present. As core three drivers for this market he identified the need for cars to be safe, clean and economical. This mirrors the "three zeros" Bosch supplier Freescale outlined earlier this year at the Freescale Technology Forum as "zero defects, zero emission and zero fatalities". The rest of Dr. Biermann's talk focused more on the power electronics aspects in cars, as well as the energy flow in a car.
To understand the impact of software and system-level design, I went back to the proceedings of the EDA Forum and looked at a talk given by Dr. Christian Sebeke, also from Bosch, called "EDA for ‘More than Moore.'" In that talk, Sebeke identified the demand for high performance safety critical system-level design in automobiles. Not unlike other application domains, parts of the system integration, including software, are taken to the next lower level (you can see my previous comments here and here). I really liked the graph he showed at the time outlining the challenges for EDA (see below, Source: Bosch).
As a result, Sebeke foresaw big challenges for mixed mode design verification, validation, simulation and modeling:
So just like in the other application domains I have reviewed so far, it is safe to assume that software and system-level development are critical components for automotive developments as well. Some of the technologies like virtual prototypes have the potential to become key enablers.
Whether and when we will find USB and Ethernet ports at our gas stations to allow us to get the latest software updates for our cars remains to be seen ...