Three Challenges when Testing AUTOSAR in a MBD Process

  • Génération automatique de code série

1:00:07min

Aperçu

In this free webinar recording, Felix Engel from dSPACE and Markus Gros from BTC Embedded Systems share best practices and common mistakes they have observed during their combined 25 years of industry experience. The AUTOSAR Standard was introduced over a decade ago with the goal of facilitating the management of software architectures for automotive embedded software. The standardized interface concept makes software components more independent from the hardware architecture, and it makes collaboration between companies and the reuse of software across different projects much easier.

But especially in a model-based development process, testing AUTOSAR software brings some challenges and we often hear questions like:

  • On which architecture level (composition?, SWC?, runnable?) can and should we test?
  • How can we efficiently handle the different AUTOSAR interface types during MIL/SIL/PIL testing?
  • Which test methods should be used?

Hôtes

Markus Gros

Markus Gros

Vice President Marketing & Sales BTC Embedded Systems AG Berlin, Germany

Felix Engel

Felix Engel

Strategic Product Manager Code Generation, dSPACE GmbH

Faire avancer l'innovation. Toujours à la pointe de l'évolution technologique.

S’abonner à nos newsletters, gérer ses abonnements ou se désabonner. La newsletter mensuelle contenant toutes les informations liées à l’aéronautique et défense.

Enable form call

At this point, an input form from Click Dimensions is integrated. This enables us to process your newsletter subscription. The form is currently hidden due to your privacy settings for our website.

External input form

By activating the input form, you consent to personal data being transmitted to Click Dimensions within the EU, in the USA, Canada or Australia. More on this in our privacy policy.