Auf Basis des Integrations-Modells kann nun der Software-Integrationstest durchgeführt werden. ISO 26262 empfiehlt die gleichen Methoden wie für den Software-Unit-Test: funktionale Tests, strukturelle Tests, Messung des Ressourcenbedarfs sowie Back-to-Back-Tests zwischen Simulations-Modell und Code. Diese Tests lassen sich analog zum Software-Unit-Test mit den gleichen Werkzeugen durchführen. sj
Literatur + Links
[1] Road vehicles – Functional Safety. ISO 26262 (Committee Draft), International Organization for Standardization, 2008.
[2] Functional Safety of Electrical/Electronic/ Programmable Electronic Safety Related Systems. IEC 61508, 1998.
[3] MISRA AC TL: Modelling style guidelines for the application of TargetLink in the context of automatic code generation. Version 1.0, 2007.
[4] MathWorks Automotive Advisory Board, Control Algorithm Modeling. Guidelines using Matlab, Simulink, and Stateflow. Version 2.0, 2007.
[5] Modeling Guidelines for Matlab/Simulink/Stateflow and TargetLink Version 2.1. dSpace GmbH, 2008.
[6] MISRA-C: 2004 Guidelines for the use of the C Language in critical systems. MIRA, 2004.
[7] Tracing Requirements to Designs, Tests, and Generated Code. www.mathworks.com/products/simverification
[8] SystemDesk. www.dspace.de/goto?SystemDesk
[9] Model Examiner: Automatic Compliance Checks for Simulink and TargetLink models. html>www.model-engineers.com/our-products/model-examiner.html
[10] EmbeddedTester. www.btc-es.de/
[11] MTest classic. www.mtest-classic.com/
[12] Analyzing Model Coverage. www.mathworks.com/products/simverification
[13] Code Coverage Analysis. www.dspace.de/ww/en/pub/home/products/sw/pcgs/code_coverage.cfm
[14] CTC++. verifysoft.com/de.html>www.verifysoft.com/de.html
[15] IBM Test Real-Time. www.ibm.com/developerworks/rational/products/testrealtime
Autor: | |
![]() | Dipl.-Math. Michael Beine ist Lead Product Manager bei dSpace in Paderborn. mbeine@dspace.de |