Critical Systems

Code:

PRODEI022

Acronym:

SC

Keywords
Classification	Keyword
OFICIAL	Comp. Architectures, Operating and Networks Sys.

Instance: 2012/2013 - 2S

Active?	Yes
Responsible unit:	Department of Electrical and Computer Engineering
Course/CS Responsible:	Doctoral Program in Informatics Engineering

Cycles of Study/Courses

Acronym	No. of Students	Study Plan	Curricular Years	Credits UCN	Credits ECTS	Contact hours	Total Time
PRODEI	2	Syllabus	1	-	6	54	162

Teaching language

Suitable for English-speaking students

Objectives

This course unit aims to broaden students’ knowledge regarding Critical Systems. This course unit will cover notions related to safety, which are fundamental during the development life-cycle of Critical Systems.

Learning outcomes and competences

At the end of this course, it is expected that students will have consolidated their knowledge: - The need for a systemic approach to safety; - The main software-based fault tolerance techniques; - The main verification and validation guidelines for the reliable operation in Critical Systems.

Working method

Presencial

Pre-requirements (prior knowledge) and co-requirements (common knowledge)

Basic knowledge of software engineering.

Program

Chapter 1 - Introduction to Critical Systems - Taxonomy - Presentation of relevant case studies related to safety - Safety criteria Chapter 2 - Development of safety-critical systems - Hazards analysis - Risk analysis Chapter 3 - Obtaining confidence: prevention, fault tolerance - Fault prevention - Quality management of Critical Systems - Development environments - Programming languages - Software fault tolerance: - Types of recovery - Techniques, Languages and Programming Environments - Diversion of Design/Implementation - Data diversity - Time diversity - Results adjudication Chapter 4 - Verification and validation of confidence: - Confidence modelling: basic concepts; - Modelling techniques: confidence blocks and fault trees - Software liability: fault prediction, error models, fault prediction models - HW/SW architecture modelling

Mandatory literature

Neil Storey; Safety-critical computer systems. ISBN: 0-201-42787-7
Laura L. Pullum; Software fault tolerance techniques and implementation. ISBN: 1-58053-137-7

Complementary Bibliography

M. Xie; Software reliability modelling. ISBN: 981-02-0640-2
Martin L. Shooman; Realiability of computer systems and networks. ISBN: 0-471-29342-3
Marvin Rausand, Arnljot Hoyland; System reliability theory. ISBN: 0-471-47133-X
The Motor Industry Software Reliability Association; MISRA-C 2004. ISBN: 0-9524156-2-3
John Knight; Fundamentals of Dependable Computing for Software Engineers, Chapman and Hall/CRC, 2011. ISBN: 978-1439862551

Teaching methods and learning activities

Theoretical classes will be based on the presentation of the most relevant case studies of Critical Systems. Theoretical-practical will be based on practical assignments to design and implement fault-tolerant software architectures. They will also be based on the analysis of confidence of Critical Systems.

Evaluation Type

Distributed evaluation with final exam

Assessment Components

Description	Type	Time (hours)	Weight (%)	End date
Attendance (estimated)	Participação presencial	52,00
	Exame	48,00
Examination	Exame	2,00	60,00
Practical work	Trabalho laboratorial	60,00	40,00
	Total:	-	100,00

Amount of time allocated to each course unit

Description	Type	Time (hours)	End date
	Estudo autónomo	78
	Total:	78,00

Eligibility for exams

To be admitted to exams students have to attain a minimum grade of 8 out of 20 in the continuous assessment component.

Calculation formula of final grade

2 practical assignments (design and implementation of software fault-tolerant architectures): 20% + 20% A written exam (closed book exam- 2.30h): 60%

Examinations or Special Assignments

Students have to do two assignments during the semester. The first is on software fault tolerance and the second is on verification and validation of software.

Special assessment (TE, DA, ...)

Students with a special status do not need to attend to classes. However, they have to do all the assignments and deliver them on the scheduled date. Students have to schedule meetings with the professors on a regular basis, so that professors can supervise the evolution of the work.

Classification improvement

Improvement of Final Grade: written exam at recurso (resit) season Improvement of Continuous Assessment: following year