Wednesday, 15:00-16:30, HS I - Christian Doppler, Jakob Haringer Straße 2A
Tutorial
The tutorial will take place on Wednesday, 17:00-19:00, and Thursday, 17:00-18:00, in Room T.04 Jakob-Haringer-Straße 2.
Niklas Leon Draxl is responsible for the tutorial.
You can contact him at the following email address: tutorium_algodat@cs.plus.ac.at
Contact
If you have any questions about the course that do not concern the tutorial, please send them to the following email address: algodat2026@cs.plus.ac.at
The aim of the proseminar is to deepen and apply the content of the lecture Algorithms and Data Structures.
Participants are divided into four groups for the proseminar, which meet on different weekly dates (see above).
The work to be done for the proseminar consists of four parts: short tests, theory tasks, short presentations and programming tasks.
Short tests:
Every week, the material from the last two calendar weeks of the lecture and proseminar is tested in short 10-minute tests.
Theory assignments:
For the theory tasks, a task sheet with three tasks is posted online every week on Wednesday after the lecture.
Students must upload their successfully completed tasks via Blackboard by 13:00 noon on Wednesday of the week of the next proseminar session and tick them in a list. Ticked tasks will be randomly checked for correctness.
Short presentations:
For each theory task, one student is selected to present a completely prepared solution on the board. TThis student is chosen during the previous week's seminar.
Programming assignments:
In the course of the semester, two programming assignments are set to implement and test algorithms and data structures from the lecture.
The processing time for each programming assignment is four weeks.
Java is used as the programming language.
The source codes of the programs are submitted via a submission platform by 12:00 noon on the day of submission.
The first programming assignment must be completed individually by all students.
For the second programming assignment, it is permitted to work together in teams of three; the collaboration must be noted in the source code and all team members must submit the identical source code.
For teams in which one member has already worked on the assignment in one of the previous years, it must be documented to what extent the contribution of the other members is at least one third.
Registration and deregistration
Registration for the proseminar via PLUSonline is required.
Observe the university guidelines to avoid a negative degree due to late deregistration.
Assessment
The four parts of the proseminar contribute to the overall mark in the following proportions:
30% short tests,
30% theory tasks,
10% short presentations,
30% programming assignments.
Short tests:
10 points can be achieved for each test. The best 10 of the 12 short tests of the semester are scored individually. This results in a maximum possible score of 100 points.
Theory assignments:
There are three tasks to be solved for each task sheet and each submitted task is awarded one point.
Of the 12 question sheets for the semester, the best 10 will be evaluated.
This results in a maximum possible score of 30 points. If the solution of a submitted and ticked task is slightly incorrect or incomplete, it will be considered as not solved.
If the solution of a submitted and ticked task is grossly incorrect or inadequate, all tasks for the corresponding week will be considered as not solved.
Programming assignments:
3 points can be achieved for each of the two programming tasks.
This results in a maximum possible score of 6 points.
Points are awarded based on automatically performed tests.
For the programming tasks, each team or individual must create an independent solution.
The literature and other sources used when creating the solution must be stated as comments in the source code.
Copying source code when creating the solution is explicitly not permitted.
Plagiarism presented as your own achievement will result in a grade of 0 points.
In addition, poor readability of the source code can be penalized with points deducted due to disregard of usual programming conventions.
In the sub-areas short tests, theory assignments and programming assignments, at least 40% of the points must be achieved in order to pass the course.
In addition, the following grading scale is used.