In seminars, you will work on weekly iterations to practice everything you have learned. Your seminar tutor is present in the lab to help you with these assignments.
Seminar attendance is mandatory. Unfortunately, there have been too many situations with people submitting sub-par solutions due to their absence from the seminar. Moreover, these people usually had problems finishing team projects, bringing their whole teams down.
Weekly ROPOTs will serve as proof of attendance. This means that the ROPOTs can only be taken physically during the seminar. They will test the crucial knowledge gained from the lecture necessary for the seminar to move forward.
There are thirteen seminars during the semester. Out of these thirteen seminars, you can have four unexcused absences. If you have more unexcused absences, you will automatically be awarded the X mark. For each seminar, there will be one ROPOT worth 0.4 soft points. These points may help you get a better grade after reaching the 70-point threshold (For credit type of course completion, these points serve as hard points).
The first seminar's ROPOT is comprised of questions from the organizational information from the Interactive Syllabus, as many of the seminars during the first week occur before the lecture.
During the seminars, the teacher works on a demo project, similar to the iterations you receive each week. Students can pay attention to the seminar demo and ask questions, or they can work on the weekly iteration.
Almost all iterations are independent of each other. You can choose to skip an iteration and work on another one (if they are independent of each other). We advise you to finish most of them, as they are an invaluable learning resource for your team projects and your final exam.
After finishing an assignment, you will send it to your teacher for review. Sending the solution is not tied to the seminar. You can work on your solutions outside the seminar too. Many iterations will require some time to complete. Your teacher/code reviewer will grade you with points for finished work according to the quality of your submission. The concrete way of assigning someone to review your code will vary from seminar to seminar. You will receive concrete information for your seminar group during your first seminars.
After the first review, you will receive a suggested evaluation from your teacher. If you are satisfied with your score, you can ask your code reviewer to finalize your evaluation. You can also work on your assignment again to correct mistakes / bad practices found by your code reviewer. After eliminating the found issues, you can hand in the solution once more. The evaluation after the second submission is final.