The information on this page may be subject to changes during the run of the semester.

Lectures

Tutorials

Please see your individual calendar for the exact date.

Programming Projects

The projects are submitted in teams of two students (in exceptions: three). Each submission consists of source code, report, and screen recording. A zip-archive with the following structure (replacing X by the appropriate number) should be submitted to itslearning:

projectX/
projectX/report/
projectX/sources/
projectX/video/

• source code: submit the source code of the project. If the project requires you to start with a codebase, for example the linux kernel, then only include the files you have changed (using the original directory structure).
• report: submit a pdf (5-10 pages) describing your solution and decisions in English language, if applicable explain what problems have occurred and possible limitations of solution. Should not contain full source code. Can be written for example in LaTeX, OpenOffice, or Microsoft Word. The report must include at least: a small introduction; a description of the design decisions you have made; a description of your implementation (here, it is fine to use snippets of interesting code, where you explain what you have done); a description and motivation of the tests you have made to verify that your solution works in both valid and invalid usage; a small conclusion.
• screen recording: in this recording you show that your implementation is working correctly. During the session you should also perform all or some of the tests that you described in your report. In your report you should refer to the tests you performed by giving the precise time in the video file. The recorded session should be maximally 5 minutes long and have a maximal size of 50MB. For recording the desktop session you can e.g. use Zoom (which is probably easiest) or the tool gtk-recordmydesktop. The video does not need to include any audio, and if the text in the command line you are using is readable, the quality is good enough. Make sure that the video format is a standard video format (such that mplayer or VLC can play it).

If the submission deviates significantly from these requirements, it will be considered as not submitted.

Grading is done according to the following rubric. Different criteria are weighted differently. If one or more criteria are graded with needs improvement, a resit (second try) has to be done for the project.

Exam, grading, and repeat students

There is a written exam at the end of the course (June 13th for first try and August 6th for second try). The exam counts as 80% of the final grade with the remaining 20% coming from the the programming projects. Both parts have to be passed.

The topics of the exam are the following:

• The book chapters mentioned in the lecture list restricted to content discussed in lectures and exercise sessions (see slides and exercise sheets).
• Exam exercises comparable to those on exercise sheets
• One exercise to test rudimentary knowledge of topics from programming projects

Repeat students who have participated in the course in previous years will need to submit the projects again. In case they want to reuse their own submissions from the previous year (adapted to the changes if necessary), they should submit it alone.