Teaching

Bachelor


Number ECTS Type WS SS Name
182.025 3.0 PS x x Grundlagen methodischen Arbeitens
182.064 6.0 VL
x Microcontroller
182.074 1.5 VO xx Grundlagen Microcontroller
182.090 4.5 SE xx Didaktik in der Technischen Informatik (not offered anymore)

Master


Number ECTS Type WS SS Name
182.087 3.0 VU   x Networked Embedded Systems
182.XXX3.0 VU x   Distributed Algorithms for Wireless Ad-hoc Networks

Grading


Whereas in most undergraduate courses grading is based on (more or less) objective measures (e.g., how many points a student gained on an exam), some undergraduate and many master courses use less objective measures for grading (e.g., the quality of a paper submitted by the student). Although most professors probably have their own system for grading, there are some general guidelines on how to derive grades, see the Leistungsbeurteilungsverordnung, LB-VO §14 (german).

As fas as practicals are concerned, I generally use the following guidelines to derive grades:

S1 (A): Great work! This really leaves no wishes open.
To get an S1, ensure that:
  • your system/program works
  • your system/program does what we need
  • we can use your system/program without any further modifications
  • you have tested your system/program thoroughly (and we can reproduce what you have done)
  • the documentation is complete, useful, and well written
  • you did the work without constant nagging from us and you did incorporate our wishes

U2 (B): Your work is good and quite acceptable, but not perfect. Some improvements could still be made, but we will most likely leave it as is.
Problems that will make your work U2:
  • your documentation is not complete or not written very well
  • some minor features we would have liked you to include are missing
Note: Most of the time, a U2 can easily be turned into an S1 just by following our suggestions to improve the work.

B3 (C): Your work can be used, but there are some problems. To be made truely useful, someone else will have to improve it.
Problems that will make your work B3:
  • the documentation lacks important information
  • (one or two) major features are missing
  • there are bugs in your design/code

G4 (D): Well, what can we say. Basically, it works, but this is definitely not what we were looking for. Needs major improvements to be made useful, and we are probably best off if we simply find another student to do it all over again.
Problems that will make your work U4:
  • you only implemented a small subset of what we wanted you to do
  • your documentation is not useful

N5 (F): You failed to produce something that at least works.
Problems that will make your work N5:
  • no documentation
  • design/program does not work
  • you did something that's completely different from what we wanted you to do