Bachelor/Master Seminar

In this seminar, students preparing a bachelor or master thesis in software engineering meet weekly to present and discuss their latest results. If you want to do a thesis in our group, you have to attend this seminar or one in another group.

Talks

General Information

Rules

You need to:

• do the usual stuff like find an advisor, find a topic, read the literature, write a thesis proposal, etc. (this is not part of the master seminar itself).
• attend the seminar at least 10 times. Your attendance can start at any time and need not be completed within a single semester.
• give a talk where you explain your plans for the thesis (basically this means presenting the contents of your proposal).
• submit the thesis in the semester after you got the seminar schein. If you fail to do so, you need to attend another master seminar (probably at another chair) before you can start another thesis.

The first time you show up at the master seminar, you email address will be added to the mailing list, and you will get an notification email before each upcoming session.

After getting the Schein, students need to register their thesis at the Prüfungsamt.

Requirements

Although the thesis proposal is not part of the master seminar itself, we require a proposal to contain:

• Explicitly state verifiable hypothesis
• Explain details on how to verify hypothesis (experiments, measures, ...)
• Name potential risks and approach to treat them
• Contain a time schedule
• Length > 5 pages
• Must-have criteria: Things your thesis must cover to be successful
• May-have criteria: Things your thesis can cover to improve its value
• Must-not-have criteria: Things your thesis will not cover (although one may think so)

A presentation of such a thesis proposal must meet the following requirements:

• length about 20 minutes
• plus 10 minutes for questions

If you have questions, do not hesitate to ask Christoph Mallon