The future of automotive software engineering. Dr. Ulrik Eklund Innovative Software Developments in the Automotive Industry Summit Berlin, 2015

Transcription

1 The future of automotive software engineering Dr. Ulrik Eklund Innovative Software Developments in the Automotive Industry Summit Berlin, 2015

2 It's tough to make predictions, especially about the future. Yogi Berra

3 3 key take-aways 1. Don t expect yesterdays software development practices to still work tomorrow 2. The boundary between vehicles and surrounding software will be blurred 3. The golden standard will be set by practices not yet seen in the automotive domain

4 What influences software engineering in the automotive industry today? PRESENT SITUATION

5 Growth of embedded systems Size in object instructions Space flight control Switching systems Automotive embedded SW Linux kernel Years Ebert, C., Jones, C.: Embedded Software: Facts, Figures, and Future. Computer. 42, (2009).

6 Vehicle software size Vehicle Infotainment Total [Mbyte]

7 Vehicle software size On-board software doubles in size every 2-3 years Software grows >10x within 10 years

8 Development processes and timing A vehicle 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

9 More than 50 billion connected devices by 2020 Forecast by Ericsson,

10 Vehicle software Everything will be connected all the time including cars

11 Some current challenges ISO Functional safety, road vehicles No major impact on mature S/W developers Multi/many-core + non-parallell real-time algorithms Right at the research forefront Security and privacy in a connected world

12 Some ways to presently handle the situation of in-vehicle software PRESENT COPING STRATEGIES

13 Coping strategies Standardisation Model-driven development Design information databases Architecture

14 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) Public standards J1939 (mostly commercial vehicles) AUTOSAR application interfaces

15 Modeldriven developme nt Successful development of key features in-house, but not by writing code Models are 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% 60% more detected errors in design phase compared to classical development Kirstan, S., Zimmermann, J.: Evaluating costs and benefits of model-based development of embedded software systems in the car industry. Results of a qualitative Case Study. In: Proceedings of the European Conference on Modeling Foundations and Applications (2010).

16 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

17 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, GENIVI and/or other architectural platforms or All of the above

18 What will we see in future automotive software engineering? FUTURE SOFTWARE ENGINEERING PRACTICES

19 We always overestimate the change that will occur in the next two years and underestimate the change that will occur in the next ten. Don't let yourself be lulled into inaction. Bill Gates

20 Continuous everything Continuous Planning Continuous Integration Continuous Deployment Continuous Delivery Continuous Verification Continuous Testing Continuous Compliance Continuous Security Continuous Use Continuous Trust Continuous Run-Time Monitoring Continuous Improvement Continuous Innovation Fitzgerald, B., Stol, K.-J.: Continuous software engineering and beyond: trends and challenges. In: Proceedings of the International Workshop on Rapid Continuous Software Engineering. pp ACM (2014).

21 Evolution of practices 1. Agile Development teams can change direction 2. Continuous integration Teams deliver any time they want 3. Continuous deployment Companies deliver new value all the time to customers 4. Data-driven development Real world usage is used to drive innovation Holmström Olsson, H., Alahyari, H., Bosch, J.: Climbing the Stairway to Heaven. - A Mulitiple-Case Study Exploring Barriers in the Transition from Agile Development towards Continuous Deployment of Software, Euromicro Conference on Software Engineering and Advanced Applications. Cesme, Izmir, Turkey (2012).

22 Stage-gate S/W development Team 1 Team 2 Team 3 Team Team Project start SOP

23 Agile development in the automotive industry Front-loading is the opposite of being agile Agile is fairly recent in the automotive industry 3.25 years on average for those already doing agile according to a 2014 survey Kugler Maag Cie State of Practice Agile in Automotive,

24 Agile S/W development Team 1 Team 3 Team 2 Team Team Project start SOP

25 Continous integration Team 1 Team 1 Team 2 Team 3 Team 3 Team Team Team Team Project start SOP

26 Continous deployment Team 1 Team 1 Team 2 Team 3 Team 3 Team Team Team Team Team Project start SOP

27 Data-driven innovation and development R&D team 2-4 week cycle Deploy new functionality Usage and other performance data Vehicle Vehicle Vehicle Vehicle Vehicle Vehicle Eklund, U., Bosch, J.: Architecture for Large-Scale Innovation Experiment Systems. Proceedings of the Joint Working IEEE/IFIP Conference on Software Architecture & European Conference on Software Architecture. IEEE, Helsinki, Finland (2012).

28 Actively shaping the software portfolio and the ecosystem that contributes to it GROOMING THE SOFTWARE PORTFOLIO

29 Utilise open source AUTOSAR (GPL license) GENIVI (Infotainment) Allseen/Alljoyn (IoT platform) Brillo (Google IoT platform) Yocto (embedded Linux) Contiki (IoT platform)

30 Open up platforms When large players open up their platforms it tend to disrupt industry domains Requires a different mindset not only among developers, but also on how to do business Miscellaneous/Conceptual/iPhoneOSTechOverview/ Introduction/Introduction.html

31 Software platform evolution over time Competitive feature 3rd party development Innovative feature 3rd party development Incorporate into platform Incorporate into platform Software platform Outsource commodities Outsource commodities Supplier development Open source Supplier development Eklund, U., Bosch, J.: Introducing Software Ecosystems for Mass-Produced Embedded Systems. In: Proceedings of the International Conference on Software Business. Springer, Cambridge, MA, USA (2012).

32 Connected cars Hanson, J: 5 IoT challenges for connected car dev, (2014).

33 Future properties of connected devices 1. Automation Collection, analysis and usage of data will be done automatically 2. Intelligence Devices will adapt to the current context 3. Dynamical Devices in a new situation will connect any way possible 4. Zero configuration Users will not need any technical expertise 5. Part of a system-of-systems No-one will control/design every part

34 Architectures for connected vehicles Optimised for developing products and features with the shortest possible leadtime Emphasise modularity and composability of software from different teams Standardised platforms are the norm either industry-wide encompassing 3 rd parties or developed within the large organisation Eklund, U., Bosch, J.: Archetypical Approaches of Fast Software Development and Slow Embedded Projects. Euromicro Conference on Software Engineering and Advanced Applications. IEEE, Santander, Spain (2013).

35 Characteristics of development teams Cross-functional teams Wide set of competences, from internet security to active safety within the same team Feature-oriented Self-directed Choose their own process and activities Integration is ensured by the underlying platform and its architecture

36 1. Continuous everything 8 Characteristics of future automotive software development 2. Active orchestration of the software ecosystem 3. Open source 4. Data-driven development & innovation

37 8 Characteristics of future automotive software development 5. Vehicles as part of system-of-systems 6. Architecture suitable for everything being connected 7. Open up vehicle software platforms 8. Reshaped R&D organisation

38 in the future, all companies will be software companies George Colony VD Forrester Research

39 References 1. Ebert, C., Jones, C.: Embedded Software: Facts, Figures, and Future. Computer. 42, (2009). 2. Ericsson, (2011) 3. Kirstan, S., Zimmermann, J.: Evaluating costs and benefits of model-based development of embedded software systems in the car industry. Results of a qualitative Case Study. In: Proceedings of the European Conference on Modeling Foundations and Applications (2010). 4. Fitzgerald, B., Stol, K.-J.: Continuous software engineering and beyond: trends and challenges. In: Proceedings of the International Workshop on Rapid Continuous Software Engineering. ACM (2014). 5. Holmström Olsson, H., Alahyari, H., Bosch, J.: Climbing the Stairway to Heaven. - A Mulitiple-Case Study Exploring Barriers in the Transition from Agile Development towards Continuous Deployment of Software, Euromicro Conference on Software Engineering and Advanced Applications. Cesme, Izmir, Turkey (2012). 6. Kugler Maag Cie, State of Practice Agile in Automotive, (2014) 7. Eklund, U., Bosch, J.: Architecture for Large-Scale Innovation Experiment Systems. Proceedings of the Joint Working IEEE/IFIP Conference on Software Architecture & European Conference on Software Architecture. IEEE, Helsinki, Finland (2012) Introduction/Introduction.html 9. Eklund, U., Bosch, J.: Introducing Software Ecosystems for Mass-Produced Embedded Systems. In: Proceedings of the International Conference on Software Business. Springer, Cambridge, MA, USA (2012). 10. Hanson, J: 5 IoT challenges for connected car dev, (2014). 11. Eklund, U., Bosch, J.: Archetypical Approaches of Fast Software Development and Slow Embedded Projects. Euromicro Conference on Software Engineering and Advanced Applications. IEEE, Santander, Spain (2013)