development of functional safe systems using preevision€¦ · system, service and software design...

52
V1 | 2018-06-26 Webinar, 2018-11-07 Development of Functional Safe Systems using PREEvision

Upload: others

Post on 04-Oct-2020

6 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

V1 | 2018-06-26

Webinar, 2018-11-07

Development of Functional Safe Systems using PREEvision

Page 2: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

2

u PREEvision at a Glance

Introduction Functional Safety

PREEvision for Functional Safety

Summary

Agenda

Page 3: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

3

Supported Use Cases

PREEvision at a Glance

E/E BackboneCollaboration Platform

File Management

Design of SafetyRelevant Systems

Product LineEngineering

ArchitectureDesign

RequirementsEngineering

Wiring HarnessDesign

AUTOSARSystem, Service and Software

Design

Communication Design(AUTOSAR and Legacy Formats)

Hardware ComponentDevelopment

Function-Driven Design

System Design

Test DataManagement

Page 4: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

4

Overview

PREEvision at a Glance

M

M

M

M

Page 5: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

5

PREEvision at a Glance

u Introduction Functional Safety

PREEvision for Functional Safety

Summary

Agenda

Page 6: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

6

Challenges

Introduction Functional Safety

Airbag

Delayed deployment after crash detection

ESP

Unintended, single-sided brake effect on straight lane

Electronic Park Brake

Unintended activation in motion

Collision Avoidance

Acceleration instead of deceleration in traffic

Reality or science fiction – Is such a scenario realistic?

Page 7: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

7

Challenges

Introduction Functional Safety

Core

Part

s

ISO 26262:2011-2012Road vehicles - Functional safety

Source: [ISO26262, 10-Fig.1]

ISO 26262

Complex standard Risk of overheads and costs if applied ad hoc

u 10 Parts

u 43 Chapters

u100 Work products

u180 Engineering methods

u500 Pages

u600 Requirements

Page 8: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

8

ISO 26262 key deliverables have impact on all process areas

Challenges

Introduction Functional Safety

SystemReq. Analysis

ComponentTest

SystemDesign

ComponentReq. Analysis

ComponentImplementation

SystemIntegration

ComponentIntegration

ComponentDesign

SystemTest

Item Definition

Hazard and Risk Analysis

FunctionalSafety Concept

QualitativeSafety Analyses

QuantitativeSafety Analyses

Validation

Safety Case

Verification

TechnicalSafety Concept

HSI Specification

DIASafety Plan

Page 9: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

9

High cost for ISO 26262 compliant work products

Challenges

Introduction Functional Safety

u Data for work products fragmented across legacy tools and documents

u System responsible, safety managers and engineers have to struggle withmultiple mostly inconsistent sources for producing the work products

u Maintaining traceability and consistency is inefficient, error prone anda source for quality and compliance problems

Verification

Safety Plan

FTA

HARAHW Analysis

Safety caseRequirements

Function / HW / SW Design

FMEA

Page 10: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

10

PREEvision at a Glance

Introduction Functional Safety

u PREEvision for Functional Safety

Summary

Agenda

Page 11: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

11

Integrated Model Based System Engineering Platform

PREEvision for Functional Safety

Safety Plan

Requirements Management

System / Function / HW /

SW Design

Test Management

Change Management

Safety Analysis Methods

Cost efficient consistency and traceability

Page 12: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

12

ISO 26262 key areas supported by PREEvision

PREEvision for Functional Safety

SystemReq. Analysis

ComponentTest

SystemDesign

ComponentReq. Analysis

ComponentImplementation

SystemIntegration

ComponentIntegration

ComponentDesign

SystemTest

Item Definition

Hazard and Risk Analysis

FunctionalSafety Concept

QualitativeSafety Analyses

QuantitativeSafety Analyses

Validation

Safety Case

Verification

TechnicalSafety Concept

HSI Specification

DIASafety Plan

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 13: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

13

Item Definition

PREEvision for Functional Safety

Artifacts modeled in PREEvision:

u Feature specifications, functional and non-functional requirements

u Operating scenarios and operating modes

u Logical and topological system architecture including allocation of functions

u Dependencies with other systems

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Item Definition

Page 14: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

14

ISO 26262 key areas supported by PREEvision

PREEvision for Functional Safety

SystemReq. Analysis

ComponentTest

SystemDesign

ComponentReq. Analysis

ComponentImplementation

SystemIntegration

ComponentIntegration

ComponentDesign

SystemTest

Item Definition

Hazard and Risk Analysis

FunctionalSafety Concept

QualitativeSafety Analyses

QuantitativeSafety Analyses

Validation

Safety Case

Verification

TechnicalSafety Concept

HSI Specification

DIASafety Plan

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 15: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

15

u HAZOP is a qualitative analysis method tosystematically identify malfunctions for a system

u The malfunctions can be used in a following Hazard and Risk Analysis (HARA)to derive and classify hazardous events

u The malfunctions are identified based on defined guide words

u PREEvision supports HAZOPs with the HAZOP editor

u The following artifacts can be used as HAZOP items:logical functions, customer features, requirements

HAZard and OPerability Study (HAZOP) Editor

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Hazard and Risk Analysis

Page 16: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

16

u Pick functions and malfunctions from catalogues

u Pick operating scenarios and operating modes from catalogues

u Automatic calculation of Automotive Safety Integrity Level (ASIL) of hazardous events and derived safety goals

u Highlighting based on ASIL classification

u Create and link safety goals directly in table

u Set Safe State of Safety Goal

u Consistency checks and highlightinge.g. check ASIL classification of Hazardous Event against Safety Goal

Hazard Analysis and Risk Assessment (HARA) Editor

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Hazard and Risk Analysis

Page 17: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

17

ISO 26262 key areas supported by PREEvision

PREEvision for Functional Safety

SystemReq. Analysis

ComponentTest

SystemDesign

ComponentReq. Analysis

ComponentImplementation

SystemIntegration

ComponentIntegration

ComponentDesign

SystemTest

Item Definition

Hazard and Risk Analysis

FunctionalSafety Concept

QualitativeSafety Analyses

QuantitativeSafety Analyses

Validation

Safety Case

Verification

TechnicalSafety Concept

HSI Specification

DIASafety Plan

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 18: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

18

u Support detailing safety goals via

u Refinement

u Decomposition

u Prevent errors and inconsistencies

u Trace tables with automatic validation of ASIL decomposition

u Increase efficiency and reduce manual efforts

u Automatically create valid decompositions of Safety Goals, Functional Safety Requirements and Technical Safety Requirements via metrics

Functional Safety Concept (FSC) - Requirements

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

FunctionalSafety Concept

Page 19: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

19

Functional Safety Concept (FSC) - High Level

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

FunctionalSafety Concept

Page 20: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

20

Functional Safety Concept (FSC) – Detailed Level

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

FunctionalSafety Concept

Page 21: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

21

u Tabular trace views visualize the allocation offunctional safety requirements to the preliminary architecture elements

Functional Safety Concept (FSC) - Requirements Allocation

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

FunctionalSafety Concept

Page 22: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

22

u ISO 26262 compliant report forFunctional Safety Concept (FSC)

u Automatically generatedfrom model data

u Report template can be adapted to fit to company specific requirements

Functional Safety Concept (FSC) - Report

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

FunctionalSafety Concept

Page 23: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

23

ISO 26262 key areas supported by PREEvision

PREEvision for Functional Safety

SystemReq. Analysis

ComponentTest

SystemDesign

ComponentReq. Analysis

ComponentImplementation

SystemIntegration

ComponentIntegration

ComponentDesign

SystemTest

Item Definition

Hazard and Risk Analysis

FunctionalSafety Concept

QualitativeSafety Analyses

QuantitativeSafety Analyses

Validation

Safety Case

Verification

TechnicalSafety Concept

HSI Specification

DIASafety Plan

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 24: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

24

Technical Safety Concept (TSC) – Hardware – High Level

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

TechnicalSafety Concept

u HW elements can be modeled and associated withtechnical safety requirements, faults and safety mechanisms

u Powerful library concept for faults and safety mechanisms

1) Example Based on ISO 26262 – 5, Annex D.1

Page 25: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

25

Technical Safety Concept (TSC) – Hardware – Detailed Level

PREEvision for Functional Safety

1)Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

TechnicalSafety Concept

u HW elements can be modeled and associated withtechnical safety requirements, faults and safety mechanisms

u Powerful library concept for faults and safety mechanisms

u HW safety design can be detailed down to the device level

1) Example Based on ISO 26262 – 5, Annex E.1

Page 26: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

26

u SW safety design, technical safety requirements (TSR), faults and safety mechanisms (SM)can be detailed down to ports, interfaces and data elements

u AUTOSAR Import / Export of SW Architecture

Technical Safety Concept (TSC) – Software – Detailed Level

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

TechnicalSafety Concept

Page 27: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

27

u Tabular trace views visualize the allocation ofTechnical Safety Requirements (TSR) to the technical architecture elements

Technical Safety Concept (TSC) – Trace Editor

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

TechnicalSafety Concept

Page 28: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

28

ISO 26262 key areas supported by PREEvision

PREEvision for Functional Safety

SystemReq. Analysis

ComponentTest

SystemDesign

ComponentReq. Analysis

ComponentImplementation

SystemIntegration

ComponentIntegration

ComponentDesign

SystemTest

Item Definition

Hazard and Risk Analysis

FunctionalSafety Concept

QualitativeSafety Analyses

QuantitativeSafety Analyses

Validation

Safety Case

Verification

TechnicalSafety Concept

HSI Specification

DIASafety Plan

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 29: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

29

u Efficiently specify HSI via HSI Editor

u Create HSI-Requirements directly in Editor

u Pick HW/SW Elements in Editor from existing Architecture

u Efficiently generate HSI Specification

u Work Product required byISO 26262-4/5/6

Hardware-Software Interface (HSI) Specification

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

HSI Specification

See ISO 26262 – 4, Annex B

Page 30: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

30

ISO 26262 key areas supported by PREEvision

PREEvision for Functional Safety

SystemReq. Analysis

ComponentTest

SystemDesign

ComponentReq. Analysis

ComponentImplementation

SystemIntegration

ComponentIntegration

ComponentDesign

SystemTest

Item Definition

Hazard and Risk Analysis

FunctionalSafety Concept

QualitativeSafety Analyses

QuantitativeSafety Analyses

Validation

Safety Case

Verification

TechnicalSafety Concept

HSI Specification

DIASafety Plan

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 31: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

31

u Analysis leads to FMEA issues which can lead to new requirements or solutions

Failure Mode and Effects Analysis (FMEA)

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

QualitativeSafety Analyses

u Use technical architecture to derive FMEA Parts

Page 32: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

32

u Modeling of fault trees in malfunction diagrams

u Calculation of minimal cut sets

Qualitative Fault Tree Analysis (FTA)

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

QualitativeSafety Analyses

Page 33: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

33

u Typical relevant information for analysis can be easily added to fault trees via diagram tables

u Visibility can be controlled via diagram filters

Qualitative Fault Tree Analysis (FTA)

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

QualitativeSafety Analyses

Page 34: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

34

u Efficient, redundancy free modelling of fault tree alternatives

u Alternatives of fault trees can be easily switched and visualized

u The only tool which supports analysis on alternatives of fault trees

Qualitative Fault Tree Analysis (FTA)

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

QualitativeSafety Analyses

Page 35: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

35

ISO 26262 key areas supported by PREEvision

PREEvision for Functional Safety

SystemReq. Analysis

ComponentTest

SystemDesign

ComponentReq. Analysis

ComponentImplementation

SystemIntegration

ComponentIntegration

ComponentDesign

SystemTest

Item Definition

Hazard and Risk Analysis

FunctionalSafety Concept

QualitativeSafety Analyses

QuantitativeSafety Analyses

Validation

Safety Case

Verification

TechnicalSafety Concept

HSI Specification

DIASafety Plan

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 36: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

36

u Modeling of fault trees in malfunction diagrams

u Calculation of minimal cut sets (with order and quantitative importance)

u Calculation of probabilities

Quantitative Fault Tree Analysis (FTA)

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

QuantitativeSafety Analyses

Page 37: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

37

u Build failure mode library by convenient annotation of all HW library elements

u Dedicated Failure Mode Library Editor for high usability and efficiency

Hardware Architectural Metrics: Failure Mode Library

PREEvision for Functional Safety

Build / Edit Failure Mode

Library

Design Hardware Architecture

Perform Analysis with HW

ArchitecturalMetrics

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 38: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

38

u Use library elements during HW design as usual

u Increased efficiency by reusing failure mode definitions for design from library

Hardware Architectural Metrics: Using library elements

PREEvision for Functional Safety

Build / Edit FailureMode Library

Design Hardware Architecture

Perform Analysis with HW

ArchitecturalMetrics

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

1) Example Based on ISO 26262 – 5, Annex E.1

Page 39: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

39

u Allocate target values via D&D

u Assign safety mechanisms via D&D

u Convenient HW architectural metrics calculator

u Instant highlighting of fulfillments and violations

Hardware Architectural Metrics

PREEvision for Functional Safety

Build / Edit Failure Mode Library

Design Hardware Architecture

Perform Analysis with HW

Architectural Metrics

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 40: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

40

ISO 26262 key areas supported by PREEvision

PREEvision for Functional Safety

SystemReq. Analysis

ComponentTest

SystemDesign

ComponentReq. Analysis

ComponentImplementation

SystemIntegration

ComponentIntegration

ComponentDesign

SystemTest

Item Definition

Hazard and Risk Analysis

FunctionalSafety Concept

QualitativeSafety Analyses

QuantitativeSafety Analyses

Validation

Safety Case

Verification

TechnicalSafety Concept

HSI Specification

DIASafety Plan

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 41: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

41

Specification of Requirements & Tests

Execution & Documentationof Tests

Evaluation & Analysisof Test Results

Design & Implementationof Tests

Planningof Tests

Test Design & Implementation Tool

Vector3rd party

Traceability Information

SynchronizeTest Scripts

Test Execution Tool

Vector3rd party

Parse for Verdicts andRequirements / Test Specification Associations

PREEvision Test Engineering und Test Management: Information Flow

PREEvision for Functional Safety

PREEvision

Requirements

RequirementsEngineer

TestSpecifications

and Test Items

Derive

TestEngineer

Test Implementations

Manual test sequence

Test script

Create

Create

TestEngineer

TestEngineer

Test Plan and Test Tasks

Plan

TestManager

Test Execution

Verdict

ar

Verdict

ar

Execute

TestEngineer

Analysis

ReportReport

Report

Analyze

TestManager

File System

Requirements Source

RIF / ReqIFXLS

Import & Update

optional

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 42: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

42

Verification and Validation

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Validation

Verification

Page 43: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

43

ISO 26262 key areas supported by PREEvision

PREEvision for Functional Safety

SystemReq. Analysis

ComponentTest

SystemDesign

ComponentReq. Analysis

ComponentImplementation

SystemIntegration

ComponentIntegration

ComponentDesign

SystemTest

Item Definition

Hazard and Risk Analysis

FunctionalSafety Concept

QualitativeSafety Analyses

QuantitativeSafety Analyses

Validation

Safety Case

Verification

TechnicalSafety Concept

HSI Specification

DIASafety Plan

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 44: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

44

u Predefined safety plan template according to ISO 26262

u Can be adapted to match organizational needs

u Serves as process justification argument for safety case

u Can be used to generate DIA

Safety Plan

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Safety Plan

Page 45: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

45

u Predefined template for development interface agreement according to ISO 26262, including

u Distribution of safety activities between customer and supplier

u Responsible for each activity

u Data to be exchanged

Development Interface Agreement (DIA)

PREEvision for Functional Safety

u MS Excel

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

DIA

Page 46: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

46

ISO 26262 key areas supported by PREEvision

PREEvision for Functional Safety

SystemReq. Analysis

ComponentTest

SystemDesign

ComponentReq. Analysis

ComponentImplementation

SystemIntegration

ComponentIntegration

ComponentDesign

SystemTest

Item Definition

Hazard and Risk Analysis

FunctionalSafety Concept

QualitativeSafety Analyses

QuantitativeSafety Analyses

Validation

Safety Case

Verification

TechnicalSafety Concept

HSI Specification

DIASafety Plan

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Page 47: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

47

Safety Case Report

u Based on work products and safety plan

u Always consistent, can be generated at any time

u Covers technical safety argument and process justification argument

Concept of safety case

PREEvision for Functional Safety

Safety Goals

Hazard and Risk

Assessment

Item Definition

Safety Plan

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Safety Case

Page 48: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

48

Workflow for generating safety case reports

PREEvision for Functional Safety

Safety Plan

Hazard and Risk Analysis

Item Definition

Functional Safety

ConceptFTA

Perform Safety Engineering Tasks

Generate Safety Case

Report

Check Consistency

of Work Products

Item

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Safety Case

Page 49: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

49

u Automatic support for review of safety deliverables via online checks

u Support for (safety) managers via safety cockpit

Safety assessment support

PREEvision for Functional SafetyIt

em

Definitio

nH

azard

Analy

sis

and

Ris

k A

ssessm

ent

Functional

Safe

ty C

oncept

Technic

al

Safe

ty C

oncept

Hard

ware

Soft

ware

In

terf

ace (

HIS

)

Safe

ty C

ase

Validation

Verification

Quantita

tive

Safe

ty A

naly

sis

Qualita

tive

Safe

ty A

naly

sis

Safety Case

Page 50: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

50

PREEvision at a Glance

Introduction Functional Safety

PREEvision for Functional Safety

u Summary

Agenda

Page 51: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

51

Advantages

Summary

Integrated approach

•Full traceability can be easily established and maintained

•Consistent work products

•Reduce cost for tool interfaces

Automated consistency checking of deliverables

•Relieve engineers from error prone and tedious tasks

•Provide safety managers with insight in status and progress

•Reduce effort for manual reviews and progress reports

Engineer safe products – generate compliant deliverables

•Deliverables can be generated from engineering data

•Reduced effort for compliant deliverables

Page 52: Development of Functional Safe Systems using PREEvision€¦ · System, Service and Software Design Communication Design (AUTOSAR and Legacy Formats) Hardware Component Development

52 © 2016. Vector Informatik GmbH. All rights reserved. Any distribution or copying is subject to prior written approval by Vector. V1 | 2018-06-26

For more information about Vectorand our products please visit

www.vector.com

Author:Nico AdlerVector Germany