Embed Size (px)
Citation preview
Contact: Rakesh Rana, [email protected]
ParticipantsPhD Student Rakesh Rana, University of Gothenburg
Academic supervisors Prof. Jörgen Hansson, Chalmers University of Technology
Associate Prof. Miroslaw Staron, University of Gothenburg
Asst. Prof. Christian Berger, University of Gothenburg
Verification of ISO 26262 Software requirements in safety critical EE-systems
VISEE
Objectives
• Develop new verification & validation
methods and tools for safety compliance at
complete EE system level.
• Develop means and approaches for
building statistical evidence for safety goal
argumentation according to ISO 26262
References[1] McKinsey: McKinsey Analysis. PTW HAWK survey, Institute for Production Management,
Technical University of Darmstadt, 2003.
[2] ISO/FDIS 26262:2010 - Road vehicles - Functional safety, International Organization for
Standardization.
[3] N. Mellegård, M. Staron and F. Törner, “A light-weight defect classification scheme for embedded
automotive software and its initial evaluation,” in International Symposium on Software Reliability
Engineering (ISSRE), 2012.
Industrial supervisors
Martin Nilsson, Volvo Car Corporation
Dr. Fredrik Törner, Volvo Car Corporation
FFI, Proj No: #####
ISO 26262: Road vehicles – Functional safety [2]
Chapter 6
Part 6: Product development at
the software level
Model based development
Defect backlog [3]
Motivation
• According to a McKinsey study automotive
software furthers approximately 80% of
future innovations in cars [1].
• Software products account for most part of
functionality in modern safety systems such
as pedestrian detection system.
• At early stages, model based simulations
(eg. simulink models) can be effective tools
to predict and prevent late defects.
• Software functionality verification and
validation is now a critical factor for
delivering quality products.
Next Steps
• WP1: Identify the main challenges to effective
implementation of ISO 26262, Chapter 6
Interviews to identify practical challenges
• WP2: Defect analysis, prediction & prevention
• WP3: Develop verification methods to prevent
defects by types
• WP4: Case studies evaluating the results
Impact
• Increase OEMs capacity to introduce new
software functions fulfilling the ISO 26262
requirements at reasonable cost and time
• Safer cars at optimal development costs
• Innovative V&V methods for automotive
software engineering
Pedestrian detection system
