Database Technology Dat5/F9D/DE3/Inf7 Fall 2007
News
- A lecture from December 10 was reschedulled to December 6. It will take place in 0.2.11.
- Project presentation guidlines are added.
- Here are a few slides on what is expexted from the development and presentation of your Streamspin service.
Overview
In the Dat5/F9D/DE3/Inf7 course, we cover a mixture of classical and
emerging topics within database technology. This includes mobile
services, location-based services, business intelligence, and different aspects of database
performance, including indexing and query processing. In addition, the course introduces Streamspin, which is a new and innovative platform for delivering and recieving mobile services. During the course the students are expected to develop their own Streamspin services. 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 and Google
Scholar.
Schedule
Lectures are scheduled Mondays between 10.15 and 12:00 in 0.2.15. The table below contains the details 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.
- One presentation of a technical paper for each student.
- During the course each group is expected to develop and then present a Streamspin service.
- Presentations of projects by each of the group at the end of the course
Note that links to the papers can only be accessed from the university network!
Date |
Presenters |
Title (Reading material) |
2007-09-10 |
Christian S. Jensen |
Streamspin: Mobile Services for the Masses
|
2007-09-17 |
Kenneth H. Pedersen |
Service Development with Streamspin in Practice
|
2007-09-24 |
Torben B. Pedersen |
|
2007-10-01 |
Kristian Torp
|
|
2007-10-08 |
Simonas Saltenis
|
|
2007-10-22 |
Thomas Winterberg
Martin L. Kristiansen
|
|
2007-10-29 |
Claus H. Poulsen
Dennis B. Andersen |
|
2007-11-05 |
Christian W. Christiansen
Jan M. Johansen
|
|
2007-11-12 |
Donatas Saulys
Martin M. Larsen
|
|
2007-11-19
9:15 |
Martin M. Larsen
Anders Skovsgaard
Lars T. Sørensen
|
|
2007-11-26
9:15 |
Jan M. Johansen
Massih Mayeli
Claus H. Poulsen
|
|
2007-12-03 |
All groups |
|
2007-12-6
in 0.2.11 |
Kristian's group
Simonas' group |
|
2007-12-17
10:00 |
Christian's group
Massih Mayeli |
|
Presentation Requirements
The following is a list of requirements for the presentations. The requirements must be 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 simas [at] 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 Guidelines
The following is a list of guidelines for the presentations. The guidelines may
be adapted to the specific situation in which they are used.
- 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.
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.
A group has approximately 35 minutes to:
- 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
Best regards,
Christian S. Jensen, Torben Bach Pedersen, Simonas Saltenis, and Kristian Torp
Last updated Dec 18, 2007,
Simonas Saltenis