Print Course syllabus
Course syllabus - Safety critical software
Scope
6.0 credits
Course code
DVA465
Valid from
Autumn semester 2026
Education level
Second cycle
Progressive Specialisation
A1N (Second cycle, has only first-cycle course/s as entry requirements)
Main area(s)
Computer Science
Organisation
Department of Computer Science & Engineering
Ratified
2018-02-01
Revised
2025-11-03
Literature lists
Course literature is preliminary up to 8 weeks before course start. Course literature can be valid over several semesters.
-
Books
Engineering a safer world: systems thinking applied to safety
ISBN: 978-0-262-01662-9
Articles
A Combined Analysis Method of FMEA and FTA for Improving the Safety Analysis Quality of Safety-Critical Software, 2013 IEEE International Conference on Granular Computing
A Systematic Way to Incorporate Security in Safety Analysis, 3rd Workshop on Security and Dependability of Critical Embedded Real-Time Systems
Best Practices in Code Inspection for Safety-Critical Software
Design and code inspections to reduce errors in program development
Determining Maximum Stack Usage in Preemptive Shared Stack Systems, 27th IEEE International Real-Time System Symposium
Experiences with program static analysis, In proceedings of the 5th International Software Metrics Symposium
IEEE Standard for Software Verification and Validation Plans, IEEE Std 1012-1986
In-flight upset event 240 km north-west of Perth, ATSB TRANSPORT SAFETY INVESTIGATION REPORT, Aviation Occurrence Report 200503722
Inadequate risk analysis might jeopardize the functional safety of modern systems, Technical report
Issues on software testing for safety-critical real-time automation systems, 23rd Digital Avionics Systems Conference
Practical experiences of applying source-level WCET flow analysis to industrial code, In proceedings of the 4th international conference on Leveraging applications of formal methods, verification and validation
PROBABILISTIC R&M PARAMETERS AND REDUNDANCY CALCULATIONS, Applied R&M Manual for Defence Systems, Part D - Supporting Theory, GR-77 Issue 2012
Risk-based Decision-making Fallacies: Why Present Functional Safety Standards Are Not Enough, IEEE International conference on software architecture workshops
Safety Tactics for Software Architecture Design, In proceedings of the 28th annual international computer software and applications confererence
The choice of computer languages for use in safety-critical systems
Objectives
The purpose is to give the students an overview of issues and methods for development and quality assurance of safety-critical software, including details of selected technologies, methods and tools.
Learning outcomes
After completing the course, the student shall be able to:
- be well aware of key issues, tools and methods used for development of safety-critical software
- be able to apply selected tools and methods for development and quality assurance of safety-critical software
- have demonstrated ability to document the safety assurance work
- have acquired an ability to adopt scientific advances within the area
Course content
- Introduction to functional safety; knowledge that give increased understanding of the relationship between Embedded systems / safety-critical system / accidents / complexity / development models (development lifecycle models) / certification / "the safety case".
- Analysis and modelling methods; review of analysis and modelling techniques for the development of safety-critical systems.
- Verification and validation of safety critical software, methods and activities to perform verification and validation
- Architectures for safety critical systems. Safety as a design constraint
Specific requirements
120 credits of which at least 80 credits should be within Computer Science, Computer Engineering or equivalent, and at least 18 months of documented work experience in software development or software related areas. In addition Swedish course 3 or Swedish level 3 and English course 6 or English level 2 are required. For courses given entirely in English exemption is made from the requirement in Swedish course 3 or Swedish level 3.
Examination
Oral examination (MUN1), digital oral examination through Teams, Module 1: Functional safety management, an introduction to functional safety, 2 credits, examines the learning objectives 1, 3 and 4, marks Fail (U) or Pass (G).
Oral examination (MUN2), digital oral examination through Teams, Module 2: Safety analysis, 1,5 credits, examines the learning objectives 1 and 4, marks Fail (U) or Pass (G).
Oral examination (MUN3), digital oral examination through Teams, Module 3: Software verification and validation, 1,5 credits, examines the learning objectives 1-4, marks Fail (U) or Pass (G).
Oral examination (MUN4), digital oral examination through Teams, Module 4: Architectures, 1 credit, examines the learning objectives 1,2 and 4, marks Fail (U) or Pass (G).
A student who has a certificate from MDU regarding disability study support, can request adaptions for the examination. It is the examiner who takes decisions on any adaptions, based on the certificate and other conditions.
Grade
Two-grade scale
Interim Regulations and Other Regulations
The course overlaps with 6 credits towards Safety-critical Software and also completely with Functional safety for safety critical software.