Database Technology dat5/F9D/KDE3/Inf7/SW9 Fall 2010

News

• 2010-08-31: Page up and running

1 Overview

In the course, we cover a mixture of classical and emerging topics within database technology. This includes mobile services, location-based services, business intelligence and database performance. The course will consist of 15 seminars.

A high degree of interaction and frequent discussions will be encouraged. It is expected that you attend all sessions, read the papers for each session, and are able to pose questions to the presenters about the papers (see note about the opponent system below). Note that it may in some cases, e.g., when presenting a paper yourself, be necessary to read additional papers referenced by your paper in order to fully understand your own paper. A good place to find papers is the DBLP online bibliography.

2 Schedule

Lectures are scheduled Thursday between 10.15 and 12:00 in room 0.2.11. The table below contain thedetails about the preparation for the seminars.

The course consists of following parts.

• Presentations by the supervisors. This provides an overview of the course and some of the issues covered in the course.
• Two presentation of a technical paper for each student.
• One presentation from each group with the results from the current semester and the future work on the next semester.

Presentation Requirements

The following is a list of requirements for the presentations. The requirements mustbe followed, unless specific permission is given by the course teachers.

• The total time spent on a presentation is about 35 minutes. This means that the presentation must be rehearsed beforehand to get an estimate of the time spent, and the necessary modifications made afterwards. It is important to actually say out loud all words of the presentation. Only this way is it possible to get a good feeling for the length of the talk and to identify trouble spots in the presentation that need further work. After the presentation, we will spend about 15 minutes on discussing the paper and the presentation.
• The presentations must contain concrete examples. It is often time-consuming and difficult to construct good, specific examples, but the time spent on this is well spent. Important observations that the listener should definitely understand are prime candidates for exemplification.
• The presentation must be shown to the project supervisor 72 hours before the course presentation, and any modifications required by the supervisor must be made to the presentation.
• The slides must be sent to torp@cs.aau.dk  after the presentation. They will then be put on the web page.
• Each student must present 1 paper.
• Each student must be the opponent for two paper presentations. The opponents read the paper particularly carefully and are required to be able to ask detailed questions about the paper and discuss it in a detail.
• Additionally, each student must participate in one of the following activities: a) presenting a demo of the prototype developed in the project, b) presenting the results of the DAT5 project, or c) giving a presentation on how to present papers.

Presentation Checklist

General

• Is it clear where the paper was published and by whom?
• Are there unique slide numbers on all slides (to have something to refer to during the discussion)?
• Is the minimum font size should be 20 points the listeners could be short-sighted?
• Does the talk have a concrete motivating example very early?
• Are unfamiliar abbreviations introduced and used appropriately?
• Is the main problem addressed in the paper clearly stated?
• Does the presentation have concrete and minimal examples of core ideas?
• Is the relationship to your project stated (it is is relevant)?
• Are dynamics, e.g., searching a tree presented using animation techniques?
• Are the listeners background use appropriately, e.g., no need to tell what an array is, however must tell what the XY++-Tree is?
• Is white-space used appropriately (too much, too little)?
• Is it clear when the talk is done?
• Is there a reasonable number of slides in total in the presentation?

Figures

• Are complicated figures presented in sufficient details?
• Are the symbols used in the figures clear to the listeners?

Performance Graphs

• Is data, queries, modification, and transactions appropriately introduced?
• Are the axis on performance graphs clearly explained?
• Are the main conclusion from the graph clearly stated?
• Is there only one graph per slide (or are graphs compared)?

Critique

• Is the critique relevant and fair?
• Is the critique balanced?
• Is the critique points concrete, i.e., not "it is a good paper"?

During the Presentation

• Is the presentation done without standing with papers in the hands?
• Does the speaker face the audience?
• Is the hand-waving at an appropriate level (too much => should figures be used)?
• Is the stick used appropriately?
• Is time used appropriately (talk not too short or too long)?

Presentation Guidelines

• Make sure that the presentation has a simple structure and that the listener understands and is able to follow the structure during the presentation. There should probably be an overview slide at the beginning and a talk summary/conclusions slide at the end. It may be useful to remind the listener of the structure during the presentation. The outline of the presentation can also be written on the board, where it can be pointed to throughout the presentation.
• It is often a good idea to divide a presentation into three separate parts. The first part should present the material without criticism, but be as faithfully to the authors as possible. The second part then relates the material to a) related work, e.g., as presented on DAT5 and b) your DAT5 project. The third part evaluates both form and content of the presented material, i.e., good and bad points. A self-evaluation of the presentation is also possible. The time spent on these parts should be about 28, 4, and 3 minutes, respectively (give or take a few minutes).
• Do try to use figures effectively. Although these can take some time to draw and although it may take some time to do them exactly right, they can be very effective in communicating the most important points of a presentation.
• Rehearse the presentation in front of an audience before the exam.
• Make sure that the slides are easy to present. If some transitions between slides are difficult to remember then the slides should probably be revised. Again, the way to identify problems is through saying all the words out loud.
• Do number the slides; this makes it easier for the listeners to later refer to them.
• For the exam, it is a good idea to have everything on the slides so that there is no need to draw spontaneous pictures on the board.

Exam Requirements

The exam requirements.

Project Presentation Guidelines

The following is a list of guidelines for the presentations of your projects for the other groups and advisors at the end of the course. The guidelines may be adapted to the specific situation in which they are used. The groups has approximately 35 minuets for present the

• Present the specific topic that the group is working on.
• Present the motivation for working on this topic.
• Provide the necessary background such that the other groups and advisors can understand the topic you are working on
• Discuss the most relevant related work.
• Present the status of the project. What will be in the project report that you hand in for evaluation.
• State clearly the contributions of your work.
• Discuss shortly what you will working on for the next semester. What are the best directions of future research?
• List 3-5 questions/topics where you would like feedback from the other groups and advisors