Master and Bachelor Seminar: Winter Semester 2013/2014

In winter semester 2013/14, the research groups

offer a Master and Bachelor seminar on topics in software engineering (cf. 89-3372/89-3311).

Update

  • First topic allocation meeting: Thursday, 18 July 2013, 17:15, Room 34/420
  • Kickoff meeting: Thursday, 24 October 2013, 17:15, Room 32/349
    Warning All interested students including those who have topics must attend this meeting.

    The seminar introduction slides is available here.
  • Deadlines:
  • Warning All documents must be sent to your supervisor and Ilham Kurnia. Deadlines will be strictly enforced.
    The time plan for the deadlines distributed in the kickoff meeting can be downloaded here (updated with the slides deadline).
  • The presentation will be held on 13–14 February 2014. The timetable for presentation is to available below.
  • The certificates are now available from AG Softech secretary, Judith Stengel.

Submissions

The following table lists the submission status of each participating student.

Topic # Student Table of Contents Preliminary Version Reviews Papers # Reviewed by * Final Version * * Slides *
4 Sebastian Lutsch yes yes 20 yes, 22 yes 9, 18 yes yes
5 Zheyao Dai yes yes 19 yes, 21 yes 14, 23 yes yes
7 Malik Mlitat yes yes 9 yes, 10 yes 19 , 21 yes yes
9 Tobias Lutz yes yes 4 yes, 18 yes 7, 10 yes yes
10 Panagiotis Giokoglou yes yes 9 yes, 18 yes 7, 19 yes yes
11 Christopher Stangohr yes yes 13 yes, 17 yes 8, 13 yes yes
13 Luc Francois yes yes 8 yes, 11 yes 11, 17 yes yes
14 Matthias Koch yes yes 5 yes, 23 yes 20, 22 yes yes
17 Yannick Schott yes yes 8 yes, 13 yes 8, 11 yes yes
18 Simon André Scherr yes yes 4 yes, 22 yes 9, 10 yes yes
19 Sebastian Fuchs yes yes 7 yes, 10 yes 5, 21 yes yes
20 Santiago Castiñeira yes yes 14 yes, 23 yes 4, 22 yes yes
22 Agus Hartoyo yes yes 14 yes, 20 yes 4, 18 yes yes
6 Abhijot Singh Mann yes
15 Nils Richter yes
23 Muhammad Asif Iqbal yes yes 5, 21 14, 20
21 Razan Jaber yes yes 7 yes, 19 yes 5, 23 yes
12 Elleni Eyob yes
8 Xavier Hofmann yes yes 11 yes, 17 yes 13, 17 yes

Presentation Schedule

The following table lists the presentation schedule. All presentations will take place at Room 32/349 (the same room as the kickoff meeting).

Day Time Presenter Talk
13-Feb 09:30-10:40 Seminar organizer Introduction
^ ^ Zheyao Dai Applying the Repertory Grid Technique to User Experience Engineering
^ ^ Tobias Lutz Software Architecture Knowledge Management: Foundation Concepts and Recent Developments
^ 10:40-11:00 Break
^ 11:00-12:05 Matthias Koch Business Process Models vs. Goal Models for Elicitation of System Requirements
^ ^ Santiago Castiñeira Conflict-Free Replicated Data Types
^ 12:05-14:00 Lunch time
^ 14:00-15:05 Agus Hartoyo Patterns for Program Generation
^ ^ Sebastian Fuchs Statically Safe Program Generation with SafeGen
^ 15:05-15:25 Break
^ 15:25-16:30 Panagiotis Giokoglou Preprocessor Code Usage and Analyses
^ ^ Sebastian Lutsch Purity Analysis for Java
14-Feb 09:00-10:05 Malik Mlitat Analysis of the Scaled Agile Framework
^ ^ Simon André Scherr Agile Software Development in Embedded System
^ 10:05-10:25 Break
^ 10:25-11:50 Yannick Schott Actors and Distributed Programming in Java/JCobox
^ ^ Luc Francois Actors and Distributed Programming in Scala
^ ^ Christopher Stangohr Repleo: A Syntax-Safe Template Engine

Seminar Topics

The following table presents the list of topics on offer (which will be updated as more topics become available) and the respective supervisor. Students are advised to contact the supervisor of their topic of choice as soon as possible because the topic allocation principle is first-come-first-serve. When the “Student” field in the table below contains an entry, it indicates that the corresponding topic has already been chosen and is no longer available to other students.
Warning A student may not apply for two or more topics simultaneously.

The following table presents the list of topics on offer for this semester, the respective supervisors and the students to whom the topics are allocated to.

# Topic Supervisor Student
4 Purity Analysis for Java (Master) Mathias Weber Sebastian Lutsch
5 Applying the Repertory Grid Technique to User Experience Engineering (Master) Andreas Maier Zheyao Dai
6 Large and Complex Software Evolution: Approaches and Evaluation (Master) Mohammed Abufouda Abhijot Singh Mann
7 Analysis of the Scaled Agile Framework (Master) Balthasar Weitzel Malik Mlitat
8 Using Abstract Languages in Software Engineering (Bachelor) Ilham Kurnia Xavier Hofmann
9 Software Architecture Knowledge Management: Foundation Concepts and Recent Developments (Master) Dominik Rost Tobias Lutz
10 Preprocessor Code Usage and Analyses (Master) Bo Zhang Panagiotis Giokoglou
11 Repleo: A Syntax-Safe Template Engine (Bachelor) Malte Brunnlieb Christopher Stangohr
12 Accomplishments and Research Challenges in Meta-programming (Master) Malte Brunnlieb Elleni Eyob
13 Actors and Distributed Programming in Scala (Bachelor) Ilham Kurnia Luc Francois
14 Business Process Models vs. Goal Models for Elicitation of System Requirements (Master) Norman Riegel Matthias Koch
15 Actors and Distributed Programming in Erlang (Bachelor) Christoph Feller Nils Richter
17 Actors and Distributed Programming in Java/JCobox (Bachelor) Mathias Weber Yannick Schott
18 Agile Software Development in Embedded System (Master) Philipp Diebold Simon André Scherr
19 Statically Safe Program Generation with SafeGen (Master) Malte Brunnlieb Sebastian Fuchs
20 Conflict-Free Replicated Data Types (Master) Ilham Kurnia Santiago Castiñeira
21 Geo-Replicated Storage Systems (Master) Prof. Dr. Arnd Poetzsch-Heffter Razan Jaber
22 Patterns for Program Generation (Master) Malte Brunnlieb Agus Hartoyo
23 The Level of Interoperability of Web Services (Master) Hadeel Abukwaik Muhammad Asif Iqbal

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.

Successful participation in the seminar requires:

  • Term Paper
  • Term Paper Review
  • Presentation

Term paper (Preliminary and Revised Versions)

  • Master students: Approximately 15 (fifteen) pages (excluding table of contents, title page, references, figures)
  • Bachelor students: Approximately 10 (ten) pages (excluding table of contents, title page, references, figures)

The term paper must be written in LNCS Style, a popular medium for efficient dissemination of new developments from all areas of computer science. The LaTeX template with instructions can be downloaded here (local copy), while the Microsoft Word template is available here (local copy).

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

Term paper review

  • Each student reviews two term papers
  • A review contains
    • Title of the reviewed paper
    • Summary
    • Comments to the author
    • Positive and negative aspects
    • At least 400 words (that is, at least 1 page)
  • The reviews must be submitted as plain text files whose names are as given in the email sent to the student.

The following links provide some guidelines how the review should be done. Although they are geared more towards paper reviews in a scientific conference/journal setting, many of the reviewing concepts are still applicable in this review task.

Presentation

Every student must give a presentation on his topic. The time structure of a presentation is listed below.

  • 20 min. presentation for Master students (hard deadline!)
  • 15 min. presentation for Bachelor students (hard deadline!)
  • 10 min. Q & A and comments on presentation style

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.

The general seminar guidelines also contain good tips.

How to fail a seminar

  • Plagiarism
  • Non-observance of deadlines
  • Non-observance of compulsory attendance
  • Poorly written term paper (e.g. failed scope)
  • Superficial reviews
  • Bad presentation
  • No participation at discussion rounds

On the topic of plagiarism: here are some sources to help you avoid plagiarizing the work of others: 1, 2, 3, 4.

Contact

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

Previous Seminars

Below are the links to homepages of several previous seminars. More links are available from ELSA (use the search tool with the search term “Seminar: Software Engineering”). Valuable tips can also be obtained from these sites.