Subject

Software Engineering for Critical Systems

Course Title

Software Engineering for Critical Systems
Software Engineering for Critical Systems

Code

m23_s_020

Study Programme

—

Organizer of the study programme (unit, institute, department or division)

Faculty of Computer Science and Engineering

Degree level (first, second, third cycle)

Second cycle

Academic year / semester

10 / Summer

Number of ECTS credits

Teacher

Magdalena Kostoska Gjorgchevska

Prerequisites for enrolling in the course

—

10.

Objectives of the course programme (competences)

This course introduces the concepts and methods for the development of “critical systems” – systems whose failure can result in endangering lives, the environment, or the survival of a business. It is important that critical software not be viewed in isolation but as part of a larger system that includes hardware, software, people, and processes. Upon completion of the course, students will be able to: understand the basic representations of dependencies in software, perform analysis, analyze the infrastructure and its threats, develop critical software, and be familiar with existing global standards.

11.

Course content

Safety and risk analysis, Identification of potential problems, Analysis of requirements for critical systems, Design principles for critical systems such as redundancy, Architecture design with regard to reliability, sustainability, and support, Development of critical systems with evaluation, Standards, Organizational aspects, Role of human error.

12.

Learning methods

Lectures supported by slide presentations, interactive lectures, practical classes (using equipment and software packages), teamwork, case studies, guest lecturers, independent preparation and defence of a project assignment and seminar paper, and learning in an electronic environment (forums and consultations).

13.

Total available time

6 ECTS x 30 hours = 180 hours

14.

Distribution of available time

60 + 0 + 45 + 45 + 30 = 180 hours

15.

Forms of teaching activities

15.1.	Lectures - theoretical instruction	60 hours
15.2.	Exercises (laboratory, auditory), seminars, teamwork	0 hours

16.

Other forms of activities

16.1.	Project assignments	45 hours
16.2.	Independent assignments	45 hours
16.3.	Home study	30 hours

17.

Assessment method

17.1.	Tests	0 points
17.2.	Seminar paper / project (presentation: written and oral)	45 points
17.3.	Activities and learning	0 points
17.4.	Final exam	0 points

18.

Grading criteria (points / grade)

up to 50 points	5 (five) (F)
from 51 to 60 points	6 (six) (E)
from 61 to 70 points	7 (seven) (D)
from 71 to 80 points	8 (eight) (C)
from 81 to 90 points	9 (nine) (B)
from 91 to 100 points	10 (ten) (A)

19.

Requirement for obtaining a signature and taking the final exam

completed activities

20.

Language of instruction

Macedonian and English

21.

Method for monitoring the quality of teaching

internal evaluation and survey mechanism

22.

Literature

22.1.	Required literature 1. Perrow, C \| Normal Accidents: Living with High-Risk Technologies \| Princeton University Press \| 1999 2. Leveson, N.G. \| Engineering a Safer World \| MIT Press \| 2011 3. Roland, H.E. and Moriarty, B. \| System Safety Engineering and Management (2nd ed) \| Wiley \| 1990 4. Ian Sommerville \| Software Engineering, 9th edition \| Addison Wesley \| 2011
22.2.	Additional literature No. Author Title Publisher Year