Didactic Concept
Weekly lectures give an overview of foundations of the subject matter as well as background information. Weekly programming tasks have to be solved in small teams (3 team members). To achieve the goals it is important that students find their own individual approaches; the way to the solution is more important than the solution itself.
ECTS Breakdown
(3 ECTS is 75 hours)
- 49.7 h - Working on 9 programming assignments
- 00.3 h - Discussion of programming assignments (interview)
- 00.7 h - Introduction to the lecture
- 09.8 h - Lecture time
- 14.2 h - Preparation for exam
- 00.3 h - Oral exam
Registration
You have to register for the course as well as for one of the many groups named oopXn, where X is a letter in the name of the mentoring tutor and n a consecutive number. All other groups shown here will be used in January to arrange interview dates. Exact dates for interviews and exams will be subject to change until January.
German
The course is given in German. The German version of this page contains more detailed infomation than the English one. Please press the "Deutsch" button.
The grade depends (one half each) on the achievements when solving programming tasks in a team (this is the exercise part) and the result of an oral exam (this is the lecture part). To get a positive grade for this course it is necessary to get positive grades for both, the exercise part and the lecture part. It is recommended to take the oral exam soon after finishing the exercise part. Oral exams must be positively taken until June, otherwise a negative certificate will be issued. A negative certificate will also be issued if the lecture part or two trials to take the oral exam result in a negative grade.
A negative oral exam can be retried at most once within the given time frame (until June) before a certificate is issued.
Grade of the exercise part
Teams get e-mails with feedback on the quality of their solutions of programming tasks about one or two weeks after the deadlines. However, such feedback is not a final assessment of a programming task. The grade of the exercise part is determined at an interview meeting in January. Beside the quality of work delivered by the team the grade also considers efforts and achievements as an individual team member. To find out the performance as a team member it is necessary to understand own solutions and justify own decisions during the interview.
A point system is used to assess solutions of programming tasks. To assess the entrance phase (constisting of the first three programming tasks) tutors suggest between 0 and 100 points depending on timeliness, completeness and correctness (also for reactions on requests to eliminate specific problems in the program code). For each of the remaining six tasks the supervisors award up to 100 points depending on the quality (based on quality criteria specified in the tasks). However, if students need additional time to solve a task and supervisors agree to extend the deadline by one week (Fristerstreckung), the points are reduced to 2/3 of the points that would have been awarded otherwise. Up to 700 points can be achieved over all. They correspond to the following grades:
- 000 - 350 points -> 5 (negative)
- 351 - 437 points -> 4
- 438 - 525 points -> 3
- 526 - 612 points -> 2
- 613 - 700 points -> 1
As described above, these points and grades are only preliminary until the interview meeting and can be changed during the interview meeting.
Please see the changed conditions for exams (online exams) in German.
The script is available in the Documents section. The two available versions differ in the format, not in their contents.
Programming assignments and lecture slides will also be put into the Documents section at the specified dates for assignments, and after the lectures, respectively.
