1 / 36

nSafeCer WP500 Ramp-up Automotive and Construction Equipment Demonstrators

nSafeCer WP500 Ramp-up Automotive and Construction Equipment Demonstrators Riga, nSafeCer-Workshop, Day3, 27-09-2013, 13:30h – 14:50h. Helmut Martin, V iF, WP500 leader Roland Mader, AVL, WP520 leader. Jonny Vinter, SP, WP540 leader Ulf Olsson, VCE, WP550 leader. Agenda.

hunter-everett
Download Presentation

nSafeCer WP500 Ramp-up Automotive and Construction Equipment Demonstrators

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. nSafeCer WP500Ramp-up Automotive and Construction Equipment Demonstrators Riga, nSafeCer-Workshop, Day3, 27-09-2013, 13:30h – 14:50h Helmut Martin, ViF, WP500 leader Roland Mader, AVL, WP520 leader Jonny Vinter, SP, WP540 leader Ulf Olsson, VCE, WP550 leader

  2. Agenda • Introduction of AT & CE Demonstrators • HEV Powertrain Use Case • AUTOSAR BSW Use Case • Construction Equipment Evaluation • Open Discussion

  3. Agenda • Introduction of AT & CE Demonstrators • HEV Powertrain Use Case • AUTOSAR BSW Use Case • Construction Equipment Evaluation • Open Discussion

  4. Introduction of AT & CE Demonstrators (1/4) • Overview of use cases: • HEV Powertrain Use Case (AVL/ViF) • BSW Module Use Case (SP) • Construction Equipment Evaluation (VCE) • Introduction of CE together with AT • Best practices concerning similarities with automotive systems • Distributed development requires aligned processes • Cover CE domain specifics • Use cases provides different aspects of the safety life cycle

  5. Introduction of AT & CE Demonstrators (2/4) • Each demonstrator covers different use case scenarios of SafeCer’s methods and tools

  6. Introduction of AT & CE Demonstrators (3/4) • Evaluation plan over SafeCer project • Intermediate evaluation of achievements • Presenting and discussing demonstrator results • Synchronisation points with other WPs • methods, tools, other demonstrators

  7. Introduction of AT & CE Demonstrators (4/4) • Evaluation of Use Case Results • Coverage of requirements and maturity of demonstrator use cases • Each demonstrator covers specific number of SafeCer requirements • Evaluation of requirements at intermediate milestones and project end • Number of … • Publications at scientific and industrial conferences • Contributions to scientific or industrial workshops • Completed diploma or master thesis DM3 DM4 DM5

  8. Agenda • Introduction of AT & CE Demonstrators • HEV Powertrain Use Case • AUTOSAR BSW Use Case • Construction Equipment Evaluation • Open Discussion

  9. HEV Powertrain Use Case - Background • Advanced features • Fuel economy or drivability • Faults and failures • Hazards • Cause harm • Safety-relevant: ISO 26262 • Safety arguing • Tool qualification • Safety analyses • Model-based safety engineering EMS…Engine Management System CCU…Clutch Control Unit HCU…Hybrid Control Unit TCU…Transmission Control Unit MCU…Motor Control Unit BMS…Battery Management System

  10. HEV Powertrain Use Case - Status • IN REVIEW • Specification • Conception and Specification of Use Case PMTC – Review • D501.1  D521.1 • Relase planned nSCM18 (09/2013) • Methods • Safety Modeling – First experiences in SysML modeling • Safety Analysis – Concept Phase work in progress • Tool Integration in CTF&CAR • MDS: Meta X integrated in CTF&CAR • CEA List: Diversity integrated in CTF&CAR • ARTIMon • Evaluation of demonstrator • First preliminary evaluation planned for nSC M19 (10/2013) • FINISHED • IN REVIEW • WORKING • WORKING • WORKING • WORKING

  11. HEV Powertrain Use Case - Tool: MetaX • IN REVIEW • MDS MetaX mapping tool • Supports traceability • Between heterogeneous fragments of information • Over different tools • Semantics relationships • Change impact analysis • Refined precision (fragments) • Identify impacted elements • Guarantee consistency between coupled structured hierarchical elements • FINISHED • WORKING

  12. HEV Powertrain Use Case - Tool: MetaX • IN REVIEW • MDS MetaX mapping tool • Supports traceability • Between heterogeneous fragments of information • Over different tools • Semantics relationships • Change impact analysis • Refined precision (fragments) • Identify impacted elements • Guarantee consistency between coupled structured hierarchical elements • FINISHED • WORKING

  13. HEV Powertrain Use Case - Tool: MetaX • Mapping of design elements • Declaration and formalization of the existing relationships between fragments of artifacts involved in the development (requirements, specifications, models, source code, etc.). • Forward and backward traceability • Static safety analysis, e.g. coverage and consistency checks, by exploiting the traceability links declared between artifacts. • Change impact analysis • Assessment of the impacts implied by a given modification of an artifact at any level of the flow. • Interfacing to requirements management tools • Support of the Requirement Interchange Format (ReqIF) standard in order to interface with widespread requirements management tools

  14. HEV Powertrain Use Case - Tool: ARTImon • IN REVIEW • Analyses a flow of dated observations in order to detecthazardsexpressed in formal entry language • A flow maybeobtainedfrom: • instrumentation of a physicalobject • simulation of a model • execution of a code • Useful for: • design process of complexsystems, • models validation, • systemstesting. • Used in embedded component for control or diagnostic. • Operates in continuous time or in logical time mode • No limitation about the length of flow (memory isbounded & predictable) • FINISHED • WORKING

  15. HEV Powertrain Use Case - Tool: Safety Ext. • IN REVIEW • AVL Safety Extensions as Addin for Enterprise Architect 9.3 • Specific language enhancement of SysML1.1 – AVL Meta Model • Meta Model and Addin Features support: • Item Definition • Hazard Analysis & Risk Assessment • Functional Safety Concept • Technical Safety Concept • Interface to Requirement Management System • FINISHED • WORKING

  16. HEV Powertrain Use Case - CTF & CAR usage Which tools are used? First experience by tool support • MetaX (MDS) • First Functional Prototype is available • Integration in CTF & CAR under investigation • ARTiMon(CEA) • CTF: ARTiMonplugged to any simulator or running device; •  producing a trace and check real time orientedproperties • CAR: ARTiMonis a C librarywith a simple API (refresh variable values 6 time) •  No input format isstriclyimposed •  wrapper/driver/parser has to bedeveloped for each format/environment • Safety Extension (AVL) • Integration in CTF and CAR as a futureperspective • Atfirstintegrationatconceptuallevelaspired • Restrictions of Enterprise Architect need to be considered • Potential ofintegration still underevaluation

  17. HEV Powertrain Use Case - Open issues Discuss of open issues demonstrator work or any possible improvements in each demonstrator or in the project wide cooperation • MDS MetaX: • Provide traceability information to the CAR ? (TBC) • Interface with CTF ? (TBC) • AVL Safety Extension: • Integration in CTF and CAR as a futureperspective (TBC) • ViF - Integration of other supporting tools to CTF and CAR? • E.g. Enterprise Architect or APIS IQ FMEA

  18. Agenda • Introduction of AT & CE Demonstrators • HEV Powertrain Use Case • AUTOSAR BSW Use Case • Construction Equipment Evaluation • Open Discussion

  19. Background of AUTOSAR BSW module Use Case • There are four task identified in the use case • One task is completely allocated to Akhela • The other three are incremental in nature, i.e. the tools, methods and results are reused in the next task. • Therefore we can concentrate on “Validity of safety certification when moving BSW to different contexts” (first task) to ascertain status.

  20. Status of AUTOSAR BSW module Use Case • “Validity of safety certification when moving BSW to different contexts” contains • Tool used and developed is SaftyADD • Eclipse plugin attaches currently empty safety contract container to source code. • Method used is Safety Contracts from component model • Currently main focus, investigating the appearance, rules and content of the safety contract container • BSW module to be analyzed is AUTOSAR diagnostics • Source code candidate identified

  21. Status of SafetyADD tool AUTOSAR BSW module Use Case • Schematic view of SafetyADD Focus now is on formulation of the rule set governing the automatic compliance check of assume and guarantee to be implemented in the tool SafetyADD

  22. Status of SafetyADD tool AUTOSAR BSW module Use Case • SafetyADD When the development and testing of a SWC is done, it is time to export the software component for possible reuse at a later time. (stored in CAR) This is a view of the general properties of the SWC that can be edited

  23. Status of tool AUTOSAR BSW module Use Case (Akhela) Akhela uses Parasoft C++ Test that supports some default standard coding rules (i.e. MISRA C or C++) And also map AUTOSAR BSW requirements mapped onto ISO26262, with custom made rules for checking

  24. CTF & CAR useage in AUTOSAR BSW module Use Case • CTF interaction minimal, launchable from platform only. • CAR will hopefully enable storage and traceability of the certification artifacts and their dependencies. • The SafetyADD tool relates each software component to a component certificate via a contract; these contracts are in in the form of rules implemented in XML format not yet integrated in CAR.

  25. Open issues of AUTOSAR BSW module Use Case • How and when will Safety Contracts be integrated in CAR • A wider cooperation/discussion of practical usage of Safety Contracts

  26. Agenda • Introduction of AT & CE Demonstrators • HEV Powertrain Use Case • AUTOSAR BSW Use Case • Construction Equipment Evaluation • Open Discussion

  27. Status of Volvo CE Use Case - Background • The Volvo CE Use case consists of four incremental parts • Product development according to ISO 26262 process following • Concept Phase • Product development at System level • Product development at Hardware level • Product development at Software level • Development of a Component model concept including Safety Contracts and Safety Element out of Context • Development of a Product line concept on top of the Component model

  28. Status of Volvo CE Use Case – Current Status • The Volvo CE Use case consists of four incremental parts • Product development according to ISO 26262 process following • Concept Phase • Product development at System level • Product development at Hardware level • Product development at Software level • Development of a Component model concept including Safety Contracts and Safety Element out of Context • Development of a Product line concept on top of the Component model Ended Q2 2013 Ending Q3 2013 Background task (Q3) Starting

  29. CTF & CAR useage in Volvo CE Use Case • Tools • MoMuT • WEFACT

  30. Open issues of Volvo CE Use Case • Process model • Activity patterns

  31. Open issues of Volvo CE Use Case • Component model • Different levels and languages • SYSML • UML • Simulink • Safety Contracts SYSML/UML UML UML/Simulink

  32. Open issues of Volvo CE Use Case • Tools • MoMuT • WEFACT

  33. Open issues of Volvo CE Use Case • Feature model, Component model and Patterns

  34. Agenda • Introduction of AT & CE Demonstrators • HEV Powertrain Use Case • AUTOSAR BSW Use Case • Construction Equipment Evaluation • Open Discussion

  35. Open discussion for AT & CE demonstration • Any improvements of cooperation across WPs? • Technology and Process providers WP100? • Tool-providers WP200? • Other demonstrator use case WP300/400/500/600? • Application of SafeCer methods and tools • Share experience by using CTF&CAR • Evaluation of results

More Related