Course syllabus - Safety critical software
Autumn semester 2018
A1N (Second cycle, has only first-cycle course/s as entry requirements).
School of Innovation, Design and Engineering
Course literature is preliminary up to 8 weeks before course start. Course literature can be valid over several semesters.
Engineering a safer world : systems thinking applied to safety
Cambridge, Mass. : MIT Press, cop. 2011. - xx, 534 p.
ISBN: 978-0-262-01662-9 LIBRIS-ID: 13552321
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
Institute of Electrical and Electronics Engineers, 2013
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
IEEE Software, Volume: 20, Issue: 3, 2003
Design and code inspections to reduce errors in program development
IBM Systems Journal, Volume: 15, Issue: 3, 1976
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
Australian Transport Safety Bureau, 2007
Inadequate risk analysis might jeopardize the functional safety of modern systems, Technical report
Mälardalen University, 2016
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
Safety and Reliability Society, 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
IET, Software Engineering Journal, Volume: 6, Issue 2, 1991
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.
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
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
Web-based pre-recorded lectures.
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.
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.Study guide
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.