Safe Automotive software architecture (SAFE)

Transcription

1 Safe Automotive software architecture (SAFE) , ARTEMIS Technology Conference 2012 Stefan Voget Continental Automotive

2 Content Motivation Project Organization Work Packages Approach for Interoperability

3 SAFE Motivation Scope and Goals Scope: Automotive electronics architecture (system + software + electronic hardware including electrical distribution system) Goals: Improve dependability from vehicle to component Ensure process compliance to ISO26262 at the best cost (automation required, and no over design) matching AUTOSAR requirements methods to reference supplier chain job split, liability and to respect intellectual property rights Early evaluation of safety architecture and reuse (quality and cost driven) Demonstrate preservation of functional design choice (safety oriented) on component architecture

4 SAFE Motivation Approach ISO26262 Requirements Developer Modelling Language Interoperable Toolset Guidelines, Application Rules HW-SW Component Models

5 SAFE Motivation Results Open meta model for description of system, software, hardware Technology Platform Training Material Industrial use cases demonstrating methods and tools Assessment process to demonstrate compliance to ISO26262 Recommendation and Guidelines for System decomposition for effective design of safety mechanism Compliance with architecture constraints and safety mechanism AUTOSAR platform configuration for safety Inclusion of COTS in a safety system

6 Content Motivation Project Organization Work Packages Approach for Interoperability

7 SAFE Project Organization Basic Data Duration: 36 months Timing: Partners: 18 Countries: Austria, France, Germany Budget: 12 M Coordinator: Dr. Stefan Voget, Continental Automotive (G)

8 SAFE Project Organization Consortium OEMs BMW-CarIT (G) Tiers1 Continental Automotive (G) Continental Automotive (Fr) Continental Teves (G) Valeo EEM(Fr) ZF (G) Silicon Supplier Infineon Technologies (G) Tool suppliers & SME Aquintos (G) AVL (G) Dassault Systems (Fr) ITEMIS France (Fr) Pure Systems (G) TTTEch (Aut) Accreditation body TÜV NORD Mobilität (G) Academia Fortiss (G) FZI, Karlsruhe University (Ge) OFFIS (Ge) LaBRi, Bordeaux University (Fr)

9 SAFE Project Organization Work-Package Structure WP1: Project Management, Exploitation WP2: Requirement Elicitation WP3: Model Based Development for Functional Safety WP4: Technology Platform WP6: Methodology & Application Rules Modelling Language Interoperable Toolset Guidelines, Application Rules WP5: Evaluation Scenarios WP7: Training, Dissemination

10 Content Motivation Project Organization Work Packages WP2 Requirements Elicitation WP3 Model Based Development for Functional Safety WP4 Technology Platform WP5 Evaluation Scenarios WP6 Methodology & Application Rules Approach for Interoperability

11 SAFE WP 2 Requirements Elicitation ISO26262 Requirements on model based development > 500 requirements Filter: Project Targets State of the art Parallel projects to cooperate with Use Cases Exemplarily industrial use cases available > 60 requirements SAFE Project Requirements

12 SAFE WP 3 Model based dev. for Functional Safety Safety goals modelling Hazard analysis, safety goals and ASIL def. Safety Requirement Expression Safety case documentation Architecture modelling System and Software models enhancement Hardware Description COTS evaluation Methods for analysis Failure and cut-sets analysis Safety evaluation safety and multi-criteria architecture benchmarking Variant Management Safety code generation Modelling Language Interoperable Toolset Guidelines, Application Rules Implemented in Meta Model Definition Approach: base technologies are used and extended ReqIF EAST-ADL AUTOSAR IP-XACT

13 SAFE WP 4 Technology Platform Modelling Language Specialized Plugins Traceability and requirement import Failure and cutset analysis Behavioural translator Variability seamless integration Safety and multi-criteria architecture benchmarking Safety code generator Platform Software platform for mixed criticality Tool Interfacing Interoperable Toolset Guidelines, Application Rules PREEVISION extension Metamodel implementation

14 SAFE WP 6 Methodology & Application Rules Objectives Tackle the introduction of a comprehensive functional safety process according to ISO26262 to a real engineering team Modelling Language Interoperable Toolset Guidelines, Application Rules Assessment procedure for functional safety Process step and adequate measures to allow seamless implementation in the different engineering disciplines

15 SAFE WP 5 Evaluation Scenarios Project Targets Tier1 s perspective (egas & Electrical Brake) Mixed criticality software layer safety analysis of a system with MCU and MCAL SAFE Requirements (WP2) Definition of assessment criteria loop safety analysis at high level Requirements on WP 3/4/6 Evaluation Scenarios (WP5) safety code generation WP 3/4/6 results

16 Content Motivation Project Organization Work Packages Approach for Interoperability

17 Approach for Interoperability Preliminary Package Structure Process Validation System Configuration Requirements Hardware Software Hazards Dysfunctional References Analysis

18 Approach for Interoperability Use meta-model backbone for SAFE SAFE Technology Platform USES Req-IF MM: OMG Toolplatform: Eclipse RMF project MM: SAFE project USES EAST-ADL MM: EAST-ADL Association Toolplatform: EATOP (TBD.) Toolplatform: SAFE project & Eclipse A-IWG USES USES AUTOSAR MM: AUTOSAR Toolplatform: ARTOP IP-XACT MM: IEEE Toolplatform: XMLSchema, Eclipse Editor

19 Approach for Interoperability EAST-ADL A System Modeling Approach that is a template for how engineering information is organized and represented provides separation of concerns embrace the de-facto representation of automotive software AUTOSAR Feature content Vehicle Level Analysis Level Design Level Implementation Level Operational Level Abstract functional architecture Functional architecture, HW architecture, platform abstractions AUTOSAR Software architecture Embedded system in produced vehicle

20 Approach for Interoperability EAST-ADL Focus on functional objectives and not technological solutions Realization by high level architectural elements without notion of HW Vehicle Level Analysis Level Design Level Implementation Level Operational Level Introducing HW & SW in architecture Implementation of SW/HW A Perfect Match!

21 Approach for Interoperability EATOP (EAST-ADL Tool Platform) In preparation - Comming soon EAST-ADL Model Extender EATOP EAST-ADL Meta Model Implementation ARTOP (AUTOSAR Tool Platform) Serialization Abstraction level M2M EAST-ADL Explorer Validation User Group that implements the AUTOSAR meta-model in an Eclipse based platform. EAST-ADL Editor Tool Adapters SPHINX Eclipse

22 Approach for Interoperability Usage of CESAR Association Modelling Language Interoperable Toolset EAST-ADL MM CMM RTP Guidelines, Application Rules EATOP Eclipse

23 Thank you for your attention This document is based on the SAFE project in the framework of the ITEA2, EUREKA cluster program Σ! The work has been funded by the German Ministry for Education and Research (BMBF) under the funding ID 01IS11019, and by the French Ministry of the Economy and Finance (DGCIS). The responsibility for the content rests with the authors.