|
The integration of hardware and software in cars has always been very complex and it takes a long time to improve the process.
Hardware: typically requires longer planning, design, and manufacturing cycles. The software innovation moves at a much faster speed
Software: new features demanded by the the market often require new hardware - which triggers yet another planning, design, and manufacturing cycle. Cars caught un the middle of this cycle are often left behind. It is what is.
Engineering process / supplier integration / testing: the most complex part. Not all software is created equal not all software is written by BMW. The best software engineers will still have difficulties executing a poor design. Even the best design may not be executed as intended if the team is new or lacks the experience working on specific problems.
Security: with integration of cellular connectivity and multiple hosts (driver app, BMW in-country and global HQ servers, authorized apps running on the curved display, and many more) and closer integration with various control units, code security is even more important and not discussed for obvious reasons. Code security is being used to describe a much larger scope. For example, is the incoming request arriving from a valid host?
In short, if the driver doesn't see a polite (yet alarming) "blue screen of demise" then progress can be declared.
This is a _long_ journey. Good example is Apple's IOS now at iteration 16.
|