Seminar: Summer Semester 2019

In the Summer Semester 2019 we offer a Bachelor and Master seminar “Software Engineering” (cf. 89-3311 and 89-3372).

Organization

You can apply for the the seminar via e-mail to Peter Zeller. Please use the subject “Registration Software Engineering Seminar” and include the following information in your mail:

  • Your name
  • Course of study (Bachelor CS, Master CS, EMSE, …)
  • List of planned and completed courses

Usually we have more students than available seminar places. We will assign the available seminar places after the registration deadline and will then notify you via mail.

Schedule

  • Registration deadline: March 18
  • Kickoff Meeting: Wednesday, April 17, 11:45-13:15, room 11-260 (Slides: Introduction, Latex Tutorial)
  • Submit introduction: Monday, May 13, 23:59
  • Submit first draft of paper: Monday, June 17, 23:59
  • Presentations: Wednesdays, 11:45-13:15, room 11-260
    • June 5:
      • Argus
    • June 12:
      • Futures and Promises
      • Mozart
    • June 19:
      • Actors in Scala
      • Orleans
    • June 26:
      • Publish/Subscribe
      • Distributed Reactive Programming
    • July 3:
      • Cloud Haskell
      • IronFleet
    • July 10:
      • DISTALGO
      • PaRiS
    • July 17:
      • P: safe asynchronous event-driven programming
      • Delta CRDTs
  • Final paper: Fri, July 19, 09:00 (in the morning)

Deadlines are strict: Failing to submit a document by the end of the deadline-day means failing the seminar.

Attendance and active participation on all presentation days is mandatory.

Topics

The topic of this seminar is “distributed and concurrent programming”. Check the detailed list of topics for more information.

Contact

If you have any questions concerning our seminar please send an e-mail to Peter Zeller.

General Remarks

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 minutes with around 10 minutes for questions and discussions.

Successful participation in the seminar requires:

  • Term Paper
  • Presentation

Language

The seminar has to be done in English.

Term paper

You have to officially submit three versions of your paper.

  1. Extended abstract:

    An abstract is a short (often 100-250 words) summary of a paper, which helps potential readers to decide, whether they should read a paper or not. An abstract often has 4 parts:

    1. A motivation/problem statement, which explains what the topic and scope of the paper is and what problem it tries to solve.
    2. A brief statement about what approach/methods were used to address the problem.
    3. A summary of the results of the paper, which show the reader what was achieved.
    4. A conclusion which summarizes the contributions/usefulness of the results.

    The extended abstract you should write is similar but longer (at least 2 pages). You should focus on the motivation and problem statement and the main ideas of your topic, but you don’t have to go into technical details yet. The extended abstract can later be reused to write the introduction to your paper.

    You should discuss with your supervisor what exactly should go into the extended abstract.

  2. First draft:

    This should be a full paper including everything you want to have in the final paper.

  3. Final paper:

    You will get feedback about your first draft, which you have to incorporate into the final version. Depending on the quality of your first draft, this can range from making a few changes to rewriting the complete paper.

Style

The term paper must be written in LaTeX and use the style “SeminarReport” from the computer science department:

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 submit the paper as a PDF file.

Here are some advice on writing your term paper in addition to the general guidelines:

Presentation

You are free to use your favorite program and style for creating your presentation slides. If you want to use the official university style, you can use the respective Latex template or Powerpoint template.

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.