We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byNora Venis
Modified over 2 years ago
SAFe Automotive aRchItecture SAFARI
SAFARI_Presentation_Short_v1.ppt 2 / /P. Cuenot/ 2009.09.03 © 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/ 2009.09.03 © 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/ 2009.09.03 © 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/ 2009.09.03 © 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/ 2009.09.03 © 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/ 2009.09.03 © 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
Safe Automotive soFtware architEcture (SAFE) Project Presentation SAFE project partners.
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.
Guaranteed Component Assembly with Round Trip Analysis for Energy Efficient High-integrity Multi-core Systems Artemis-AAL day 7 May, Budapest 1BME and.
9/7/20151 Compiled by Arthur Alexander Reyes. Introduction to Software Quality Assurance (SQA)
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
Value chain analysis general overview Some reminders Software has a high development cost But production cost almost nil Automotive software specifics.
Skills and products portfolio an overview Lorenzo Martinelli – Business Development Contact:
© 2012 xtUML.org Bill Chown – Mentor Graphics Model Driven Engineering.
On the relation between software development and control function development in automotive embedded systems Stefan Kowalewski Embedded Software Laboratory.
Model Checking and Model-Based Design Bruce H. Krogh Carnegie Mellon University.
Model based development for function safety Continental Automotive France Philippe CUENOT OFFIS Thomas PEIKENKAMP.
10th TTCN-3 User Conference, 7-9 June 2011, Bled, Slovenia AUTOSAR Conformance Tests - Feedback on their development and utilization Alain Feudjio-Vouffo,
CENELEC STANDARDS and its Application on Indian Railways for Signalling Alok Katiyar Dir/RDSO.
2009 – E. Félix Security DSL Toward model-based security engineering: developing a security analysis DSML Véronique Normand, Edith Félix, Thales Research.
Decisive Themes, July, JL-1 ARTEMIS Decisive Theme for Integrasys Pedro A. Ruiz Integrasys July, 2011.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
SE513 Software Quality Assurance Lecture12: Software Reliability and Quality Management Standards.
PRJ566 Project Planning & Management Software Architecture.
System Integration Verification and Validation. Remember V-Cycle for all Increments? SW Requirements SW Architecture SW Design SW Coding SW Module Test.
Intent Specification Intent Specification is used in SpecTRM
S Q A. What is "Quality"? "Quality of Design" and "Quality of Conformance" -- Roger Pressman User Satisfaction = compliant product + good quality + delivery.
Questions/Comments: Ed Smith VVSG and Requirements Management Ed Smith January 13, 2011.
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.
ITEA International Workshop on Challenges in Methodology, Representation, and Tooling for Automotive Embedded Systems, Berlin 2012 Target Mapping.
SAB Sponsor Progress Report Paul R. Croll Software and Systems Engineering Standards Committee (S2ESC) February 3, 2016.
Security Engineering II. Problem Sources 1.Requirements definitions, omissions, and mistakes 2.System design flaws 3.Hardware implementation flaws, such.
Chapter 4 Quality Assurance in Context SE Software Testing and Quality Assurance 1.
Cultural Heritage in REGional NETworks REGNET Quality Assurance – D14.
Requirements Engineering n Elicit requirements from customer Information and control needs, product function and behavior, overall product performance,
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Lecture 7: Requirements Engineering. Waterfall Model.
Testability of Analogue Macrocells Embedded in System-on-Chip Workshop on the Testing of High Resolution Mixed Signal Interfaces Held in conjunction with.
Bernd Bruegge & Allen H. Dutoit Object-Oriented Software Engineering: Using UML, Patterns, and Java 1 Introduction to Software Engineering CEN 4010.
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.
Lecture-3 Software Development Life Cycle (SDLC) Thepul Ginige.
CEN 5076 Software Testing Instructor: Peter Clarke Fall 2005.
1 IEEE/EIA – 1996 “Software Life Cycle Processes” National Defense Industrial Association (NDIA) Presents.
ARCH-01: Introduction to the OpenEdge™ Reference Architecture Don Sorcinelli Applied Technology Group.
Guide to the Software Engineering Body of Knowledge Chapter 1 - Introduction.
Stages of design High level design High level data structure Architecture Low level design-code design Algorithms Low level data structures.
Overview of Formal Methods. Topics Introduction and terminology FM and Software Engineering Applications of FM Propositional and Predicate Logic Program.
Chapter 10 Analysis and Design Discipline. 2 Purpose The purpose is to translate the requirements into a specification that describes how to implement.
No: 1 CEMSIS wp6_beg037_v0_2_fisa 2003 slides.ppt CEMSIS FIKS-CT Cost-Effective Modernisation of Systems Important to Safety Deryk Pavey, Deryk.
DITSCAP Phase 2 - Verification Pramod Jampala Christopher Swenson.
SOFTWARE DEVELOPMENT PROCESS PRACTICAL ASPECTS Information Software Systems ISS Modern SW Development Practices: Processes and Technologies 18 May 2007.
ESA UNCLASSIFIED – For Official Use ISVV Effectiveness Measurement in ESA Space Projects Pedro A. Barrios, Maria Hernek, Marek Prochazka European Space.
Example of practice content Practice content is organized into sections: Enterprise Systems development Software development Delivery processes detail.
™ ™ © 2006, KDM Analytics Software Assurance Ecosystem and its Applications Djenana Campara Chief Executive Officer, KDM Analytics Board Director, Object.
Software Configuration Management (SCM) ä Overview ä What is SCM? ä What are the processes of SCM? ä How does each process do? ä Summary.
© 2017 SlidePlayer.com Inc. All rights reserved.