Course syllabus - Functional safety for safety critical software

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:
 
1. be well aware of key issues, tools and methods used for development of safety-critical software
2. be able to apply selected tools and methods for development and quality assurance of safety-critical software
3. have demonstrated ability to document the safety assurance work
4. have acquired an ability to adopt scientific advances within the area

Course content

1. 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".
2. Analysis and modelling methods; review of analysis and modelling techniques for the development of safety-critical systems.
3. Verification and validation of safety critical software, methods and activities to perform verification and validation
4. Architectures for safety critical systems. Safety as a design constraint

Tuition

Web-based pre-recorded lectures.

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 B/Swedish course 3 and English course A/English course 6 are required. For courses given entirely in English exemption is made from the requirement in Swedish course B/Swedish course 3.
 

Examination

Written assignment (INL1), Module 1: Introduction, 2 credits, (examines the learning objectives 1, 3 and 4), marks Fail (U) or Pass (G)
Written assignment (INL2), Module 2: Analysis Techniques, 1,5 credits, (examines the learning objectives 1 and 4), marks Fail (U) or Pass (G)
Written assignment (INL3), Module 3: Verification and Validation, 1,5 credits, (examines the learning objectives 1-4), marks Fail (U) or Pass (G)
Written assignment (INL4), 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 a disability has the opportunity to submit a request for supportive measures during written examinations or other forms of examination, in accordance with the Rules and Regulations for Examinations at First-cycle and Second-cycle Level at Mälardalen University (2020/1655). It is the examiner who takes decisions on any supportive measures, based on what kind of certificate is issued, and in that case which measures are to be applied.

Suspicions of attempting to deceive in examinations (cheating) are reported to the Vice-Chancellor, in accordance with the Higher Education Ordinance, and are examined by the University’s Disciplinary Board. If the Disciplinary Board considers the student to be guilty of a disciplinary offence, the Board will take a decision on disciplinary action, which will be a warning or suspension.

Grade

Pass, Fail

Interim Regulations and Other Regulations

The course overlaps with 6 credits towards DVA433 Safety-critical Software.