Skip to main content

Automotive Software Development

  • Chapter
  • First Online:
Automotive Software Architectures
  • 6651 Accesses

Abstract

In this chapter we describe and elaborate on software development processes in the automotive industry. We introduce the V-model for the entire vehicle development and we continue to introduce modern, agile software development methods for describing the ways of working of software development teams. We start by describing the beginning of all software development—requirements engineering—and we describe how requirements are perceived in automotive software development using text and different types of models. We discuss the specifics of automotive software development such as variant management, different integration stages of software development, testing strategies and the methods used for these. We review methods used in practice and explain how they should be used. We conclude the chapter with discussion on the need for standardization as the automotive software development is based on client-supplier relationships between the OEMs and the suppliers developing components of vehicles.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Vard Antinyan, Miroslaw Staron, Wilhelm Meding, Per Österström, Erik Wikstrom, Johan Wranker, Anders Henriksson, and Jörgen Hansson. Identifying risky areas of software code in agile/lean software development: An industrial experience report. In Software Maintenance, Reengineering and Reverse Engineering (CSMR-WCRE), 2014 Software Evolution Week-IEEE Conference on, pages 154–163. IEEE, 2014.

    Google Scholar 

  2. Christian Allmann, Lydia Winkler, Thorsten Kölzow, et al. The requirements engineering gap in the oem-supplier relationship. Journal of Universal Knowledge Management, 1(2):103–111, 2006.

    Google Scholar 

  3. Jan Bosch, Gert Florijn, Danny Greefhorst, Juha Kuusela, J Henk Obbink, and Klaus Pohl. Variability issues in software product lines. In International Workshop on Software Product-Family Engineering, pages 13–21. Springer, 2001.

    Google Scholar 

  4. Manfred Broy. Challenges in automotive software engineering. In Proceedings of the 28th international conference on Software engineering, pages 33–42. ACM, 2006.

    Google Scholar 

  5. IEEE Standards Coordinating Committee et al. IEEE Standard glossary of software engineering terminology (IEEE Std 610.12-1990). los alamitos. CA: IEEE Computer Society, 1990.

    Google Scholar 

  6. Jane Cleland-Huang, Raffaella Settimi, Xuchang Zou, and Peter Solc. Automated classification of non-functional requirements. Requirements Engineering, 12(2):103–120, 2007.

    Google Scholar 

  7. DeJiu Chen, Martin Törngren, Jianlin Shi, Sebastien Gerard, Henrik Lönn, David Servat, Mikael Strömberg, and Karl-Erik Årzen. Model integration in the development of embedded control systems-a characterization of current research efforts. In Computer Aided Control System Design, 2006 IEEE International Conference on Control Applications, 2006 IEEE International Symposium on Intelligent Control, 2006 IEEE, pages 1187–1193. IEEE, 2006.

    Google Scholar 

  8. Jan Dannenberg and Jan Burgard. 2015 car innovation: A comprehensive study on innovation in the automotive industry. 2015.

    Google Scholar 

  9. Simulink Demo. Modeling an anti-lock braking system.

    Google Scholar 

  10. Hubert Dubois, Marie-Agnès Peraldi-Frati, and Fadoi Lakhal. A model for requirements traceability in a heterogeneous model-based design process: Application to automotive embedded systems. In Engineering of Complex Computer Systems (ICECCS), 2010 15th IEEE International Conference on, pages 233–242. IEEE, 2010.

    Google Scholar 

  11. Vincent Debruyne, Françoise Simonot-Lion, and Yvon Trinquet. EAST–ADL – An architecture description language. In Architecture Description Languages, pages 181–195. Springer, 2005.

    Google Scholar 

  12. Ulrik Eklund and Jan Bosch. Architecture for embedded open software ecosystems. Journal of Systems and Software, 92:128–142, 2014.

    Google Scholar 

  13. Ulrik Eklund and Håkan Gustavsson. Architecting automotive product lines: Industrial practice. Science of Computer Programming, 78(12):2347–2359, 2013.

    Google Scholar 

  14. Ulf Eliasson, Rogardt Heldal, Eric Knauss, and Patrizio Pelliccione. The need of complementing plan-driven requirements engineering with emerging communication: Experiences from Volvo Car Group. In Requirements Engineering Conference (RE), 2015 IEEE 23rd International, pages 372–381. IEEE, 2015.

    Google Scholar 

  15. Markus Hardt, Rainer Mackenthun, and Jürgen Bielefeld. Integrating ECUs in vehicles-requirements engineering in series development. In Requirements Engineering, 2002. Proceedings. IEEE Joint International Conference on, pages 227–236. IEEE, 2002.

    Google Scholar 

  16. Frank Houdek. Managing large scale specification projects. In Requirements Engineering foundations for software quality, REFSQ, 2013.

    Google Scholar 

  17. ISO. 26262–road vehicles-functional safety. International Standard ISO, 26262, 2011.

    Google Scholar 

  18. Ivar Jacobson, Grady Booch, and Jim Rumbaugh. The objectory software development process. ISBN: 0-201-57169-2, Addison Wesley, 1997.

    Google Scholar 

  19. Ludwik Kuzniarz and Miroslaw Staron. On practical usage of stereotypes in UML-based software development. the Proceedings of Forum on Design and Specification Languages, Marseille, 2002.

    Google Scholar 

  20. Eric Knauss, Miroslaw Staron, Wilhelm Meding, Ola Söder, Agneta Nilsson, and Magnus Castell. Supporting continuous integration by code-churn based test selection. In Proceedings of the Second International Workshop on Rapid Continuous Software Engineering, pages 19–25. IEEE Press, 2015.

    Google Scholar 

  21. Vincent Langenfeld, Amalinda Post, and Andreas Podelski. Requirements Defects over a Project Lifetime: An Empirical Analysis of Defect Data from a 5-Year Automotive Project at Bosch. In Requirements Engineering: Foundation for Software Quality, pages 145–160. Springer, 2016.

    Google Scholar 

  22. Mahshad M Mahally, Miroslaw Staron, and Jan Bosch. Barriers and enablers for shortening software development lead-time in mechatronics organizations: A case study. In Proceedings of the 2015 10th Joint Meeting on Foundations of Software Engineering, pages 1006–1009. ACM, 2015.

    Google Scholar 

  23. Niklas MellegĂĄrd and Miroslaw Staron. Methodology for requirements engineering in model-based projects for reactive automotive software. In 18th ECOOP Doctoral Symposium and PhD Student Workshop, page 23, 2008.

    Google Scholar 

  24. Niklas MellegĂĄrd and Miroslaw Staron. A domain specific modelling language for specifying and visualizing requirements. In The First International Workshop on Domain Engineering, DE@ CAiSE, Amsterdam, 2009.

    Google Scholar 

  25. Niklas Mellegård and Miroslaw Staron. Characterizing model usage in embedded software engineering: a case study. In Proceedings of the Fourth European Conference on Software Architecture: Companion Volume, pages 245–252. ACM, 2010.

    Google Scholar 

  26. Niklas Mellegård and Miroslaw Staron. Distribution of effort among software development artefacts: An initial case study. In Enterprise, Business-Process and Information Systems Modeling, pages 234–246. Springer, 2010.

    Google Scholar 

  27. Niklas Mellegård and Miroslaw Staron. Improving efficiency of change impact assessment using graphical requirement specifications: An experiment. In Product-focused software process improvement, pages 336–350. Springer, 2010.

    Google Scholar 

  28. Nesredin Mahmud, Cristina Seceleanu, and Oscar Ljungkrantz. ReSA: An ontology-based requirement specification language tailored to automotive systems. In Industrial Embedded Systems (SIES), 2015 10th IEEE International Symposium on, pages 1–10. IEEE, 2015.

    Google Scholar 

  29. Daniel Ott. Defects in natural language requirement specifications at Mercedes-Benz: An investigation using a combination of legacy data and expert opinion. In Requirements Engineering Conference (RE), 2012 20th IEEE International, pages 291–296. IEEE, 2012.

    Google Scholar 

  30. Daniel Ott. Automatic requirement categorization of large natural language specifications at Mercedes-Benz for review improvements. In Requirements Engineering: Foundation for Software Quality, pages 50–64. Springer, 2013.

    Google Scholar 

  31. Alexander Pretschner, Manfred Broy, Ingolf H Kruger, and Thomas Stauner. Software engineering for automotive systems: A roadmap. In 2007 Future of Software Engineering, pages 55–71. IEEE Computer Society, 2007.

    Google Scholar 

  32. Marie-Agnès Peraldi-Frati and Arnaud Albinet. Requirement traceability in safety critical systems. In Proceedings of the 1st Workshop on Critical Automotive applications: Robustness & Safety, pages 11–14. ACM, 2010.

    Google Scholar 

  33. Joakim Pernstål, Tony Gorschek, Robert Feldt, and Dan Florén. Software process improvement in inter-departmental development of software-intensive automotive systems – A case study. In Product-Focused Software Process Improvement, pages 93–107. Springer, 2013.

    Google Scholar 

  34. Rakesh Rana, Miroslaw Staron, Christian Berger, Jörgen Hansson, Martin Nilsson, and Fredrik Törner. Improving fault injection in automotive model based development using fault bypass modeling. In GI-Jahrestagung, pages 2577–2591, 2013.

    Google Scholar 

  35. Rakesh Rana, Miroslaw Staron, Claire Berger, Jorgen Hansson, Martin Nilsson, and Fredrik Torner. Evaluating long-term predictive power of standard reliability growth models on automotive systems. In Software Reliability Engineering (ISSRE), 2013 IEEE 24th International Symposium on, pages 228–237. IEEE, 2013.

    Google Scholar 

  36. Rakesh Rana, Miroslaw Staron, Niklas Mellegård, Christian Berger, Jörgen Hansson, Martin Nilsson, and Fredrik Törner. Evaluation of standard reliability growth models in the context of automotive software systems. In Product-Focused Software Process Improvement, pages 324–329. Springer, 2013.

    Google Scholar 

  37. Miroslaw Staron, Jorgen Hansson, Robert Feldt, Anders Henriksson, Wilhelm Meding, Sven Nilsson, and Christoffer Hoglund. Measuring and visualizing code stability – A case study at three companies. In Software Measurement and the 2013 Eighth International Conference on Software Process and Product Measurement (IWSM-MENSURA), 2013 Joint Conference of the 23rd International Workshop on, pages 191–200. IEEE, 2013.

    Google Scholar 

  38. Miroslaw Staron, Ludwik Kuzniarz, and Ludwik Wallin. Case study on a process of industrial MDA realization: Determinants of effectiveness. Nordic Journal of Computing, 11(3):254–278, 2004.

    Google Scholar 

  39. Miroslaw Staron, Ludwik Kuzniarz, and Ludwik Wallin. A case study on industrial MDA realization – Determinants of effectiveness. Nordic Journal of Computing, 11(3):254–278, 2004.

    Google Scholar 

  40. Miroslaw Staron, Ludwik Kuzniarz, and Ludwik Wallin. Factors determining effective realization of MDA in industry. In K. Koskimies, L. Kuzniarz, Johan Lilius, and Ivan Porres, editors, 2nd Nordic Workshop on the Unified Modeling Language, volume 35, pages 79–91. Abo Akademi, 2004.

    Google Scholar 

  41. Sebastian Siegl, Martin Russer, and Kai-Steffen Hielscher. Partitioning the requirements of embedded systems by input/output dependency analysis for compositional creation of parallel test models. In Systems Conference (SysCon), 2015 9th Annual IEEE International, pages 96–102. IEEE, 2015.

    Google Scholar 

  42. Mikael Svahnberg, Jilles Van Gurp, and Jan Bosch. A taxonomy of variability realization techniques. Software: Practice and Experience, 35(8):705–754, 2005.

    Google Scholar 

  43. Jörg Schäuffele and Thomas Zurawka. Automotive software engineering – Principles, processes, methods and tools. 2005.

    Book  Google Scholar 

  44. Fredrik Törner, Martin Ivarsson, Fredrik Pettersson, and Peter Öhman. Defects in automotive use cases. In Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering, pages 115–123. ACM, 2006.

    Google Scholar 

  45. Andreas Vogelsanag and Steffen Fuhrmann. Why feature dependencies challenge the requirements engineering of automotive systems: An empirical study. In Requirements Engineering Conference (RE), 2013 21st IEEE International, pages 267–272. IEEE, 2013.

    Google Scholar 

  46. Jilles Van Gurp, Jan Bosch, and Mikael Svahnberg. On the notion of variability in software product lines. In Software Architecture, 2001. Proceedings. Working IEEE/IFIP Conference on, pages 45–54. IEEE, 2001.

    Google Scholar 

  47. Matthias Weber and Joachim Weisbrod. Requirements engineering in automotive development-experiences and challenges. In Requirements Engineering, 2002. Proceedings. IEEE Joint International Conference on, pages 331–340. IEEE, 2002.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2017 Springer International Publishing AG

About this chapter

Cite this chapter

Staron, M. (2017). Automotive Software Development. In: Automotive Software Architectures. Springer, Cham. https://doi.org/10.1007/978-3-319-58610-6_3

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-58610-6_3

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-58609-0

  • Online ISBN: 978-3-319-58610-6

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics