Ulrik Eklund_Volvo Cars IT University.pdf - Lindholmen Science Park

Binary size [Mbyte]
500
450
400
350
300
250
200
150
100
50
The future of automotive
software engineering
Ulrik Eklund
Volvo Car Corporation / IT University
ulrik.eklund@ituniv.se
Lindholmen software development day
2010-10-22
This is the (near) future
S/W size in new car models
Meego
infotainment
binary
Graphic
infotainment with
integrated GPS
0
1998 2000 2002 2004 2006 2008 2010 2012 2014
Year
Vehicle Infotainment
Connected car +
fully graphic HMI
Safety and
driver support
1

Software processes & timing
• Vehicle manufacturers tend to use the same mindset for mechanical
design and software design
• A car project has a lead time of about 30 months
– From the decision what to build until first car rolls off the manufacturing line
– Deciding what to build takes up to 18 months in addition to this
– Stage-gate processes
• Current trends for the mechanical vehicle design
– Shortening lead times < 30 months
– ”front load” the design work and freezing blueprints early
– Lean, but not agile
• That software follows the same principle is “natural”
Software process constraints
• ISO 26262 – Functional safety, road
vehicles
– Will be mandatory for everybody
developing safety-critical automotive
software
– No major impact on mature S/W
developers
2

• Standardisation
Coping strategies
• Model-driven development
• Design information databases
• Architecture
Standardisation
• Standardised functional interfaces is seen as the
solution to
– Integration
– Minimise engineering work, by reuse
– Launching new products based on existing solutions
• Proprietary standardisation (across vehicle lines)
– Ford motor Company, started with re-using power packs
• “Public”
– J1939 (mostly commercial vehicles)
– AUTOSAR Application interfaces
3

Model-driven development
• Traditionally: Software is developed by suppliers
• Trend: Car manufacturers increases software development of key
features in-house
– But not by writing code
– Models as the implementation = code generation
– Enables domain experts to do code
– Primary drivers are quality and early V&V, cost is a nice side benefit
– The OEM ”owns” the important stuff
• Average cost savings of 27%, lead-time savings of 36%
– Highly dependent on experience, varies up to 10%
• 60% more detected errors in design phase compared to classical
development
Model-driven development
• The following is usually not code-generated
– Safety critical functions, because of lack of trust in tools
– Relatively small enhancements of existing classically
developed functions
– Functions for which the know-how is at the supplier
– At suppliers classical coding is still norm
– Functions in the Infotainment system area! (

Design information databases
• Going from paper specifications to databases
– Several tools are already in use
– Strong support for
• maintaining relationship between design information
• instantiate a specific design variant in a product
• version control
– Poor on presenting information
• Little graphical representation
Architecture
• Disparate view on what architecture is:
– Architecture = Design of network topology, i.e. use of
communication protocols and electronic control units (ECUs)
or
– Architecture = Standardisation of interfaces
• Sometimes together with model-driven development
• Network signal databases
or
– Architecture = Stakeholder analysis, quality attributes, and view &
viewpoints (mainly logical)
or
– Architecture = AUTOSAR and/or other architectural platforms
or
– All of the above
5

Architecture platform
• AUTOSAR
– component-based architecture
– component templates in XML
– associated methodology and tool-chain
– Basic software components & interfaces
defined
– Not focusing on infotainment
– Already in use, e.g. on some BMW ECUs
Infotainment architecture
platforms
• Windows Embedded Automotive 7
– Used by Ford Sync, Fiat Blue&Me, and Kia
– Support for HMI development tools, speech recognition, mobile
device integration and several connected services
• MeeGo
– Linux-based architecture for various applications, e.g. handhelds,
netbooks, in-vehicle infotainment
– Development toolkit, sample navi, voice and data connectivity,
telephone stack, Bluetooth, media frameworks and file system
included in v. 1.0
– “Android for Infotainment”
• GENIVI
– Alliance for developing standard solutions for infotainment
– Linux-based
– Probably based on Meego architecture
6

Trends not seen (yet?)
• ”Openness”
– Manufacturers still decides what services
goes into the car, e.g. Spotify
– No production vehicle software released as
open source
• Agile development
Summary
• Software in vehicles increases dramatically: Size, features,
ECUs, …
• There is no consensus in how to deal with this, but some
strategies are
– Standardisation of interfaces
– Model-driven development
– Design information databases
– Architecture (whatever that is)
• Vehicle companies still see themselves as manufacturing
products
– Not software developers
– Slow adopters of current software engineering ”trends”
7

More information
• General overviews
– Fabbrini, F., Fusani, M., Lami, G., & Sivera, E. (2008). Software Engineering in the European
Automotive Industry: Achievements and Challenges. In Computer Software and Applications, (pp.
1039-1044). doi:10.1109/COMPSAC.2008.140
– Krüger, I. (2010). Opinion: An Outlook on Automotive Software. IEEE Embedded Systems Letters,
IEEE Embed. Syst. Lett. (USA), 2(1), 14-15. Retrieved from
http://dx.doi.org/10.1109/LES.2010.2047079
– Pretschner, A., Broy, M., Krüger, I. H., & Stauner, T. (2007). Software Engineering for Automotive
Systems: A Roadmap. In 2007 Future of Software Engineering (pp. 55-71). Presented at the
International Conference on Software Engineering, IEEE Computer Society. Retrieved from
http://portal.acm.org/citation.cfm?id=1253532.1254710
– Sangiovanni-Vincentelli, A., & Di Natale, M. (2007). Embedded System Design for Automotive
Applications. Computer, 40(10), 42-51. doi:10.1109/MC.2007.344
• Driver support and safety features
– Dan Nilsson. (2010, October 10). Google testar förarlös bil. Svenska Dagbladet. Stockholm, Sweden.
Retrieved from http://www.svd.se/naringsliv/motor/google-testar-forarlos-bil_5485569.svd
8

More information
• Connected car
– Automotive technology: The connected car. (2009 June 4). The Economist,
http://www.economist.com/sciencetechnology/tq/displayStory.cfm?story_id=13725743
– Dedicated Short Range Communication (DSRC): CEN 12253,12795, 12834,13372 & ISO 14906
– ICT Results. (2009). Download, install and drive – the future of automotive software. ICT Results,
http://cordis.europa.eu/ictresults/index.cfm/section/news/tpl/article/BrowsingType/Features/ID/90412
– Smethurst, G. (2010). Changing the In-Vehicle Infotaiment Landscape. GENIVI Alliance,
http://www.genivi.org/portals/9/documents/GENIVI%20White%20Paper%20-
%20Changing%20the%20IVI%20Landscale.pdf
• Standardised software interfaces
– A. Tsakiris, (2010). Managing Software Interfaces of On-Board Automotive Controllers. Conference
presentation presented at the SATURN,
http://www.sei.cmu.edu/library/abstracts/presentations/tsakirissaturn2010.cfm?WT.DCSext.abstractsource=RelatedLinks
– AUTOSAR application interfaces,
http://www.autosar.org/index.php?p=3&up=1&up=1&uup=6&uuup=0&uuuup=0&uuuuup=0
– J1939 Recommended Practice for a Serial Control and Communications Vehicle Network,
http://www.sae.org/standardsdev/groundvehicle/j1939a.htm
• Automotive software processes
– ISO/IEC 15504 Software Process Improvement and Capability Determination (SPICE)
– ISO 26262 Road vehicles -- Functional safety (forthcoming)
More information
• Model-based development
– Dr. Jens Zimmermann & Sascha Kirstan (2010), “Costs and benefits of model-based development of
embedded software systems in the automotive domain”, http://www.altran.de/index.php/en/m-tec/mnews/m-news-downloads
– Broy, M., Feilkas, M., Herrmannsdoerfer, M., Merenda, S., & Ratiu, D. (2010). Seamless Model-
Based Development: From Isolated Tools to Integrated Model Engineering Environments.
Proceedings of the IEEE, Proc. IEEE (USA), 98(4), 526-45. Retrieved from
http://dx.doi.org/10.1109/JPROC.2009.2037771
• Design data management tools
– Vector eASEE Automotive Solution - System Data Management,
http://www.vector.com/vi_easee_sdm_en.html
– Systemite SystemWeaver, http://systemite.se/content/products-services/systemweaver-concept
• Domain specific langauges and tools
– Simulink for AUTOSAR, http://www.mathworks.com/automotive/standards/autosar.html
– Da Vinci developer, http://www.vector.com/vi_davinci_developer_en,,223.html
– Aquintos PreVision, http://www.aquintos.com/index.php?page=464
– EAST-ADL2, http://www.atesst.org/
9

More information
• Software architecture in automotive
– Broy, M., Gleirscher, M., Merenda, S., Wild, D., Kluge, P., & Krenzer, W. (2009). Toward a holistic
and standardized automotive architecture description. Computer, 42(12), 98-101. Retrieved from
http://dx.doi.org/10.1109/MC.2009.413
– Gustavsson, H., & Eklund, U. (2010). Architecting Automotive Product Lines: Industrial Practice. In
Software Product Lines: Going Beyond, Lecture Notes in Computer Science (Vol. 6287, pp. 92-105).
Presented at the Software Product Line Conference, Jeju, South Korea: Springer. doi:10.1007/978-3-
642-15579-6_7
– Hans Grönniger, Jochen Hartmann, Holger Krahn, Stefan Kriebel, Lutz Rothhardt, & Bernhard
Rumpe. (2008). View-Centric Modeling of Automotive Logical Architectures. Presented at the
Tagungsband des Dagstuhl-Workshop MBEES: Modellbasierte Entwicklung eingebetteter Systeme
IV, TU Braunschweig.
• Architecture platforms
– AUTOSAR, http://www.autosar.org
– Windows Embedded Automotive 7, http://www.microsoft.com/windowsembedded/enus/products/windows-embedded-automotive/default.mspx
– Ford Sync, http://www.fordvehicles.com/technology/sync/
– Meego, http://www.meego.com
– GENIVI, http://www.genivi.org
10