The tutorial will take place on Monday, 14:00-15:30, in Room T.04 Jakob-Haringer-Straße 2.
Tutors are Manuel Lankes and Peter Lindner.
You can contact them 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: algodat2024@cs.sbg.ac.at
21/03/2024: First programming assignment is out. Due date: 21/04/2024
08/05/2024: Second programming assignment is out. Due date: 16/06/2024
Please send an email to emilio.cruciani@plus.ac.at with the team information (first name, last name, student ID of each team member) to be registered as a team for the second programming assignment.
Guidelines
Procedure
The aim of the proseminar is to deepen and apply the content of the lecture Algorithms and Data Structures.
Participants are divided into three groups for the proseminar, which meet on different weekly dates (see above).
The work to be done for the proseminar consists of three parts: short tests, theory tasks, and programming tasks.
Short tests:
Every week, the material from the last two calendar weeks of the lecture 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 use Blackboard to indicate which tasks they have successfully completed by 12:00 noon on Wednesday of the week of the next proseminar date using a tick list.
In the proseminar, the tasks are then discussed by randomly selected students presenting the solutions to the tasks they have ticked on the blackboard.
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 three parts of the proseminar (short tests, theory tasks, programming tasks) each contribute one third to the overall grade.
Short tests:
10 points can be achieved for each test. The best 10 of the 11 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 ticked task is awarded one point.
Of the 11 question sheets for the semester, the best 10 will be evaluated.
This results in a maximum possible score of 30 points. If the board presentation of a ticked task is slightly incorrect or incomplete, it will be considered as not solved.
If the blackboard presentation of a ticked task is grossly incorrect or inadequate, all ticked tasks for the corresponding week will be considered as not solved.
Programming assignments:
10 points can be achieved for each of the two programming tasks.
This results in a maximum possible score of 20 points.
In addition to the correctness of the submitted program, the asymptotic running time and the asymptotic memory consumption are also evaluated.
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 each of these sub-areas, at least 40% of the points must be achieved in order to pass the course.
In addition, the following grading scale is used.