ISO 26262

This master project report titled, ‘Document Management Software Tool for Safety-related Application (ISO 26262)’ was prepared because it represents a certain evaluation grade for the master course on Functional Safety Engineering at the University of Kassel, Hessen, Germany.
This report consists of the ideas and demonstrations on the document management software tool designed for creating highly technical documentation (work products) for ISO 26262 compliant electrical and/or electronic (E/E) safety-related system or sub-system, automatically, repeatedly, efficiently, and quickly. The software tool was designed using the graphical user interface (GUI) library, Tkinter, from the Python programming language and the codes were written in the PyCharm, which is an integrated development environment (IDE) suitable for executing the Python programming language.
This report has been organized to highlight some of the fundamental concepts of functional safety, relevant information on documentations mentioned in the generic functional safety standard series IEC 61508, also in functional safety standard series for road vehicles ISO 26262. Followed by the approach and methodology of the document management software tool designed for this master course project. All the relevant documentation templates used by the software tool is provided in the annex, and in the reference section of this report all the information used in writing this report, as well as designing the software interface are provided for further understanding on any particular topic. The source code used for developing the document management software tool is not included in this report but could be made available on request.
Towards the end of the report, in the future work section, a discussion on the potential improvement points of this software tool is emphasized, which could be used as a guide for the future works in the similar topic. Finally, the project report ends with the conclusion section which summarizes the important points of this project report as a quick recap.

Although autonomous driving is characterized by the definition for “fully automated” according to BASt as well as the quote by Feil “self-determination within the scope of an higher (moral) law”, it is possible to come up with a large variety of usage scenarios and specifications for autonomous driving. In order to grasp this variety, proxies are sought, which on the one hand make use of distinguishing characteristics, and on the other hand describe typical usage scenarios for autonomous driving. In the following, these will be called use cases for autonomous driving. Besides the nomenclature, the use cases are defined by their distinguishing characteristics, so that a common understanding can be reached for all writing and reading these book chapters.

Road vehicles-functional safety, ISO 26262, is a functional safety standard used in the automotive industry, and ASIL is a key component to determine safety requirements for software development. Complying with this standard is critical for automotive product development. OEMs, their suppliers, and developers of automotive components all need to comply. Learn more in an Automotive Functional Safety ISO 26262 Training course by Tonex.

In this chapter, a survey of the current state of research on autonomous driving is given and is set in the context of the requirements of an autonomous vehicle following the vision of an automated taxi. The overview is based on (scientific) publications and self-reports of the developing teams. Aspects of interest for this summary are approaches on environmental perception, self-perception, mission accomplishment, localization, cooperation, map usage, and functional safety. Typically, emphasis is given to reliance on global satellite systems (e.g., GPS) and map data. Only a few approaches focus on environmental perception and scene understanding. Even though impressive demonstrations of autonomous driving have been presented in recent decades, this overview concludes that many aspects still remain only partially solved or even unsolved, especially when driving autonomously in public road traffic.

The  Code  of  Practice  (CoP)  comprises  a  suitable ADAS  (Advanced  Driver  Assistance  System) description  concept  including ADAS  specific requirements  for  system  development. It  summarises best  practices  and  proposes  methods  for  risk assessment and controllability evaluation. The Code of Practice has been pro-duced  by  a  group  of  experts within  the  RESPONSE  3  project,  a subproject  of  the integrated  project  PReVENT,  a  European  automotive industry  activity,  co-funded  by  the  European Commission, to contribute to road safety by developing and demonstrating pre-ventive safety applications and technologies.

Failure Mode and Effects Analysis (FMEA) is a key safety assessment analysis that determine failure modes at system, hardware and software level. Overlooking Failure Modes can often cause system or functionality failure which directly impacts a systems safety performance, reliability and quality.

FMEA is a bottom-up approach which has four key phases - identification of fault, assessment of impact, determination of potential causes and their resolutions, and finally testing and documentation of analysis.

FMEA addresses the effect of failures at the system, software and hardware level. The outcome of the analysis helps us identify gaps in safety requirements specification and provides input for component testing, integration testing and system level testing. This paper describes the application of Failure Mode and Effects Analysis (FMEA) to software modules.

ISO 26262, titled Road Vehicles–Functional Safety, is the new automotive functional safety standard for passenger vehicle industry. In order to accomplish the goal of designing and developing dependable automotive systems , ISO 26262 uses the concept of Automotive Safety Integrity Levels (ASILs), the adaptation of Safety Integrity Levels. ASILs are allocated to the components and subsystems that can cause system failure and malfunctions that lead to hazards. ASILs allocation is a hard problem consists of finding the optimal allocation of safety levels to the system architecture which must guarantee that the highest safety requirements are met while development cost of the automotive system is kept minimum. There were many successful attempts to solve this problem using different techniques. However, it is worth pointing out that there is an absence of a review that provides an in-depth study of all the existing methods and highlights their merits and demerits. This paper presents an overview of different approaches that were used to solve ASILs allocation problem. The review provides an overview of safety requirements including the related standards followed by a study of the resolution methods of the existing approaches. The study of each approach provides a detailed explanation of the used methodology and a discussion of its strength and weaknesses including the main open challenges.