Syllabus
Registration via LPIS
| Day | Date | Time | Room |
|---|---|---|---|
| Tuesday | 10/06/26 | 09:30 AM - 01:30 PM | TC.2.03 |
| Tuesday | 10/13/26 | 09:30 AM - 01:30 PM | TC.2.03 |
| Tuesday | 10/20/26 | 09:30 AM - 01:30 PM | TC.2.03 |
| Tuesday | 10/20/26 | 02:00 PM - 04:00 PM | TC.4.01 |
| Wednesday | 10/21/26 | 10:00 AM - 12:00 PM | LC.2.064 (P&S) |
| Tuesday | 10/27/26 | 09:30 AM - 01:30 PM | TC.2.03 |
| Tuesday | 11/03/26 | 09:30 AM - 01:30 PM | TC.2.03 |
| Tuesday | 11/10/26 | 09:00 AM - 02:00 PM | TC.3.05 |
| Tuesday | 11/10/26 | 02:15 PM - 03:15 PM | D5.0.002 |
| Thursday | 11/12/26 | 02:00 PM - 04:00 PM | D5.1.004 |
| Tuesday | 11/17/26 | 10:00 AM - 12:30 PM | TC.0.02 |
This course focuses on the development and operation of software-based systems, including cyber-physical systems. After an introduction and recap, the course will discuss software failures and their consequences (selected examples, reasons for software failure, if and how generative AI might help). Subsequently, the course discusses established concepts, standards, techniques, and methods for building complex, reliable, resilient, secure, safe, and maintainable software systems. Topics include:
- the specification of a complete, correct, unambiguous, and testable requirements document (requirements engineering)
- the verification of software artifacts, e.g. via different software testing techniques
- the specification of system and software architectures
- the model-based design of software-based systems
- the organisation of engineering and systems operation activities
The role of modern approaches to automation, including LLMs and so-called AI agents, will be addressed for each topic as a cross-cutting concern.
Students will have the opportunity to engage with guest speakers from leading technology companies, including LieberLieber Software GmbH and SparxSystems (Enterprise Architect).
This course assumes knowledge of the topics discussed in the mandatory "Foundations of Digital Economy" course. Prior knowledge of one or multiple of the following topics can be helpful but is not formally required: basic knowledge of a programming language (e.g. Python or Java), basic knowledge of a software modeling language (e.g. the Unified Modeling language, UML; Entity-Relationship models, ER), basic knowledge of the software engineering process (development cycle).
Upon successful completion, students will be able to:
- Describe the sources of failure for software-based systems;
- Understand how software failures can be avoided;
- Understand how (generative) AI can assist software engineering tasks;
- Describe and explain the methods, techniques, and tools for:
- the specification of a requirements document
- the verification of software artifacts
- the specification of system and software architectures
- the model-based design of software-based systems
- the organisation of engineering and systems operation activities
- Describe and compare architectural decisions on software-based systems;
- Describe and, to some extent, apply tools for model-based system design;
- Summarize and critically reflect on related scientific literature;
According to the examination regulation, 80% attendance is required for this course. This means that absence in one unit is tolerated. Beyond that, a reason must be given in accordance with WU's examination regulation. Any absence must reported as soon as possible. The standard way for reporting an absence is an email to the course's contact address. Physical attendance is mandatory for all exams (quizzes, final exam).
The course is delivered using a combination of the following:
- lectures and presentations of the main course topics (see above);
- live demonstration of software tools;
- self-study of the course materials (handouts, mandatory reading articles);
- 2 in-class exams (quizzes) counting for 20 points each;
- 1 final exam counting for 60 points;
- A positive grade is awarded if at least 50% of all points (i.e. 50/100) are earned. The remaining grades are awarded in 10% steps (60%, 70%, 80%). Thus, a "1, excellent" is awarded if at least 80% (i.e. 80/100) of all points have been earned.
- Each student who participates in at least one of the 3 exams will be graded.
- If a student fails the course (i.e. finishes with a negative grade), the student will be allowed a single repeat of the final exam, given the following conditions hold:
- the student earned at least 15/40 points from the in-class exams;
- and the student earned at least 15/60 points from the final exam.
- If one or both of the above conditions are missed, students will have to repeat the course (incl. all exams) in a subsequent semester.
- If a student fails the course (i.e. finishes with a negative grade), a repeated final exam (see above) can at most result in the lowest passing grade.
- All candidates eligible for repeating the final exam will be notified via e-mail after the grading procedure of all regular exams has been completed.
- Winter term 2026/27: The repeat of the final exam is scheduled for March 3rd 2027 (this is a fixed date which cannot be moved or adjourned).
Please log in with your WU account to use all functionalities of read!t. For off-campus access to our licensed electronic resources, remember to activate your VPN connection connection. In case you encounter any technical problems or have questions regarding read!t, please feel free to contact the library at readinglists@wu.ac.at.
Back