Hochschule Darmstadt - Fb Informatik

Drucken| Layout| Design| Schriftgröße English|
Modulbeschreibung
Module:Functional Safety for Safety-Critical Software
Module numbers:41.5074 [PVL 41.5075]
Language:english
Study programme:Dualer Master 2021 - Katalog AS: Anwendungs- und systemorientierte Module
Dualer Master 2021 - Vertiefung SE: Software-Engineering
Master 2021 - Katalog AS: Anwendungs- und systemorientierte Module
Master 2021 - Vertiefung SE: Software-Engineering
Dualer Master 2013 - Katalog AS: Anwendungs- und systemorientierte Module
Dualer Master 2013 - Vertiefung SE: Software-Engineering
Master 2013 - Katalog AS: Anwendungs- und systemorientierte Module
Master 2013 - Vertiefung SE: Software-Engineering
MN Data Science 2016 - Katalog M-I_I: Allgemeine Wahlpflicht Informatik
Type of course:V+P = Lecture+Practical
Weekly hours:3+1
Credit Points:6
Exam:oral exam
Registering for examexplicitly and independent of booking
PVL (e.g. Practical):not graded
Frequency of offering:each winter semester (lastly in WS 2021/2022)
Required knowledge:Sound knowledge in Software-Engineering, Good programming skills
Learning objectives:The students can
  • recognize the difference between Usage Safety ("Gebrauchssicherheit)", Electrical Safety, and Functional Safety
  • write SW requirements
  • apply a Safety Analysis and Dependent Failure Analysis to software
  • recognize traceability between requirements, SW architectural design components, SW units, and source code
  • recognize criteria for choosing between source code reviews and SW unit testing
Content:Based on a simple case study, it is shown that safety-critical software is based on two pillars:

1. Software engineering methodology, i.e. avoidance of "systematic faults":
  • Criteria state-of-the-art requirements specifications
  • Precise understanding of SW design modelling techniques (UML,SysML)
  • Fault indentification techniques (e.g. SW FMEA, Dependent Failure Analysis, Fault Tree Analysis (FTA))
  • Difference between "SW Unit" and "SW component"
  • Interplay between SW code metrics, SW unit testing, code reviews, SW integration testing
  • Traceability between requirements, SW design, code, test cases

2. Implemented fault detection & mitigation in code, e.g.
  • homogeneous and heterogeneous redundancy
  • HW-supported memory space protection vs. CRC checksums vs. Double Inverse Storage
  • Task execution timing vs. high interrupt loads vs. controfl flow monitoring
Literature:
  • Funktionale Sicherheit im Automobil, ISO 26262, Systemengineering auf Basis eines Sicherheitslebenszyklus, Carl Hanser, ASIN: B01LP371ZC
  • Funktionale Sicherheit nach ISO 26262: Ein Praxisleitfaden zur Umsetzung
Lecture style / Teaching aids:Seminaristic lecture using parts of the ISO standard ISO 26262 and a mini case study
Responsibility:Ralf Hahn
Released:WS 2020/2021
Professional competencies:
  • formal, algorithmic, mathematical competencies: low
  • analytical, design and implementation competencies: high
  • technological competencies: high
  • capability for scientific work: low
Interdisciplinary competencies:
  • project related competencies: high

[Fachbereich Informatik] [Hochschule Darmstadt]
© 2008 - 2022 FBI OBS Team. Alle Rechte vorbehalten.