Diese Website verwendet Cookies, um das Angebot nutzerfreundlicher und effektiver zu machen. Bitte stimmen Sie der Verwendung von Cookies zu, um alle Funktionen der Website nutzen zu können.Weitere Informationen

26. - 28. Februar 2019 // Nürnberg, Germany

Konferenzen und Rahmenprogramm

Zurück zur Tagesansicht
Class 03 - The ETAS-Class: From Idea to Production ECU Code in One Day

From Idea to Production ECU Code in One Day Vortragssprache Englisch

During this one day class the participant will have the unique possibility to follow an ECU development process from the start to the end. During this journey you will see how a lot of hurdles and inefficiencies are being overcome to meet the current and future demands of development departments. Among others those demands are development speed, functional safety, traceability, variant handling, open source, software erosion, coding errors and many more. These demands come from competitive challenges and legal requirements but more and more also from the fact that using the wrong Toolchain could make it impossible to develop a valid solution at all. The participants will gain new insights on how to improve an existing development process or how to setup a new Toolchain and the related processes. During the day, a simple example is used to show how real artefacts (files) are being processed and generated in order to reach the goal of executing our generated code on both a virtual as well as a real ECU. In almost all real development projects the Toolchain will be heterogeneous. That means the tools will come from different tool vendors and parts of the Toolchain will have been implemented by the development department itself. This also applies to the Toolchain shown during our class. There will be more than 10 tools from different tool vendors, which create an efficient Toolchain by combining the best available tools for each step. Besides this, during the day, you will have the opportunity to discuss and get into contact with some of the best industry experts in their respective fields. Don?t miss this opportunity. In the following you see a list of problems that most if not all software development-teams face. For each of the problems solutions exist in the form of methods, tools and processes. But we all know that a tool alone will not be sufficient. It is also important to get the buy-in from the engineers using those tools. Training and face to face contact to the ?inventors? of the tools will help to make this initial step. In order not to frequently re-invent the wheel it is essential to use an open platform or better an eco-system that offers a multitude of already existing components for reuse. This reduces the effort for development, rollout and customization. During this class, the majority of tools use the Eclipse IDE. AUTOSAR as the current standard system offers maximum flexibility during the development process. Exploiting this flexibility requires a whole set of tools and software components, which need to interwork in order to create the underlying foundation for easily portable application code. Tracing is essential. But tracing must not introduce high overhead nor additional hardware, otherwise it will be used lesser and lesser the closer we come to production. Best will be if tracing stays active in the production code. The GLIWA Timingsuite-T1, besides many other advantages, allows this. Models used as source for the generation of embedded system code have to comply with modelling guidelines for several reasons. Robustness and readability are two major objectives. The MES tools help to enforce the quality of a model by automated checks and give guidance for model improvement. Another positive effect of rule checkers is that once an error has been solved it is possible to create rules that make sure that this type of error will never happen again. Some of the code will be written by hand, other code will be generated by configuration tools others will be automatically generated from models (model based development). During the workshop we will show mainly 3 concepts that allow to reduce the complexity of the solution, and therefore reduce the complexity of the implemented code. In the ideal case the complexity of the solution will be at the same level as the intrinsic complexity of the problem, as it avoids added complexity by unsuited methods, languages and tools. Even the smallest system will grow in complexity over time with new variants and new versions being added. If variant handling is not properly addressed during the setup of the Toolchain and during the start of the project(s) the amount of work that is being wasted due to fixing errors again and again or having software that implements the same features in many slightly different ways, will make projects unprofitable or even worse, will make projects fail e.g. due to insufficient quality in Functional Safety projects. Last but not least there is the functional testing, no matter where the test is being run. May this be on a virtual ECU, a real ECU or any other execution or simulation platform. And there is a ?glue? that puts it all together: traceability. Especially for FuSi (ISO26262) projects it is essential that it is e.g. possible to trace or link a failed test, to the implementation and all the way to the requirements for each relevant variant. All this and more will be shown during a single day. Ralph Müller (Eclipse Foundation) - The power of large Eco Systems - IDE, Work-Groups and more Chokri Mraidha (CEA LIST) - Model-Driven (Co-)Engineering - Papyrus Bernhard Reckels (ETAS) - Components of an AUTOSAR Tool-Suite - ISOLAR-A, ISOLAR-B, RTA, BSW Robert Hellebrand (pure-systems) - Properly using Variant-Management Software - pure::variants Markus Behle (ETAS) - Structured analysis with formal verification (ISO26262) - SCODE and visualized analysis of systems described by formulas - CONGRA (both with automatic code generation) Darren Buttle (ETAS) - Graphical & textual software development with high-integrity code gen - ASCET Andreas Graf (itemis) - How to implement requirements traceability - YAKINDU Heiko Dörr (MES) - Constantly making sure the model quality stays at the required level - MXAM Johannes Wagner (ETAS) - Virtual test environment for Embedded Systems Code - ISOLAR-EVE Peter Gliwa (GLIWA) - End-to-end model-check, from mind to binary ECU code - Timingsuite-T1 Jens Lüdemann (Pike Tec) - Functional Testing of embedded SW on MIL, SIL, HIL, PIL and ECU - TPT Arndt-Michael Meyer (ETAS) - Benefits and pains of setting up a seamless toolchain

--- Datum: 27.02.2018 Uhrzeit: 09:30 Uhr - 17:30 Uhr Ort: Conference Counter NCC Ost

Sprecher

top

Der gewählte Eintrag wurde auf Ihre Merkliste gesetzt!

Wenn Sie sich registrieren, sichern Sie Ihre Merkliste dauerhaft und können alle Einträge selbst unterwegs via Laptop oder Tablett abrufen.

Hier registrieren Sie sich, um Daten der Aussteller- und Produkt-Plattform sowie des Rahmenprogramms dauerhaft zu speichern. Die Registrierung gilt nicht für den Ticket- und Aussteller-Shop.

Jetzt registrieren

Ihre Vorteile auf einen Blick

  • Vorteil Sichern Sie Ihre Merkliste dauerhaft. Nutzen Sie den sofortigen Zugriff auf gespeicherte Aussteller oder Produkte: egal wann und wo - inkl. Notizfunktion.
  • Vorteil Erhalten Sie auf Wunsch via Newsletter regelmäßig aktuelle Informationen zu neuen Ausstellern und Produkten - abgestimmt auf Ihre Interessen.
  • Vorteil Rufen Sie Ihre Merkliste auch mobil ab: Einfach einloggen und jederzeit darauf zugreifen.