Master Seminar: Summer Semester 2016
In the Summer Semester 2016 we offer a Master seminar “Software Engineering” (cf. 89-3372) on topics related to software technology.
We also offer a Bachelor seminar.
The seminar will start with a meeting on Wednesday, February 10th at 10:00 in room 34-420.
You can choose whether you want to start working on your topic in the lecture free time, or if you only want to work during the lecture period (starting April 18th).
Please register for the seminar via a short mail to Peter Zeller. The mail can be written in English or German and should include your name, student number, and your course of study (in particular: Bachelor or Master seminar?). Note that the number of places we can offer is limited.
This is a first draft of the schedule and is likely to change.
- February 10th at 10:00am: First meeting (room 34-420)
- Slides: intro.pdf
- Topics are presented
- You have until February 26th to choose your favorite topics
- February 29th: Topics will be assigned
- March 15th: First meeting with your supervisor
- June 15th: Submit reviewable draft of your paper (8-14 pages)
- June 15 - July 1st: Review two papers from other students
- July 8th: Final presentations 1 (10:00 to 16:45)
- July 11th: Final presentations 2 (10:00 to 16:45)
- July 22nd: Submit final version of paper
Discuss your individual time plan and intermediate deadlines with your supervisor at the beginning of the seminar.
A list of topics is available here. Please contact the corresponding supervisor, if you want to know more about a certain topic.
If you have any questions concerning our seminar please send an e-mail to Peter Zeller.
The goal of a seminar is to introduce students to the major constituent of scientific method that is concerned with critically reading, understanding, summarizing, explaining and presenting existing scientific papers. The following links present this goal in more detail: General guidelines for seminars in English and German. This seminar in particular provides the students opportunity to get acquainted with the research in software engineering.
You will get a scientific paper, which you will have to explain in a term paper (10-15 pages LNCS style, details are given below). Your paper should be understandable by an average master-level computer science student, so you usually have to provide more background information, than what is given in the original paper. In particular this includes a clear description of the problem, a good motivation, and an understandable representation of the solution proposed by the original paper. Your paper may also include critique of the of the original paper, if appropriate.
You will also present the paper to other students. This presentation will take 20 to 30 minutes with around 15 minutes for questions and discussions.
Successful participation in the seminar requires:
- Term Paper
- Term Paper Review
The master seminar has to be done in English.
Term paper (Preliminary and Revised Versions)
The term paper must be written in LNCS Style, a popular medium for efficient dissemination of new developments from all areas of computer science. We recommend to use LaTeX, but it is also possible to use Word.
The LaTeX template with instructions can be downloaded here (local copy). We provide an example on how to use the LaTeX template here. You can compile the example using the command
latexmk -pdf seminar.tex.
Your paper must be 10-15 pages long (including figures, references, etc.; however, you should not use big figures as space filler to get to 10 pages). Please supply the paper as a PDF file.
Here are some advice on writing your term paper in addition to the general guidelines:
- Mike Ashby. How to write a paper. April 2005
- Han Xiao. How to write a seminar report. January 2013
- Simon Peyton Jones. How to write a great research paper
Term paper review
- Each student reviews two term papers
- See Review Guidelines
Some bright people have given up their time to write some tips on how to do a presentation. As with other tips given on this page, we can’t encourage you enough to read them.