This course will be given 2011/2012.
The course will give an introduction to pervasive systems, with a focus on reading overview papers and systems papers. The course is divided into a number of course items, each with a number of articles to read.
- Görel Hedin, gorel AT cs.lth.se
- Boris Magnusson, boris AT cs.lth.se
For each course item, all participants will read a number of articles, and prepare for discussion by noting down:
- A few important points made in the papers
- A few ideas on how the content could relate to your own research
- A few additional points you would like to discuss
At each meeting, these issues will be discussed. After the meeting one (or possibly two) of the participants will write a summary of the papers of 5-10 pages. The summary is to be written in the form of a chapter in an introductory book on pervasive systems. The idea is that the course will result in a draft of such a book.
Each participant will write summaries of around 20 pages, i.e., corresponding to 2-4 summaries. A preliminary (but complete) version of the summary should be committed to the common repository within two weeks after the item has been discussed. Email the reviewers and Görel when you are done. If you are two participants writing the summary, you should collaborate, and not just split the work.
Each participant will also review 2-4 chapters, correponding to around 20 pages. The review should be written in a similar way as when you review a paper for a conference or a journal. It should consist of
- A brief summary of the chapter in your own words, based on how you view the actual text. A few sentences is sufficient. Don't make it too long.
- A couple of sentences that comment on the overall quality of the chapter, both concerning good aspects and aspects that can be improved.
- A list of more detailed comments, both concerning aspects that you appreciate and aspects you think can be improved. If you think some things can be improved, try to give constructive advice on how to improve it.
- For very minor things, spelling errors, etc., you might mark them directly in the pdf or on paper and give to the authors.
Try to be positive and constructive in your review. The goal is to improve the paper. The reviews are written individually. (You do not collaborate when you write the reviews.)
The reviews should be emailed to the authors, with a copy to Görel, at most two weeks after you got the preliminary summary.
Each participant revises the preliminary summaries you wrote, based on the reviews you get. In addition to the reviews by your course collegues, you will most likely also get a brief review from Görel or Boris.
When you revise the summary, you should take all the comments from the reviewers into account. You don't have to follow all the advise of course, but if there are comments you do not agree with, you should motivate why. When you commit the final version, email back a letter to your reviewers where you briefly state how you have addressed the comments. Copy Görel on this letter.
7.5 hp. This involves active participation in at least 8 of 10 meetings (including reading papers, preparing discussions, and participating in the discussions), writing summaries, and doing reviews.
See the literature page for detailed info on what articles to read.
- Mark Weiser's vision. Tuesday Nov 22, 9:30-11:30, the LUCAS-room
- Visions and overviews. Tuesday Nov 29, 9:00-11:00, the LUCAS-room
- Infrastructure. Tuesday Dec 6, 9:30-11:30, the LUCAS-room
- Systems/Projects. Thursday, Jan 19, 2012, 9:30-11:30, the LUCAS-room
- Pervasive Healthcare. Thursday, Feb 02, 2012, 9:30-11:30, the LUCAS-room
- Discovery. Thursday, Feb 09, 2012, 8:15-10:00, the LUCAS-room
- Configuration and Composition. Thursday, Feb 16, 2012, 10:00-11:40, the LUCAS-room
- The Internet of Things. Thursday, March 8, 2012, 9:30-11:30, the LUCAS-room
- Uesr interfaces. Thursday, March 15, 2012, 15:15-17:00, the LUCAS-room
- Context awareness. Thursday, March 22, 2012, 15:15-17:00, the LUCAS-room