Modellierung im Automotive-Umfeld Traum, Wirklichkeit oder Alptraum?

Size: px

Start display at page:

Download "Modellierung im Automotive-Umfeld Traum, Wirklichkeit oder Alptraum?"

Constance Washington
5 years ago
Views:

1 Modellierung im Automotive-Umfeld Traum, Wirklichkeit oder Alptraum? BICCtalk, 5. Februar 2013 Stefan Kuntz, Continental Automotive GmbH, Regensburg

2 Modeling in the Automotive Context Dream, Reality or Nightmare? BICCtalk, February 5 th, 2013 Stefan Kuntz, Continental Automotive GmbH, Regensburg

3 Introduction Stefan Kuntz! Project Manager Advanced Development at Continental Automotive GmbH in Regensburg! Member of the Advanced Development Team in Business Unit Powertrain Engine Systems ECU Engineering! Topics:! Modeling various aspects in the system development from customer requirements, system to Hardware and Software Implementation! Methodology and methods! Time frame: Five years ahead! Supporting the development and improvement of Electronics Architecture and Software Technology - Architecture Description Language (EAST-ADL) and Automotive Open System Architecture (AUTOSAR)! Participating and involved in a number of public funded research projects 3 / S. Kuntz

4 Introduction Automotive Context Powertrain Engine Systems: Gasoline DI and SCR Manifold Air Pressure Electronic Throttle Control Exhaust Gas Recirculation Valve (EGR) Exhaust Bypass Valve General Purpose Actuator Variable Lift Control High Temperature Nox Mass Air Flow with integrated Temperature Canister Purge Solenoid In Cylinder Pressure Knock Coolant Water Temperature HC for Canister Purge SMART Natural Vacuum Leak Detector Fuel Pressure Manifold Absolute Pressure with Integrated Temp. Ultrasonic Oil Level Actuator 4 / S. Kuntz

5 Introduction Automotive Context Powertrain Engine Development Process System Function Software Hardware 5 / S. Kuntz

6 The Reality The best of all possible worlds Gottfried Leibniz! Modeling is performed on all levels: System, Function, Hardware and Software! Best most suitable tool is used for the specific purpose! Models are used for domain specific purposes! to describe, in the sense of documenting, the problem and its solutions! to simulate solutions! to conduct analyses in order to optimize the solutions However, there are still some challenges and lacks:! A significant number of gaps in the seamless and integrated approach across all domains! A lot of legacy must be carried on! A large number of individuals/engineers with various and different domain knowledge are involved in the development, maintenance and operations of a system 6 / S. Kuntz

7 One Pain Killer Architecture! Architecture! IEEE 1471 Recommended practice for architectural description of softwareintensive systems! Shared views among stakeholders result in a common model! Two Stakeholders have a common Concern and one model represents this Concern 7 / S. Kuntz

8 The Dream Some people call it A Vision! Seamless and integrated approach supported by a couple, a.k.a. Tool Box, of methods and tools! Role based work-flow driven tools enabling one to use the most appropriate method and tool! Support for abstraction and architecture management/engineering 8 / S. Kuntz

9 EAST-ADL Levels of Abstraction, Models and Cross Cutting Concerns 9 / S. Kuntz

Genealogy History of EAST-ADL and Funded Research Projects 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 EAST EEA EAST-ADL 1 SAFE

10 Genealogy History of EAST-ADL and Funded Research Projects EAST EEA EAST-ADL 1 SAFE ATESST ATESST 2 MAENAD EAST-ADL 2 TIMMO EAST-ADL TIMMO-2-USE TADL TADL 2 AUTOSAR R1.0 R2.0 R3.0 R4.0 R4.0.3 R4.1.1 Publication Specification 10 / S. Kuntz

11 The Nightmare Does it really need to become a nightmare?! Could you imagine the amount of information we are dealing with?! Could you imagine how many parameters and/or characteristics are varying when taking decisions during a system s lifetime?! Got this bad feeling while trying to keep the Cost-Quality-Function Triangle in balance? 11 / S. Kuntz

12 Conclusion and how to let it not become a nightmare!! Manage complexity by abstraction, separating viewpoints and focusing on important concerns be reminded that we cannot reduce complexity!! Use of sound methodologies and tools that support dealing with multi-concerns and their inter-dependencies! Establish and increase an understanding of Architecture Engineering! Further help from funded research projects:! Automotive, Railway, Avionic Multicore Systems ARAMiS! Software Platform Embedded Systems SPES 2020 and SPES xt 12 / S. Kuntz

13 Discussion Questions and Answers Thank you very much for your attention! 13 / S. Kuntz

14 Abbreviations and Acronyms ATESST AUTOSAR EAST-ADL EAST EEA ITEA MAENAD TADL TIMMO TIMMO-2-USE Advancing Traffic Efficiency and Safety Through Software Technology Automotive Open System Architecture Electronics Architecture and Software Technology - Architecture Description Language Electronics Architecture and Software Technology - Embedded Electronic Architecture Information Technology for European Advancement Model-based Analysis and Engineering of Novel Architectures for Dependable Electric Vehicles Timing Augmented Description Language Timing Model Timing Model to Use 14 / S. Kuntz

William Milam Ford Motor Co

Sharing technology for a stronger America Verification Challenges in Automotive Embedded Systems William Milam Ford Motor Co Chair USCAR CPS Task Force 10/20/2011 What is USCAR? The United States Council