SAFe Automotive aRchItecture SAFARI. SAFARI_Presentation_Short_v1.ppt 2 / /P. Cuenot/ 2009.09.03 © Continental AG ARTEMIS/Call2 R&D Project Proposal Project.

Slides:



Advertisements
Similar presentations
Cultural Heritage in REGional NETworks REGNET Quality Assurance – D14.
Advertisements

2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
Guaranteed Component Assembly with Round Trip Analysis for Energy Efficient High-integrity Multi-core Systems Artemis-AAL day 7 May, Budapest 1BME and.
System Integration Verification and Validation
DETAILED DESIGN, IMPLEMENTATIONA AND TESTING Instructor: Dr. Hany H. Ammar Dept. of Computer Science and Electrical Engineering, WVU.
Safe Automotive soFtware architEcture
Model based development for function safety Continental Automotive France Philippe CUENOT OFFIS Thomas PEIKENKAMP.
Kellan Hilscher. Definition Different perspectives on the components, behavioral specifications, and interactions that make up a software system Importance.
Software Project Management
Chapter 4 Quality Assurance in Context
ARCH-01: Introduction to the OpenEdge™ Reference Architecture Don Sorcinelli Applied Technology Group.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Stepan Potiyenko ISS Sr.SW Developer.
Software Configuration Management (SCM)
Trade Study Training Need and Goals Need Consistent methodologies and practices performing trade studies Pros/cons, advantages/disadvantages, customer/management.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
Software Quality Assurance For Software Engineering && Architecture and Design.
10th TTCN-3 User Conference, 7-9 June 2011, Bled, Slovenia AUTOSAR Conformance Tests - Feedback on their development and utilization Alain Feudjio-Vouffo,
Chapter 6– Artifacts of the process
S/W Project Management
Guide to the Software Engineering Body of Knowledge Chapter 1 - Introduction.
Introduction to Software Quality Assurance (SQA)
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
ITEA Common Workshop on automotive Tooling Prepared by the projects AMALTHEA, MAENAD, SAFE, TIMMO-2-USE 24 th and 25 th September 2012 in Berlin.
On the relation between software development and control function development in automotive embedded systems Stefan Kowalewski Embedded Software Laboratory.
Questions/Comments: Ed Smith VVSG and Requirements Management Ed Smith January 13, 2011.
ISO Tor Stålhane IDI / NTNU. What is ISO ISO 9001 was developed for the production industry but has a rather general structure ISO describes.
Requirements Analysis
RUP Implementation and Testing
ITEA International Workshop on Challenges in Methodology, Representation, and Tooling for Automotive Embedded Systems, Berlin 2012 Target Mapping.
Brussels, 1 June 2005 WP Strategic Objective Embedded Systems Tom Bo Clausen.
1 Configuration Management “The Cookbook Approach”
S Q A.
ESA/ESTEC, TEC-QQS August 8, 2005 SAS_05_ESA SW PA R&D_Winzer,Prades Slide 1 Software Product Assurance (PA) R&D Road mapping Activities ESA/ESTEC TEC-QQS.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
Intent Specification Intent Specification is used in SpecTRM
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
Model Checking and Model-Based Design Bruce H. Krogh Carnegie Mellon University.
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Testability of Analogue Macrocells Embedded in System-on-Chip Workshop on the Testing of High Resolution Mixed Signal Interfaces Held in conjunction with.
11/24/2015Dr. SASTRY-PROJ SOFTWARE PROJECT MANAGEMENT By Dr. M V S PERI SASTRY. B.E,Ph.D.
PRJ566 Project Planning & Management Software Architecture.
Value chain analysis general overview Some reminders Software has a high development cost But production cost almost nil Automotive software specifics.
Over View of CENELC Standards for Signalling Applications
Formal Specification: a Roadmap Axel van Lamsweerde published on ICSE (International Conference on Software Engineering) Jing Ai 10/28/2003.
ARTEMIS JU Grant Agreement number WP4 Instantiation WP4 Status 25 September, 2013.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
SAB Sponsor Progress Report Paul R. Croll Software and Systems Engineering Standards Committee (S2ESC) February 3, 2016.
Skills and products portfolio an overview Lorenzo Martinelli – Business Development Contact:
INCOSE IW 2012 MBSE Workshop Systems Modeling
Model-based design inspection based on traceability information models and design slicing Shiva Nejati April 15, 2015.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Interface Concepts Modeling Core Team
Role of The Software Development Plan (SDP)
Supportability Design Considerations
Chapter 24: Architecture Competence
A scalable approach for Test Automation in Vector CAST/Manage with
ITEA3 Project: ACOSAR Advanced Co-Simulation Open System Architecture
IEEE Std 1074: Standard for Software Lifecycle
Software Design Methodology
Challenges for the European Automotive Software Industry
Introduction to Software Testing
PSS verification and validation
System architecture, Def.
Functional Safety Solutions for Automotive
Presentation transcript:

SAFe Automotive aRchItecture SAFARI

SAFARI_Presentation_Short_v1.ppt 2 / /P. Cuenot/ © Continental AG ARTEMIS/Call2 R&D Project Proposal Project selection : Late October 2009 Project start : 1st of June 2010 for 3 years duration

SAFARI_Presentation_Short_v1.ppt 3 / /P. Cuenot/ © Continental AG Goals Scope : Automotive electronics architecture (system + software + electronic hardware including Electrical Distribution System) Improve dependability including safety focus of automotive products (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 Early evaluation of safety architecture and reuse (quality and cost driven) Demonstrate preservation of functional design choice (safety oriented) on component architecture Improve and standardized interface within automotive supply chain Interconnected to others Automotive R&D projects including CESAR R&D initiative as multi-domain platform

SAFARI_Presentation_Short_v1.ppt 4 / /P. Cuenot/ © Continental AG SAFARI Vision Definition of application rules for functional safety process application (ISO26262) Based on ADL language and methods capturing Functional and Technical Design (e.g. EAST-ADL2/SySML) complementing AUTOSAR hardware introduction job split (responsibilities) of involved parties Providing Model Based Techniques for safety evaluation Automatic extraction and synthesis of failure mode Fault injection methods (target virtual hardware platform) Verification of functional design choice (safety oriented) into component implementation HW and SW COTS safety characterization (matching AUTOSAR syntax) Generative approach for code and test generation Early evaluation of architecture choice based on safety and multi-criteria metrics Mastering and enforcing reuse to reach details satisfying safety case documentation

SAFARI_Presentation_Short_v1.ppt 5 / /P. Cuenot/ © Continental AG SAFARI WP structure WP1 : Requirement elicitation WP2: Safety Model Based WP4: Use case for Evaluation WP5 :Methodology and application rules WP6: Training, Dissemination Specifies Evaluates Feedbacks Analyzes Validates Adjusts Documents Standardizes System OEM / Tier1 Sub- System OEM / Tier1 Sub- System Tier1 / Supplier Use case Scenario ISO26262 Spec. State** of the art WP0: Management, Exploitation WP3: Technology Platform Integrated Platform** Specialized plug-in Realization Specifies Synchronizes **CESAR Link Meta-Model Implemen- -tation Safety goals Modeling Architecture Modeling Methods for Analysis Meta Model Variant Manag. Documents Safety code generation

SAFARI_Presentation_Short_v1.ppt 6 / /P. Cuenot/ © Continental AG SAFARI Results Open meta model for description of system, software (AUTOSAR IPR), hardware Technology Platform defined as reference for platform set-up Training Material for the reference platform Industrial use cases (confidentiality respect) managed with concurrent engineering (OEMs, Tier1, silicon supplier) demonstrating methods and tools results Assessment process to demonstrate compliance to ISO26262 (validated by accreditation body) Recommendation and guidelines for System decomposition for effective design of safety mechanism Compliance with architecture constraints and safety mechanism with supervisor architecture AUTOSAR platform configuration for safety Inclusion of COTS in a safety system developed according to the standard

SAFARI_Presentation_Short_v1.ppt 7 / /P. Cuenot/ © Continental AG SAFARI link to AUTOSAR R4.0 will include safety mechanism and documentation report (Released on Dec. 2009) SAFARI provides Set up link to ISO26262 and engineering processes Provide complete overview on system level Complement hardware description SAFARI evaluates AUTOSAR results for AUTOSAR platform configuration for safety application Safety test conformance for component Process compliance with safety standard