Alex Agizim, GlobalLogic, Inc.
Software is becoming increasingly more important for automobiles, from diagnostic programs that scan for vehicle malfunctions to in-vehicle infotainment (IVI) units that provide navigation and entertainment services. And now that Apple and Google are both entering the automotive space, the idea of a truly “connected car” is quickly gaining momentum. However, a major roadblock to extending Internet of Things (IoT) to vehicles is the industry’s strict safety regulations, which (for good reason) place heavy restrictions on any software being introduced into a driving environment. In this article, we take a deeper look at the automotive industry’s compliance standards and explore how to balance innovation with safety in a connected car by leveraging open source software.
Making a call is probably the least important thing your phone does these days. We use our smartphones as cameras, game consoles, cash registers, social media portals, and more. Banking apps enable us to deposit checks simply by taking a photo of them, and medical apps enable us (and our doctors) to remotely monitor and analyze our health. We can even use our phones to operate our home appliances, like TVs and thermostats. However, the one thing our phones cannot do is fully integrate with our cars.
With the rapid advancement of mobile, cloud, and embedded technologies, it may surprise most that In-Vehicle Infotainment (IVI) systems are typically developed four to five years before the vehicles are release to the market. In fact, most 2014 models are running IVI systems from 2009. By most modern industry standards, a five-year development lifecycle is unacceptable. So how is it that one of our most valued commodities - the automobile - is subjected to such a technological lag?