Advertisement

Integration of Development Interface Agreement, Supplier Safety Assessment and Safety Management for Driver Assistance Systems

  • T. FreseEmail author
  • D. Hatebur
  • I. Côté
  • M. Heisel
Chapter

Zusammenfassung

For most features in the automotive domain, the realized functionality is spread over several Electronic Control Units (ECUs) provided by a number of suppliers. To develop such a feature a close cooperation between suppliers and the Original Equipment Manufacturer (OEM, e. g. Ford) is necessary. During product development, the involved suppliers and the OEM have to create a large set of aligned artefacts, consisting of textual documents (e. g. specifications, test plans), requirements (e. g. in a requirement management tool), models, source code etc. To improve readability, we will use the term “documents” in this paper. Note that this includes all types of artefacts as mentioned above.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Literatur

  1. [1] International Organization for Standardization (ISO), Road Vehicles – Functional Safety, ISO 26262, 2011.Google Scholar
  2. [2] International Electro mechanical Commission (IEC), Functional safety of electrical/electronic/programmable electronic safety-relevant systems, IEC 61508, 2000.Google Scholar
  3. [3] K. Beckers, I. Côté, T. Frese, D. Hatebur, M. Heisel, Systematic Derivation of Functional Safety Requirements for Automotive Systems, in: Proceedings of SAFECOMP, LNCS 8666, Springer, 65–80, 2014.Google Scholar
  4. [4] K. Beckers, I. Côté, T. Frese, D. Hatebur, M. Heisel, A structured and systematic model-based development method for automotive systems, considering the OEM/supplier interface, in: Reliability Engineering & System Safety, vol 158, 172–184, 2017Google Scholar
  5. [5] Dittel T., Aryus HJ. (2010) How to “Survive” a Safety Case According to ISO 26262. in: Schoitsch E. (eds) Computer Safety, Reliability, and Security. SAFECOMP 2010. Lecture Notes in Computer Science, vol 6351. Springer, Berlin, HeidelbergGoogle Scholar
  6. [6] E. Armengaud, Q. Bourrouilh, G. Griessnig, H. Martin2, P. Reichenpfader, Using the CESAR Safety Framework for Functional Safety Management in the context of ISO 26262, in: ERTS² 2012 – EMBEDDED REAL TIME SOFTWARE AND SYSTEMS, 2012Google Scholar
  7. [7] Birch J. et al. (2013) Safety Cases and Their Role in ISO 26262 Functional Safety Assessment, in: Bitsch F., Guiochet J., Kaaniche M. (eds) Computer Safety, Reliability, and Security. SAFECOMP 2013. Lecture Notes in Computer Science, vol 8153. Springer, Berlin, HeidelbergGoogle Scholar
  8. [8] RR. Hamann, J. Sauler, S. Kriso, W. Grote, J. Mössinger, Application of ISO 26262 in Distributed Development ISO 26262 in Reality, SAE Technical Paper 2009-01-0758, 2009Google Scholar

Copyright information

© Springer Fachmedien Wiesbaden GmbH, ein Teil von Springer Nature 2019

Authors and Affiliations

  1. 1.Ford-Werke GmbHKölnDeutschland
  2. 2.ITESYS Inst. f. tech. Sys. GmbHDortmundDeutschland
  3. 3.Universität Duisburg-EssenDuisburgDeutschland

Personalised recommendations