Applying ISO26262 to Tool Qualification



Similar documents
ISO Tool Chain Analysis Reduces Tool Qualification Costs

ISO Exemplary Tool Classification of Model-Based Design Tools

.OR.AT.ATTORNEY.AUCTION.BARGAINS.BAYERN.BERLIN.BLACKFRIDAY.BOUTIQUE.BRUSSELS.BUILDERS

Qualifying Software Tools According to ISO 26262

IBM Rational Rhapsody

Anwendung von Polyspace im Software Entwicklungsprozess nach IEC München, , Dr.-Ing. Jörg Barrho

Core Fittings C-Core and CD-Core Fittings

Problems and Measures Regarding Waste 1 Management and 3R Era of public health improvement Situation subsequent to the Meiji Restoration

R214 SPECIFIC REQUIREMENTS: INFORMATION TECHNOLOGY TESTING LABORATORY ACCREDITATION PROGRAM

ISO/IEC Part 2 provides the following copyright release:

Software Engineering. Software Testing. Based on Software Engineering, 7 th Edition by Ian Sommerville

Capital Works Construction Project. [Insert Project Title] [Insert Sponsoring Agency]

DRAFT. Propose that environmental considerations be added to the list of strategic considerations.

MDEP Generic Common Position No DICWG 02

Fundamental Principles of Software Safety Assurance

Service OnBoarding: A Process Approach for Uniting ITIL and DevOps. Bill Cunningham

COMPANY LOGO. Project Charter Project Charter

Open EMS Suite. O&M Agent. Functional Overview Version 1.2. Nokia Siemens Networks 1 (18)

Internal Quality Management System Audit Checklist (ISO9001:2015) Q# ISO 9001:2015 Clause Audit Question Audit Evidence 4 Context of the Organization

Introduction to Computers and Programming. Testing

DNV GL Assessment Checklist ISO 9001:2015

SUPPLIER ASSESSMENT CHECKLIST

Software Testing. Definition: Testing is a process of executing a program with data, with the sole intention of finding errors in the program.

Usability metrics for software components

The SPES Methodology Modeling- and Analysis Techniques

Tinwisle Corporation. ISO/DIS & 19440, Framework and Constructs for Enterprise Modeling

How to Improve Database Connectivity With the Data Tools Platform. John Graham (Sybase Data Tooling) Brian Payton (IBM Information Management)

Project Management Guidebook

Dealing with digital Information richness in supply chain Management - A review and a Big Data Analytics approach

Enhanced Project Management for Embedded C/C++ Programming using Software Components

Certified Secure Web Application Secure Development Checklist

Minnesota Health Insurance Exchange (MNHIX)

How To Monitor A Project

Clarifying a vision on certification of MDA tools

Software Project Management using an Iterative Lifecycle Model

Module 10. Coding and Testing. Version 2 CSE IIT, Kharagpur

Course Topics: Course Name: Oracle Purchasing. Duration 5 Days. Procure To Pay Lifecycle Overview. Oracle Purchasing Overview

Configuration Notes Aastra MX-ONE in Ascom VoWiFi System

WHITE PAPER. Effectively managing project performance reporting.

Risk-Based Validation of Computer Systems Used In FDA-Regulated Activities

METADATA-DRIVEN QLIKVIEW APPLICATIONS AND POWERFUL DATA INTEGRATION WITH QLIKVIEW EXPRESSOR

3rd Party Assurance & Information Governance outlook IIA Ireland Annual Conference Straightforward Security and Compliance

Institutionen för datavetenskap Department of Computer and Information Science

VDA6.3 Process Audit Webinar 1 st April Paul Hardiman Qualified VDA6.3 trainer

Configuring budget planning for Microsoft Dynamics AX 2012 R2

Software Engineering talk

A Case study based Software Engineering Education using Open Source Tools

A. Programme Specification

CHAPTER 8 THE METHOD-DRIVEN idesign FOR COLLABORATIVE SERVICE SYSTEM DESIGN

Movicon in energy efficiency management: the ISO standard

Knowledge Area Inputs, Tools, and Outputs. Knowledge area Process group/process Inputs Tools Outputs

Software Estimation: Practical Insights & Orphean Research Issues

Safe Automotive software architecture (SAFE) WP3 Deliverable D3.6.b: Safety Code Generator Specification

TESSY Automated dynamic module/unit and. CTE Classification Tree Editor. integration testing of embedded applications. for test case specifications

Threat Modeling. 1. Some Common Definition (RFC 2828)

8. Master Test Plan (MTP)

Methods Commission CLUB DE LA SECURITE DE L INFORMATION FRANÇAIS. 30, rue Pierre Semard, PARIS

UNIVERSITY OF BOLTON CREATIVE TECHNOLOGIES COMPUTING AND NETWORK SECURITY SEMESTER TWO EXAMINATIONS 2014/2015 NETWORK SECURITY MODULE NO: CPU6004

NATO GUIDANCE ON THE USE OF THE AQAP 2000 SERIES

Project Proposal: SAP Big Data Analytics on Mobile Usage Inferring age and gender of a person through his/her phone habits

SOFTWARE ENGINEERING INTERVIEW QUESTIONS

Site Configuration SETUP GUIDE. Windows Hosts Single Workstation Installation. May08. May 08

OCR LEVEL 3 CAMBRIDGE TECHNICAL

Development Process Automation Experiences in Japan

Turning Data into Actionable Insights: Predictive Analytics with MATLAB WHITE PAPER

Institute of Chartered Accountants Ghana (ICAG) Paper 2.2 Management Accounting

RUnit - A Unit Test Framework for R

Fortinet Solutions for Compliance Requirements

ISTQB Certified Tester. Foundation Level. Sample Exam 1

Effective Software Security Management

Model Based Engineering and Its Integration with Safety Assurance Cases for Medical Device Software

How to Upgrade SPICE-Compliant Processes for Functional Safety

ediscovery G-Cloud V Service Definition Lot 4 SCS Contact us: Danielle Pratt Tel: G-Cloud@esynergy-solutions.co.

Introduction to Quality Assessment

TIME KEEP LEGAL BILLING SOFTWARE REQUIREMENTS SPECIFICATION

What changes will ISO 9001:2015 bring?

TREE RISK ASSESSMENT

Unit 1: Introduction to Quality Management

Analyzing Plan Diagrams of Data Query Optimizers

Quality-Oriented Requirements Engineering for Agile Development of RESTful Participation Service

Testing of safety-critical software some principles

Continuous Delivery Workshop

Sample Pages for TEMPLATE FOR A SOFTWARE DOCUMENTATION MANAGEMENT PLAN

Initializing SAS Environment Manager Service Architecture Framework for SAS 9.4M2. Last revised September 26, 2014

Using Web Security Scanners to Detect Vulnerabilities in Web Services

Transcription:

Applying ISO26262 to Tool Qualification Dr. Oscar Slotosch, Validas AG Marco Reiling, Wind River Seite 1

Content: Tool Chain Analysis Motivation: ISO 26262: Tool Confidence Method: Tool Chain Analysis General Error Model Validas Tool Chain Analyzer Wind River Diab Compiler Qualification Kit Page 2

Content: Tool Chain Analysis Motivation: ISO 26262: Tool Confidence Method: Tool Chain Analysis General Error Model Validas Tool Chain Analyzer Wind River Diab Compiler Qualification Kit Page 3

Confidence in Use of Tools 26262-8 Planning Tool Usage [8-11.4.4] Tool Application Guide [6-5.5.4] Determination [8-11.4.4.1] of... Info for Eval & Use [8-11.4.4.2] to be available a) Feature Desc b) User Manual c) Env Tool Evaluation [8-11.4.5] a) Unique ID b) Config c) Use Cases d) Env e) Max ASIL f) Qual. Mthd d) Anomalous Op Cond e) Known Malfunctions f) Measures for Detect. Malfunctions Tool Criteria Evaluation Report [8-11.5.1] Tool Qualification [8-11.4.6] Validity Check [8-11.4.2] Usage Description [8-11.4.5.1] error -prevention & -detection a) Purpose b) Input/Output c) Env.& Func. Constraints Tool Qualification Report [8-11.5.2] Analysis [8-11.4.5.1] a) Tool Impact b) Possible Malfunctions with Tool Error Detection Qualification Info [8-11.4.6.2] Tool Confidence Level according to a) and b) Compliance Check [8-11.4.3] Confirmation Review [8-11.4.10] a) Unique ID b) Max TCL c) Max ASIL d) Config + Env e) TQ Persons f) Methods g) Measure Res Legend: [x-y] paragraph y in ISO 26262 part x (Baseline 19) h) Constraints + Malfunctions

ISO 26262-8, Chapter 11: Confidence in the use of software tools Classification in Tool Confidence Level (TCL) Tool Impact (TI) TI1: no impact => Tool is TCL1 TI2: some impact Tool Error Detection/prevention probability (TD) TD1:high confidence => Tool is TCL1 TD2:medium confidence => Tool is TCL2 TD3: low/unkown confidence => Tool is TCL3 Justification? Dokumentation? Confirmation Review! Page 5

Content: Tool Chain Analysis Motivation: ISO 26262: Tool Confidence Method: Tool Chain Analysis General Error Model Validas Tool Chain Analyzer Wind River Diab Compiler Qualification Kit Page 6

Modeling Method / Process for TCA 1. Planning: 1. Build a formal model of tool usage based on tool and process information 2. Validate the model (Review, Checklists) 2. Tool Evaluation 1. Systematically build an error model (black box / glass box) 2. Model detection and prevention (including assumptions) 3. Validate assumptions and error/detection/prevention model 4. Compute the TCL (with/without assumptions) 5. Generate tool evaluation report 3. Tool Qualification Validas General Error Model User Process tool usage TCA TCL Report Page 7 Features, possible Checks Tool Provider

Tool Chain Analysis & Error Model Motivation / Requirements for Error Model One error model describes possible tool errors in every tool Error model should be extensible (for new kinds of tools) Error model should cover all potential errors Error model should be acceptable (agreeable and simple to apply) Error model should cover the existing (known) errors Systematic ( Repeatable ) approach needed Page 8

General Error Model Creation Process Inductive: From known errors to classes of potential errors ( Observing ) Deductive: From tool to potential errors ( Analytic Approach ) Black-Box Approach: Consider Tool Outputs Default errors for typical artifact attributes (XML, Code, ) White-Box Approach: Consider Tool Structure (features & tool components) Management: Default errors for typical tool attributes (Optimizing / Parsing / Searching / ) Relation between errors: Subsuming Assignment of errors to tool chain Validation of error model error model with Default Classes Page 9

Tool / Feature Model Tool provider / expert creates this model Based on tool analysis Consisting of Tools Features with input/output artifacts Potential errors Mitigation possibilities with probabilities (HIGH / MEDIUM / LOW) Checks Restrictions Page 10

Process/Use Case Model User creates this model Based on his process Consisting of Tools Artifacts Use-Cases with input/output artifacts Potential errors are inferred from required features (including proposals for mitigations) Required features (available from Tool model) Page 11

Determine Tool Confidence Level Can be computed automatically from the model Validas General Error Model User Process tool usage TCA TCL Report Features, possible Checks Tool Provider Create a report to document the results Page 12

Content: Tool Chain Analysis Motivation: ISO 26262: Tool Confidence Method: Tool Chain Analysis General Error Model Validas Tool Chain Analyzer Wind River Diab Compiler Qualification Kit Page 13

Tool Chain Analyzer (TCA) Automatically determines the TCLs of tools and tool chains Bases on a formal model of Derived Error Model in TCA Tools Use cases (and features) Errors Detection/prevention mechanisms Artifacts (inputs & outputs) Qualifications for tools & features Supports generic error models Checks the validity of qualifications with a given ASIL Generates reports (.docx) Developed from Validas AG within European research project RECOMP Rich client, based on Eclipse modeling framework Evaluation available at www.validas.de/tca152.zip Page 14

Content: Tool Chain Analysis Motivation: ISO 26262: Tool Confidence Method: Tool Chain Analysis General Error Model Validas Tool Chain Analyzer Wind River Diab Compiler Qualification Kit Page 15

Wind River Diab Compiler Provides Classification Information Features Potential Errors Provides Qualification Support (Qualification Kit) Instrumented Compiler Tests Application Method More Details will be presented at http://www.embedded-konferenz.de/ Page 16 3. Juli 2012 Stuttgart, Mövenpick Airport Hotel

Summary Systematic method to fulfill the ISO 26262 tool requirements Generic Error Model for repeatable results Validas Tool Chain Analyzer Wind River Diab Compiler Qualification Kit Page 17

Thank You! Arnulfstraße 27 80335 München www.validas.de info@validas.de Seite 18