Seite 1. KUGLER MAAG CIE GmbH
|
|
|
- Adrian Armstrong
- 6 years ago
- Views:
Transcription
1 Requirements Engineering and Management with ISO and Automotive SPICE October 25, 2012 Milan 10th Workshop on Automotive Software & Systems Fabio Bella Kugler Maag Cie KUGLER MAAG CIE GmbH Seite 1
2 Agenda Introduction Requirements engineering according to Automotive SPICE Requirements engineering according to ISO Mapping of requirements-related work products of ISO and A-SPICE Requirements engineering and management with ISO and A-SPICE Conclusions Seite 2
3 Seite 3 Introduction (1/2) Situation with respect to regulation of requirements-related activities in the Automotive sector ISO regulates areas that are already partially addressed by Automotive SPICE In the case of requirements management and engineering, extensive overlaps but also great differences between the two standards exist In general, many companies have already structured their requirements-related processes to cope with expectations of Automotive SPICE What has to be considered when implementing ISO expectations with respect to requirements management and engineering in a context, which is already aligned to Automotive SPICE?
4 Source: ISO / DIS Introduction (2/2) Not addressed by Automotive SPICE Seite 4 As an example, with functional safety to be addressed as an item characteristic, many companies must widen their focus from the system they deliver to the whole item, which has to be safe As a result, the role of the customer becomes fundamental when eliciting (safety) requirements to properly understand hazardous events at item level and their consequences in terms of safety requirements to be met by individual systems of the item
5 Agenda Introduction Requirements engineering according to Automotive SPICE Requirements engineering according to ISO Mapping of requirements-related work products of ISO and A-SPICE Requirements engineering and management with ISO and A-SPICE Conclusions Seite 5
6 Automotive SPICE Engineering process group (ENG) Requirements elicitation (ENG.1) Customer / product management level System requirements analysis(eng.2) System architectural design (ENG.3) System level System testing (ENG.10) System integration test (ENG.9) SW requirements analysis (ENG.4) SW testing (ENG.8) SW design (ENG.5) SW level SW integration test (ENG.7) SW construction (ENG.6) Seite 6
7 Automotive SPICE Engineering process group (ENG) Requirements elicitation (ENG.1) Customer / product management level System requirements analysis (ENG.2) System architectural design (ENG.3) System level System testing (ENG.10) System integration test (ENG.9) SW requirements analysis (ENG.4) SW testing (ENG.8) SW design (ENG.5) SW level SW integration test (ENG.7) SW construction (ENG.6) Seite 7
8 Source: Automotive SPICE, PAM Vers. 2.5 ASPICE requirements-related processes ENG.1 Requirements elicitation: The purpose of the Requirements elicitation process is to gather, process, and track evolving customer needs and requirements throughout the life of the product and/or service so as to establish a requirements baseline that serves as the basis for defining the needed work products. Customer requirements ENG.2 System requirements analysis: The purpose of the System requirements analysis process is to transform the defined customer requirements into a set of desired system technical requirements that will guide the design of the system. System requirements ENG.4 Software requirements analysis: The purpose of the Software requirements analysis process is to establish the software requirements for the system. Software requirements No dedicated process exist to analyze hardware requirements Seite 8
9 Agenda Introduction Requirements engineering according to Automotive SPICE Requirements engineering according to ISO Mapping of requirements-related work products of ISO and A-SPICE Requirements engineering and management with ISO and A-SPICE Conclusions Seite 9
10 ISO Overview 1. Vocabulary 2-5 Overall safety management 2. Management of functional safety 2-6 Safety management during the concept phase and the product development 2-7 Safety management after the item s release for production 3. Concept phase 4. Product development at the system level 7. Production and operation 4-5 Initiation of product 4-11 Release for production 3-5 Item definition development at the system level 7-5 Production 4-10 Functional safety assessment 3-6 Initiation of the safety 4-6 Specification of the lifecycle technical safety requirements 4-9 Safety validation 3-7 Hazard analysis and risk assessment 3-8 Functional safety concept 4-7 System design 4-8 Item integration and testing 5. Product development at the hardware level 5-5 Initiation of product development at the hardware level 6. Product development at the software level 6-5 Initiation of product development at the software level 7-6 Operation, service (maintenance and repair), and decommissioning 5-6 Specification of hardware safety requirements 5-7 Hardware design 5-8 Evaluation of the hardware architectural metrics 5-9 Evaluation of safety goal violations due to random HW failures 5-10 Hardware integration & testing 6-6 Spec. of SW safety requirem. 6-7 Software architectural design 6-8 SW unit design & implementation 6-9 Software unit testing 6-10 Software integration & testing 6-11 Verification of software safety requirements 8-5 Interfaces within distributed developments 8-6 Specification and management of safety requirements 8. Supporting processes 8-7 Configuration management 8-10 Documentation 8-8 Change management 8-9 Verification 8-11 Confidence in the use of software tools 8-12 Qualification of SW components 8-13 Qualification of HW components 8-14 Proven in use argument 9-5 Requirements decomposition with respect to ASIL tailoring 9. ASIL-oriented and safety-oriented analyses 9-6 Criteria for coexistence of elements 9-7 Analysis of dependent failures 9-8 Safety analyses 10. Guideline on ISO (informative) Seite 10
11 ISO Overview 1. Vocabulary 2-5 Overall safety management 2. Management of functional safety 2-6 Safety management during the concept phase and the product development 2-7 Safety management after the item s release for production 3. Concept phase 4. Product development at the system level 7. Production and operation 4-5 Initiation of product 4-11 Release for production 3-5 Item definition development at the system level 7-5 Production 4-10 Functional safety assessment 3-6 Initiation of the safety 4-6 Specification of the lifecycle technical safety requirements 4-9 Safety validation 3-7 Hazard analysis and risk assessment 3-8 Functional safety concept 4-7 System design 4-8 Item integration and testing 5. Product development at the hardware level 5-5 Initiation of product development at the hardware level 6. Product development at the software level 6-5 Initiation of product development at the software level 7-6 Operation, service (maintenance and repair), and decommissioning 5-6 Specification of hardware safety requirements 5-7 Hardware design 5-8 Evaluation of the hardware architectural metrics 5-9 Evaluation of safety goal violations due to random HW failures 5-10 Hardware integration & testing 6-6 Spec. of SW safety requirem. 6-7 Software architectural design 6-8 SW unit design & implementation 6-9 Software unit testing 6-10 Software integration & testing 6-11 Verification of software safety requirements 8-5 Interfaces within distributed developments 8-6 Specification and management of safety requirements 8. Supporting processes 8-7 Configuration management 8-10 Documentation 8-8 Change management 8-9 Verification 8-11 Confidence in the use of software tools 8-12 Qualification of SW components 8-13 Qualification of HW components 8-14 Proven in use argument 9-5 Requirements decomposition with respect to ASIL tailoring 9. ASIL-oriented and safety-oriented analyses 9-6 Criteria for coexistence of elements 9-7 Analysis of dependent failures 9-8 Safety analyses 10. Guideline on ISO (informative) Seite 11
12 ISO Overview 1. Vocabulary 2-5 Overall safety management 5. Product development at the hardware level 2. Management of functional safety 3. Concept phase 4. Product development at the system level 7. Production and operation 4-5 Initiation of product 4-11 Release for production 3-5 Item definition development at the system level 7-5 Production 4-10 Functional safety assessment 3-6 Initiation of the safety 4-6 Specification of the lifecycle technical safety requirements 4-9 Safety validation 3-7 Hazard analysis and risk assessment 3-8 Functional safety concept 2-6 Safety management during the concept phase and the product development 4-7 System design 4-8 Item integration and testing Safety Goals 5-5 Initiation of product development at the hardware level 6. Product development at the software level 6-5 Initiation of product development at the software level 2-7 Safety management after the item s release for production Technical safety requirements Technical safety concept 7-6 Operation, service (maintenance and repair), and decommissioning Software safety requirements 5-6 Specification of hardware safety requirements 5-7 Hardware design 5-8 Evaluation of the hardware architectural metrics Functional safety requirements Functional safety concept 5-9 Evaluation of safety goal violations due to random HW failures 5-10 Hardware integration & testing 6-6 Spec. of SW safety requirem. 6-7 Software architectural design 6-8 SW unit design & implementation 6-9 Software unit testing 6-10 Hardware Software integration safety & testing requirements 6-11 Verification of software safety requirements 8-5 Interfaces within distributed developments 8-6 Specification and management of safety requirements 8. Supporting processes 8-7 Configuration management 8-10 Documentation 8-8 Change management 8-9 Verification 8-11 Confidence in the use of software tools 8-12 Qualification of SW components 8-13 Qualification of HW components 8-14 Proven in use argument 9-5 Requirements decomposition with respect to ASIL tailoring 9. ASIL-oriented and safety-oriented analyses Generic rules applicable to all 10. Guideline safety on ISO requirements (informative) 9-6 Criteria for coexistence of elements 9-7 Analysis of dependent failures 9-8 Safety analyses Seite 12
13 Technical safety requirements Requirements at the item / system level including safety mechanisms: Detection, indication and control of faults in the system itself and in external devices interacting with the system Measures to achieve or maintain a safe state Fault tolerant time interval and emergency operation time Measures to prevent faults from being latent (6.4.4: ASIL (A), (B), C, D) Tests before and after a period of operation (pre-drive checks, postdrive checks) Multiple point fault detection interval Seite 13
14 Agenda Introduction Requirements engineering according to Automotive SPICE Requirements engineering according to ISO Mapping of requirements-related work products of ISO and A-SPICE Requirements engineering and management with ISO and A-SPICE Conclusions Seite 14
15 Automotive SPICE Engineering process group (ENG) Requirements elicitation (ENG.1) Customer / product management level System requirements analysis(eng.2) System architectural design (ENG.3) System level System testing (ENG.10) System integration test (ENG.9) SW requirements analysis (ENG.4) SW testing (ENG.8) SW design (ENG.5) SW level SW integration test (ENG.7) SW construction (ENG.6) Seite 15
16 Automotive SPICE Engineering process group (ENG) Requirements elicitation (ENG.1) Safety Goals Customer Functional level Safety Requirements Functional Safety Concept System requirements analysis(eng.2) System architectural design (ENG.3) System level System testing (ENG.10) System integration test (ENG.9) SW requirements analysis (ENG.4) SW testing (ENG.8) SW design (ENG.5) SW level SW integration test (ENG.7) SW construction (ENG.6) Seite 16
17 Automotive SPICE Engineering process group (ENG) Requirements elicitation (ENG.1) Customer level System requirements analysis(eng.2) System architectural design (ENG.3) Technical Safety Requirements System testing (ENG.10) Technical Safety Concept System level System integration test (ENG.9) SW requirements analysis (ENG.4) SW testing (ENG.8) SW design (ENG.5) SW level SW integration test (ENG.7) SW construction (ENG.6) Seite 17
18 Automotive SPICE Engineering process group (ENG) Requirements elicitation (ENG.1) Customer level System requirements analysis(eng.2) System architectural design (ENG.3) System level System testing (ENG.10) System integration test (ENG.9) SW requirements analysis (ENG.4) SW testing (ENG.8) Software Safety Requirements SW design (ENG.5) SW level SW integration test (ENG.7) SW construction (ENG.6) Seite 18
19 Automotive SPICE Engineering process group (ENG) Requirements elicitation (ENG.1) Customer level System requirements analysis(eng.2) System architectural design (ENG.3) System level System testing (ENG.10) System integration test (ENG.9) Hardware safety requirements cannot be directly mapped to any Automotive SPICE process SW testing (ENG.8) SW requirements analysis (ENG.4) SW design (ENG.5) SW level SW integration test (ENG.7) SW construction (ENG.6) Seite 19
20 Agenda Introduction Requirements engineering according to Automotive SPICE Requirements engineering according to ISO Mapping of requirements-related work products of ISO and A-SPICE Requirements engineering and management with ISO and A-SPICE Conclusions Seite 20
21 Requirements engineering and management with ISO and Automotive SPICE (1/3) Since Automotive SPICE does not explicitely address hardware development, to specify and analyze hardware safety requirements additional processes are required Other safety requirements such as safety goals, functional and technical safety requirements can be processed within the scope of processes already implemented and aligned to Automotive SPICE Safety requirements do not relate to nominal performance of the system under development; they can be integrated into existing requirements specifications, however, they need to be classified accordingly Seite 21
22 Requirements engineering and management with ISO and Automotive SPICE (2/3) Safety goals, functional safety requirements and functional safety concept are often delivered by the customer; in any case a strong cooperation between customer and supplier(s) is required to understand all possible hazardous events at item level and derive technical safety requirements for the system to be developed by the supplier Safety goals are required to calculate hardware metrics; without clearly defined and agreed safety goals, it could become difficult or even impossible to fulfill ISO requirements with respect to hardware metrics Seite 22
23 Requirements engineering and management with ISO and Automotive SPICE (3/3) Additional ISO expectations apply with respect to methods for requirements engineering and management Seite 23 Source ISO
24 Agenda Introduction Requirements engineering according to Automotive SPICE Requirements engineering according to ISO Mapping of requirements-related work products of ISO and A-SPICE Requirements engineering and management with ISO and A-SPICE Conclusions Seite 24
25 Conclusions (1/2) Even if Automotive SPICE and ISO uses different terminology they do not contradict each other Implementation of ENG.1, 2 and 4 of Automotive SPICE is a sound basis for requirements engineering and management To deal with ISO 26262, processes need to be extended to cope with hardware (safety) requirements Seite 25
26 Conclusions (2/2) During requirements elicitations, additional information about safety goals, functional safety requirements and concept has to be provided by the customer (if no customer is available, assumptions must be made SEooC) Safety requirements can be integrated into available requirements specifications but they must be distinguished from the nominal performance of the system under development ISO states additional expectations regarding methods for requirements engineering and management Seite 26
27 If you wish to deepen the subject KUGLER MAAG CIE GmbH Leibnizstr Kornwestheim, Germany contact me Fabio Bella Senior Process Consultant, Manager Italy Mobile Seite 27
28 Thank you for your attention. Questions? Comments? Requirements Engineering and Management with ISO and Automotive SPICE, Version A KUGLER MAAG CIE GmbH Seite 28
Functional Safety Implications for Development Infrastructures
Functional Safety Implications for Development Infrastructures Dr. Erwin Petry KUGLER MAAG CIE GmbH Leibnizstraße 11 70806 Kornwestheim Germany Mobile: +49 173 67 87 337 Tel: +49 7154-1796-222 Fax: +49
Functional Safety: ISO26262
Functional Safety: ISO26262 Seminar Paper Embedded systems group Aniket Kolhapurkar, University of Kaiserslautern, Germany kolhapur@rhrk.uni kl.de September 8, 2015 1 Abstract Functions in car, such as
Safety cannot rely on testing
Standards 1 Computer-based systems (generically referred to as programmable electronic systems) are being used in all application sectors to perform non-safety functions and, increasingly, to perform safety
ISO : Rustam Rakhimov (DMS Lab)
ISO 26262 : 2011 Rustam Rakhimov (DMS Lab) Introduction Adaptation of IEC 61508 to road vehicles Influenced by ISO 16949 Quality Management System The first comprehensive standard that addresses safety
Compliance driven Integrated circuit development based on ISO26262
Compliance driven Integrated circuit development based on ISO26262 Haridas Vilakathara Manikantan panchapakesan NXP Semiconductors, Bangalore Accellera Systems Initiative 1 Outline Functional safety basic
architecture (SAFE) Project Presentation SAFE project partners
Safe Automotive software architecture (SAFE) Project Presentation SAFE project partners Content Motivation Project Organization Work Packages Miscellaneous SAFE Motivation Scope and Goals Scope: Automotive
Functional Safety with ISO Principles and Practice Dr. Christof Ebert, Dr. Arnulf Braatz Vector Consulting Services
Functional Safety with ISO 26262 Principles and Practice Dr. Christof Ebert, Dr. Arnulf Braatz Vector Consulting Services Content Challenges with Implementing Functional Safety Basic Concepts Vector Experiences
AUTOMOTIVE SPICE v3.1 POCKET GUIDE
EXTENDED VDA SCOPE ASPICE v3.1 AUTOMOTIVE SPICE v3.1 POCKET GUIDE 4 5 6 7 8-9 10 11-13 14-15 16-19 20-43 44-49 50-51 52-69 70-93 94-103 104-105 106 Automotive SPICE at a glance Automotive SPICE application
ISO Compliance Using Approved Software Components for Road Vehicles
WHITEPAPER ISO 26262 Compliance Using Approved Software Components for Road Vehicles A Verocel and RTI Whitepaper Joe Wlad, Vice President, Business Development, Verocel, Inc. David Barnett, Vice President,
Automotive Safety and Security in a Verification Continuum Context
Automotive Safety and Security in a Verification Continuum Context Accelerating the Development of Automotive Electronic Systems Jean-Marc Forey Automotive Functional Safety Professional Synopsys Inc.
VOLUME HORST HIENTZ HANS-JÜRGEN KUGLER BONIFAZ MAAG DOMINIK STRUBE
VOLUME 2 2017 HORST HIENTZ HANS-JÜRGEN KUGLER BONIFAZ MAAG DOMINIK STRUBE Kugler Maag Cie People. Performance. Processes Integration of digital capabilities: Management consulting Performance improvement
SeamleSS Implementation. based on ISO 26262
SeamleSS Implementation of ECU Software based on ISO 26262 Growing use of the ISO 26262 standard is producing clearly defined requirements for the development and validation of E/E systems. Vector describes
Results of the IEC Functional Safety Assessment HART transparent repeater. PR electronics
exida Certification S.A. 2 Ch. de Champ-Poury CH-1272 Genolier Switzerland Tel.: +41 22 364 14 34 email: info@exidacert.com Results of the IEC 61508 Functional Safety Assessment Project: 9106 HART transparent
TÜV SÜD Automotive GmbH. ISO Certificates for Tools Approach and Examples
ISO 26262 Certificates for Tools Approach and Examples Agenda Introduction Using tools in the safety lifecycle Classification of tools The tool impact level (TI) The tool error detection level (TD) Qualification
Erol Simsek, isystem. Qualification of a Software Tool According to ISO /6
Qualification of a Software Development Tool According to ISO26262 Tool Qualification for the New Automotive Standard from a Tool Manufacturer s Perspective Erol Simsek, isystem Summary Chapter 8-11 of
Independent Verification and Validation (IV&V)
Independent Verification and Validation (IV&V) 12 th Annual NDIA CMMI Conference November 2012 - Denver, CO The MITRE Corporation The author s affiliation with The MITRE Corporation is provided for identification
Inside! icteam, a confluence of parallels. - Jyothi G Shivashankar (Robert Bosch Engineering and Business Solutions) Eclipsecon 2013
Inside! Eclipsecon 2013 26 Mar 2013 16:15 16:45 Room : Back Bay - Jyothi G Shivashankar (Robert Bosch Engineering and Business Solutions) - Ryan D Brooks (The Boeing Company) 1 Agenda 1 The parallel industries
Smart Strategic Approach for Functional Safety Implementation. Chandrashekara N Santosh Kumar Molleti
Smart Strategic Approach for Functional Safety Implementation Chandrashekara N Santosh Kumar Molleti August 2015 1 Table of Contents Abstract... 3 1. Introduction... 3 2. Approach-To-Concept... 4 2.1.
17/12/1437. Lecture. Project Scope Management. Lecture 4. Project Management Knowledge Areas Section 3 Chapter 5. Project Scope Management.
17/12/137 Project Management Knowledge Areas Section 3 Chapter 5 Project Scope Management 2 of 33 1 17/12/137 Quick Re-cab Plan Scope Management Collect Requirement Define Scope Create WBS Validate Scope
IEC and ISO A cross reference guide
and A cross reference guide This guide sets out to explain where the details for different safety lifecycle activities can be found in the standards for the Machinery Sector: and. 1 Concept 2 Overall scope
ISO (SPiCE) Assessment
ISO 15504 (SPiCE) Assessment Employee Motivation and Information using SPiCE The Road to Software Process Improvement DI Christian Steinmann SYNSPACE GmbH Kartäuserstrasse 49 D - 79102 Freiburg i.br. Vox
intacs TM newsletter edition
Dear intacs members, SPICE assessors and friends of intacs, We would like to start by calling your attention to some changes in intacs.info. For several years our colleague Timo Karasch was responsible
0 Introduction Test strategy A Test Strategy for single high-level test B Combined testing strategy for high-level tests...
TPI Automotive Test Process Improvement Version: 1.01 Author: Sogeti Deutschland GmbH Datum: 29.12.2004 Sogeti Deutschland GmbH. Version 1.01 29.12.04-1 - 0 Introduction... 5 1 Test strategy...10 1.A Test
THE CHALLENGE OF ISO FOR COMPLEX SOFTWARE MODELS Oliver Collmann
THE CHALLENGE OF ISO 26262 FOR COMPLEX SOFTWARE MODELS Oliver Collmann QUALITY IN THE DRIVER S SEAT SOLUTIONS FOR INTEGRATED QUALITY ASSURANCE OF EMBEDDED AUTOMOTIVE SOFTWARE OUR COMPANY WHO WE ARE Founded
Using the CESAR Safety Framework for Functional Safety Management in the context of ISO 26262
ERTS² 01 EMBEDDED REAL TIME SOFTWARE AND SYSTEMS 1 Using the CESAR Safety Framework for Functional Safety Management in the context of ISO 66 E. Armengaud 1, Q. Bourrouilh 1, G. Griessnig 1, H. Martin,
Requirements Analysis and Design Definition. Chapter Study Group Learning Materials
Requirements Analysis and Design Definition Chapter Study Group Learning Materials 2015, International Institute of Business Analysis (IIBA ). Permission is granted to IIBA Chapters to use and modify this
International Safety Standards Designing the Future
International Safety Standards Designing the Future Wayne Pearse Safety Consultant FSExpert (TÜV Rheinland, Machinery) Rev 5058-CO900D Copyright 2013 Rockwell Automation, Inc. All Rights Reserved. Copyright
Results of the IEC Functional Safety Assessment
Results of the IEC 61508 Functional Safety Assessment Project: 3051S Electronic Remote Sensors (ERS ) System Customer: Emerson Automation Solutions (Rosemount, Inc.) Shakopee, MN USA Contract No.: Q16/12-041
Integrating Functional Safety with ARM. November, 2015 Lifeng Geng, Embedded Marketing Manager
Integrating Functional Safety with ARM November, 2015 Lifeng Geng, Embedded Marketing Manager 1 ARM: The World s Most Scalable Architecture ARM ecosystem meets needs of vertical markets from sensors to
NATO Integrated Quality Requirements for Software throughout the Life Cycle
NATO Integrated Quality Requirements for Software throughout the Life Cycle Edition 1 (July 2001) -i- -ii- NORTH ATLANTIC TREATY ORGANIZATION MILITARY AGENCY FOR STANDARDIZATION (MAS) NATO LETTER OF PROMULGATION
Jon Keswick, CFSE aesolutions Inc. 250 Commonwealth Drive, Suite 200 Greenville, SC 29615, USA
Managing critical operational Process Safety Performance Indicators (PSPI) Prepared for the 10 th European Chemical Engineering Congress, Nice, France September 2015 Jon Keswick, CFSE aesolutions Inc.
Jari Soini. Information Technology Department Pori, Finland. Tampere University of Technology, Pori
Utilizing measurement in the context of software maturity models Jari Soini Tampere University of Technology Information Technology Department Pori, Finland Where I come from Pori University Consortium
On the management of nonfunctional requirements
- modulo B On the management of nonfunctional requirements Dr Tullio Vardanega European Space Research and Technology Centre and University of Padua TU Delft, 12 November 2001 Outline of the talk What
Verlässliche Echtzeitsysteme Können wir unseren Autos noch vertrauen? Bernhard Sechser Method Park Software AG, Erlangen
Verlässliche Echtzeitsysteme Können wir unseren Autos noch vertrauen? Bernhard Sechser Method Park Software AG, Erlangen 30.04.2012 Contents Who is Method Park? Why do we need Safety Standards? Process
OSADL SIL2LinuxMP - Linux Safety Qualification
- Safety rg> October 11, 2014 - Safety Justifying GNU/ A bit on s Why for Automotive Safety Why for safety? Satisfy Demands: General security demands Performance demands in cognitive systems Functional
CMMI-DEV V1.3 CMMI for Development Version 1.3 Quick Reference Guide
processlabs CMMI-DEV V1.3 CMMI for Development Version 1.3 Quick Reference Guide CMMI-DEV V1.3 Process Areas Alphabetically by Process Area Acronym processlabs CAR - Causal Analysis and Resolution...
Research on software systems dependability at the OECD Halden Reactor Project
Research on software systems dependability at the OECD Halden Reactor Project SIVERTSEN Terje 1, and ØWRE Fridtjov 2 1. Institute for Energy Technology, OECD Halden Reactor Project, Post Box 173, NO-1751
Fiat Group Automobiles Policy for Software Quality Improvement
Fiat Group Automobiles Policy for Software Quality Improvement 2010-01-2329 Published 10/19/2010 Edoardo Sivera Fiat Group Automobiles (FGA) Copyright 2010 SAE International ABSTRACT Automotive systems
Session Nine: Functional Safety Gap Analysis and Filling the Gaps
Session Nine: Functional Safety Gap Analysis and Filling the Gaps Presenter Colin Easton ProSalus Limited Abstract Increasingly regulatory and competent authorities are looking to hazardous Installation
BCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2
BCS THE CHARTERED INSTITUTE FOR IT BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 6 Professional Graduate Diploma in IT SOFTWARE ENGINEERING 2 Friday 30 th September 2016 - Morning Answer any THREE questions
Agile in Automotive 2016
Register until 1 September and save Agile in Automotive 200 15 and 16 November 2016 Le Meridien, Stuttgart, Germany www.euroforum.de/agile-automotive CONFERENCE TUTORIALS WORKSHOPS Discuss tomorrow s ideas
PSM. Practical Software and Systems Measurement A foundation for objective project management. PSM TWG ISO/IEC and IEEE Standards.
Practical Software and Systems Measurement A foundation for objective project management PSM PSM TWG ISO/IEC and IEEE Standards March 29, 2006 PSM 1 29 Mar 06 Current Standard Activities ISO/IEC 15939,
Development of AUTOSAR Software Components with Model-Based Design
Development of AUTOSAR Software Components with Model-Based Design Guido Sandmann Automotive Marketing Manager, EMEA The MathWorks Joachim Schlosser Senior Team Leader Application Engineering The MathWorks
Request For Information (RFI) For a. Spectrum Management & Monitoring System (SMMS)
Request For Information (RFI) For a Spectrum Management & Monitoring System (SMMS) Table of Contents 1 Introduction... 3 1.1 About Iraq CMC... 3 1.2 The Iraq CMC Objectives... 3 1.3 RFI Process... 4 2
PLC IMM IAS. Presented by: Simona Grigoras
PLC Training @ IMM IAS Presented by: Simona Grigoras Contents What is a process? Quality Management System - benefits Software Quality Assurance & Process Models PLC @ BU IMM & the V cycle model Process
ASSESSING QUALITY IN SOFTWARE ENGINEERING: A PRAGMATIC APPROACH. University of Pretoria
ASSESSING QUALITY IN SOFTWARE ENGINEERING: A PRAGMATIC APPROACH. A dissertation submitted to the department of Computer Science of the University of Pretoria in partial fulfilment of the requirements for
Results of the IEC Functional Safety Assessment Universal Converter. PR electronics
exida Certification S.A. 2 Ch. de Champ-Poury CH-1272 Genolier Switzerland Tel.: +41 22 364 14 34 email: info@exidacert.com Results of the IEC 61508 Functional Safety Assessment Project: 9116 Universal
ELECTROTECHNIQUE IEC INTERNATIONALE INTERNATIONAL ELECTROTECHNICAL
61508-1 IEC: 1997 1 Version 4.0 05/12/97 COMMISSION CEI ELECTROTECHNIQUE IEC INTERNATIONALE 61508-1 INTERNATIONAL ELECTROTECHNICAL COMMISSION Functional safety of electrical/electronic/ programmable electronic
Connectivity key to efficient, safe, and convenient mobility
Connectivity key to efficient, safe, and convenient mobility Dr. Markus Heyn Member of the board of management, Robert Bosch GmbH 1 Invented for life means connected for life Combining cross-domain know-how
IEC KHBO, Hobufonds SAFESYS ing. Alexander Dekeyser ing. Kurt Lintermans
IEC 61508 KHBO, Hobufonds SAFESYS ing. Alexander Dekeyser ing. Kurt Lintermans page 2 PART 1 : GENERAL REQUIREMENTS 1 Scope The first objective of this standard is to facilitate the development of application
DESIGN AND DEVELOPMENT
DESIGN AND DEVELOPMENT Requirements - ISO 9001:2008 (7.3) Supplemental Guidance - ISO 9004:2000 1 Design Planning (7.3.1) 2 The organization shall plan and control the design and development of product.
The Internal Consistency of the ISO/IEC Software Process Capability Scale
The Internal Consistency of the ISO/IEC 15504 Software Process Capability Scale Khaled El Emam Fraunhofer Institute for Experimental Software Engineering Sauerwiesen 6 D-67661 Kaiserslautern Germany elemam@iese.fhg.de
Software Quality. A Definition of Quality. Definition of Software Quality. Definition of Implicit Requirements
Definition of Software Quality Software Quality The Ultimate Goal of Software Engineering Software must conformance to explicit and implicit requirements if it is to be considered to be of good quality.
Work Plan and IV&V Methodology
Work Plan and IV&V Methodology Technology initiatives and programs should engage with an IV&V process at the project planning phase in order to receive an unbiased, impartial view into the project planning,
Pass4sure.ITIL-F.347.QA
Pass4sure.ITIL-F.347.QA Number: ITIL-F Passing Score: 800 Time Limit: 120 min File Version: 19.1 http://www.gratisexam.com/ ITIL-F.EN.dat ITIL Foundation Enjoy the real success with nicely written Questions
Roadblocks to Approving SIS Equipment by Prior Use. Joseph F. Siebert. exida. Prepared For. ISA EXPO 2006/Texas A&M Instrumentation Symposium
Roadblocks to Approving SIS Equipment by Prior Use Joseph F. Siebert exida Prepared For ISA EXPO 2006/Texas A&M Instrumentation Symposium Houston, TX/College Station, TX October 18, 2006/ January 24, 2007
Project Plan. CxOne Guide
Project Plan CxOne Guide CxGuide_ProjectPlan.doc November 5, 2002 Advancing the Art and Science of Commercial Software Engineering Contents 1 INTRODUCTION... 1 1.1 DELIVERABLE PURPOSE... 1 1.2 LIFECYCLE...
Command and Control Software Development Lessons Learned. Lt Col Michael D. Sarchet Deputy Director, Space Systems Command and Control Division
Command and Control Software Development Lessons Learned Lt Col Michael D. Sarchet Deputy Director, Space Systems Command and Control Division 1 UNCLASSIFIED Agenda Two real world case studies Lessons
New Machine Safety Standards Usher in Era of Better Design Flexibility and Safety Performance
New Machine Safety Standards Usher in Era of Better Design Flexibility and Safety Performance By Mike Miller, CFSE, Global Safety Market Development, and Wayne Solberg, Global Technical Consultant, Rockwell
Leveraging Your Service Quality Using ITIL V3, ISO and CMMI-SVC. Monday Half-Day Tutorial
Leveraging Your Service Quality Using ITIL V3, ISO 20000 and CMMI-SVC Monday Half-Day Tutorial Definitions Service - Employment in duties or work for another The Challenge This situation where organization
Development of Safety Related Systems
July 2015 LatticeSemiconductor 7 th Floor,111SW5 th Avenue Portland,Oregon97204USA Telephone:(503)268I8000 www.latticesemi.com WP004 The increasing degree of automation brings a lot of comfort and flexibility
Guideline Asset Management
Guideline Asset Management Title of the document National Rail Safety Regulator Page1of28 Document reference number: A389849 Version No. Approved by Publication date 1.0 Chief Executive November 2014 1.1
Introduction and Revision of IEC 61508
Introduction and Revision of IEC 61508 Ron Bell OBE, BSc, CEng FIET Engineering Safety Consultants Ltd Collingham House 10-12 Gladstone Road Wimbledon London, SW19 1QT UK Abstract Over the past twenty-five
Life-cycle Management of Safety Instrumented Systems
Life-cycle Management of Safety Instrumented Systems Dr. Bernd Schroers Bayer AG, Leverkusen, Germany University of Aachen, Germany University of Kassel, Germany D-51368 Leverkusen, Building 407 Abstract
Toward Practical Application of Formal Methods in Software Lifecycle Processes
Keynote Speech at ICFEM 2012, Kyoto Toward Practical Application of Formal Methods in Software Lifecycle Processes November 14, 2012 Mario Tokoro Research Supervisor, JST/CREST DEOS Project Sony Computer
Practical Applications of Statistical Methods Under 2011 FDA Process Validation Guidance
Practical Applications of Statistical Methods Under 2011 FDA Process Validation Guidance Abe Germansderfer Associate Director, Quality Control Gilead Sciences 2011 Process Validation Guidance In January
to confirm that its document management- and archiving solution fulfils all applicable audit criteria for document management solutions
The certification body of TÜV Informationstechnik GmbH hereby awards this certificate to the company Airbus S.A.S. 1 Rond Point Maurice Bellonte 31707 Blagnac, France to confirm that its document management-
Medical Device Software under IEC George Romanski
Medical Device Software under IEC 62304 George Romanski IEC 62304 Medical Device Software Software Lifecycle Processes Quality Management System* RISK MANAGEMENT Software Safety Classification Development
Functional safety Safety instrumented systems for the process industry sector
BRITISH STANDARD BS IEC 61511-1:2003 Functional safety Safety instrumented systems for the process industry sector Part 1: Framework, definitions, system, hardware and software requirements ICS 25.040.01;
ECSS-Q-ST-80C. Space product assurance. Software product assurance. Training Course. Fernando Aldea Head of Section Jordi Duatis Manrico Fedi
ECSS-Q-ST-80C Space product assurance Software product assurance Training Course Presenters (all of them from TEC-QQS): Fernando Aldea Head of Section Jordi Duatis Manrico Fedi 1 ECSS-Q-ST-80C Origins
M.Sc. (I.T.) Sem. IV IT INFRASTRUCTURE MANAGEMENT QUESTION BANK ( )
M.Sc. (I.T.) Sem. IV IT INFRASTRUCTURE MANAGEMENT QUESTION BANK (2014 2015) Unit 1: Introduction 1. List and explain the four Perspectives of ITSM. 2. Explain the terms Service Agreement and Service Level
3rd Agile in Automotive
3rd Agile in Automotive Register until 1 September and save 400 15 and 16 November 2017 Dormero Hotel Stuttgart, Germany www.euroforum.de/agile-automotive CONFERENCE TUTORIALS WORKSHOPS Discuss tomorrow
Software Engineering Modern Approaches
Software Engineering Modern Approaches Chapter : Software Process Eric Braude and Michael Bernstein Maintenance Testing The Software Development Lifecycle Implementation Design Phase most relevant to this
Software Auditor Skills Training Course Offered by The Westfall Team
Software Auditor Skills Training Course Software Auditor Skills is a 2-day course that is a subset of the Software Auditing course. This course is designed to provide a knowledge base and practical skills
Applying Systems Engineering to ITS Projects: Advancing Beyond Federal Rule 940. INCOSE IW Transportation Working Group January 27, 2015
Applying Systems Engineering to ITS Projects: Advancing Beyond Federal Rule 940 William Gleckler Deputy Systems Engineering Officer, NYCT Capital Program Management Vincent Cavataio, CCM Deputy Systems
Introducing SAFETY in ORGANIZATIONS Lessons Learned. Henrik Thane Adj. Professor in Functional Safety, MDH SAFETY INTEGRITY AB
Safety Integrity Introducing SAFETY in ORGANIZATIONS Lessons Learned Day 1 Henrik Thane Adj. Professor in Functional Safety, MDH SAFETY INTEGRITY AB 2016-03-16 CV Dr. Henrik Thane Senior Safety Assessor
Reliability of Safety-Critical Systems Chapter 2. Concepts and requirements
Reliability of Safety-Critical Systems Chapter 2. Concepts and requirements Mary Ann Lundteigen and Marvin Rausand mary.a.lundteigen@ntnu.no & marvin.rausand@ntnu.no RAMS Group Department of Production
Risk Mitigation in a Core Banking Conversion
Risk Mitigation in a Core Banking Conversion Greg Meidt, chief information officer Chemical Bank Dick Smies, vice president IBS Conversion Services 1 800 822 6758 Introduction A core banking migration
Figure 1 Function Point items and project category weightings
Software measurement There are two significant approaches to measurement that project managers need to be familiar with. These are Function Point Analysis (Albrecht, 1979) and COCOMO (Boehm, 1981). 1.
7. Model based software architecture
UNIT - III Model based software architectures: A Management perspective and technical perspective. Work Flows of the process: Software process workflows, Iteration workflows. Check Points of The process
Engineering Management Manual
Engineering Management Manual Configuration Management ED0014 Document Category: DMS: Document Control: Procedure CRN-EPR-ENG-014 Version Date Author/discipline Reviewer Approver Remarks 1.0 13/12/2011
WORK PLAN AND IV&V METHODOLOGY Information Technology - Independent Verification and Validation RFP No IVV-B
1. Work Plan & IV&V Methodology 1.1 Compass Solutions IV&V Approach The Compass Solutions Independent Verification and Validation approach is based on the Enterprise Performance Life Cycle (EPLC) framework
Safety Management Center. DNV IT Global Services Safety Engineering / Management in the automotive industry. Content
DNV IT Global Services Safety Engineering / Management in the automotive industry Enhancing Trust and Confidence in IT Automotive SPIN Italia 4 Workshop on Automotive Software Torino, 11.12.2009 Dr. Klaus
Core Skills: Contributing Skills: Role Title: Senior Project Manager EXAMPLE. Reference: SFIA level 5
Role Title: Senior Project Manager EXAMPLE Reference: SFIA level 5 Core Skills: Requirements definition and management Stakeholder relationship management (REQM) Level 5 (RLMT) Level 5 Financial management
Results of the IEC Functional Safety Assessment. ABB, Inc. Baton Rouge, LA USA
Results of the IEC 61508 Functional Safety Assessment Project: MT5000, MT5100 and MT5200 Level Transmitter Customer: ABB, Inc. Baton Rouge, LA USA Contract No.: Q16-06-017 Report No.: ABB 10-02-051 R001
IBM Integrated Product Development (IPD)
IBM Integrated Product Development (IPD) Project Executive: Bijan Salimi 09/14/11 Agenda What is IPD and its objectives? IPD Teams Hierarchy IPD Phases Teams Roles & Responsibilities Decision Checkpoints
AUTOSAR and ISO26262 compliant development by use of Libraries
AUTOSAR and ISO26262 compliant development by use of Libraries Vector Conference 2016 V1.0 2016-08-30 Agenda 1. Challenges in Automotive Development Projects 2. AUTOSAR and ISO26262 compliant development
Requirements Gathering using Object- Oriented Models
Requirements Gathering using Object- Oriented Models Software Quality Assurance What is software? According to the IEEE (Institute of Electrical and Electronics Engineers) A software is: Programs, procedures,
A Survey on the Development and Design Strategies for Safety Related Systems according the Standard IEC/EN 61508
Proceedings of the 6th WSEAS International Conference on Applied Computer Science, Tenerife, Canary Islands, Spain, December 16-18, 2006 97 A Survey on the Development and Design Strategies for Safety
Architecture Development Methodology for Business Applications
4/7/2004 Business Applications Santonu Sarkar, Riaz Kapadia, Srinivas Thonse and Ananth Chandramouli The Open Group Practitioners Conference April 2004 Topics Motivation Methodology Overview Language and
EB Automotive ECU solutions AUTOSAR Basic Software Tooling Functional Safety Customization Services
automotive.elektrobit.com EB Automotive ECU solutions AUTOSAR Basic Software Tooling Functional Safety Customization Services Electronic Control Unit Software and Services We take AUTOSAR to the road!
Results of the IEC Functional Safety Assessment. Pressure, Temperature and Vacuum Switches. BETA B.V. Rijswijk The Netherlands
exida Certification S.A. 2 Ch. de Champ-Poury CH-1272 Genolier Switzerland Tel.: +41 22 364 14 34 email: info@exidacert.ch Results of the IEC 61508 Functional Safety Assessment Project: Pressure, Temperature
Use of PSA to Support the Safety Management of Nuclear Power Plants
S ON IMPLEMENTATION OF THE LEGAL REQUIREMENTS Use of PSA to Support the Safety Management of Nuclear Power Plants РР - 6/2010 ÀÃÅÍÖÈß ÇÀ ßÄÐÅÍÎ ÐÅÃÓËÈÐÀÍÅ BULGARIAN NUCLEAR REGULATORY AGENCY TABLE OF CONTENTS
ISO 9001:2008 Quality Management System QMS Manual
2501 Kutztown Road Reading, PA, 19605 Tel. 610-929-3330 Fax 610-921-6861 ISO 9001:2008 Quality Management System QMS Manual The information contained in this document is Fidelity Technologies Corporation
Gulfstream Flight Test Safety Management System. Evaluation Tool Guidance
Gulfstream Flight Test Safety Management System Evaluation Tool Guidance Flight test presents unique hazards and elevated risk levels during the development and certification of aircraft and new systems.
ITIL Foundation. Objectives
ITIL Foundation ITIL, formally an acronym for Information Technology Infrastructure Library, is a set of detailed practices for IT service management (ITSM) that focuses on aligning IT services with the
Category 6 Operations Focus
MFC Cat 6 Ops Focus - 1 Category 6 Operations Focus Steve Sessions Director, Supplier Quality Operations Focus Overview Enterprise Work & Process Development Align customer requirements & value to business
Implementing Veeva Align Technical Overview. Ben Lawson Practice Manager Network & Align Services, Europe
Implementing Veeva Align Technical Overview Ben Lawson Practice Manager Network & Align Services, Europe 1 How is Veeva Align implemented? 2 How can Veeva Align be deployed? 3 What does a typical project