The main part of the course is dedicated to the
design and implementation of a larger ubiquitous computing project. The
purpose of the project is to practice interaction design by doing, as
well as to experience the value of prototyping. The project will also
bring together technical knowledge from the Physical Computing course
with more design-oriented thinking of IT. The
project should result in a working prototype ready for demonstration at
the end of the course.
Possible Projects Ideas
Projects should be about creating a
thing or a computational environment with a clear relation to the ideas
of ubiquitous computing. Preferablly, the projects should also involve
the course theme, which is "Homes:
ubiquitous domestic environments" and can adress topics such as
interactive furniture, everyday activity support or sustainable living.
Exceptions to this may be accepted, in particular the project could be
appliable to the Index Aiga:
Challenge about Designing Water's Future.
When you are trying to invent your
project try to look for settings that will help you come up with ideas,
All projects must be approved by the
teachers before they are initiated.
- Design for a specific use situation or for a specific
- Find inspiration in a boring situation and design to
- Game and play - A game or a toy with a well defined
- The invisible interface
- Digital artefact - or simply digital art?
Groups and Supervision
Projects should be carried out in groups of 3-5
students (max 6). The groups are formed by the teachers at the
of the course. In the creation of groups, focus is on a forming
groups with a good mix of various skills. Throughout the project there
will opportunities for supervision regarding both interaction design
Mao Yiqi, Valgeväli Kadri-Ann, Börjesson
Joakim, Ström Victor, Sabbagh Pour Amir
Nave Saraiva Carla Do Carmo, Skogberg Alexander, Li Nancy, Zand
Muhammad, Odour Erick, Cirillo Simone
Pfoser Silvia, Dabai Aliya, Appelkvist Olof, Chamsaz Amir, Jansson
Gustaf, Winkelmann Christian
Polheimer Frida, Tian Xu, Shami Muhammed Waqas Ahmed, Prakash Kirpalani
Vicky, Al Said Ahmed Adnan
Azimi Yancheshmeh Sepideh, Tancredi Weronika, Hjulström
Martin, Chiu Han Hsiu
Holth Österlund Christian, Gantois Guilhem, Abdi Azandaryani
Patrik, Wang Zheng
Steffen, Magnusson Andreas, Gobena Markos Kassa, Daggumati Vijaya
Madhavareddy, Nizamani Abdul Rahim
Widlund Jonathan, Hallila Reetta, Dormishian Dorreh, Johansson Ramsus,
Ardavan Mohammad, Azhar Rehan
Slahuddin Asif, Johansson Erik, Jafari Harandi Farshid, Ghafari Nia
Project Drafts and Project Proposals
To ensure the quality
of the projects, each group will
have to present a number of proposals during the initial concept phase.
The process is outlined below.
As a first step each group must hand in five project suggestions no
later than 10th November 13.00.
suggestions can be rather brief, but must contain a concept
description, a description of the context of
use, possible users and, last but not least, why this project is
The suggestions are submitted
by sending an e-mail to Lalya Gaye (lalya [at] chalmers [dot] se). You
will then receive some
feedback before the next step.
On 12th November
each group will present 3 project proposals to the rest of the class
for feedback. Focus on the following issues:
You do not need to hand in anything this day. Instead, try to get your
classmates to provide feedback.
- Background / problem area
- How you intend to work with the suggested problem
- Related research / products
- How you came up with the idea
Based on the feedback from the presentation of the
project proposals, each group selects and describes their final project
proposal. The final project proposal must be submitted by sending an
e-mail to Lalya Gaye (lalya [at] chalmers [dot] se) no later than 17th
The following should be presented in your written
- Title of the project.
of your idea or concept, motivate your choice and give a short
background description. You can for instance mention related
research/projects/ideas that you know of, user group, or a use scenario.
- Some sort of picture or sketch of the concept.
- Description of how you have planned to implement and
how you plan to realise your idea.
- If your project is dependent on a certain technology,
then describe this.
- Suggestion of criteria for how you can validate how
well you have succeeded with your project.
- A time-plan for how you imagine to realise the
different parts of the project.
When the final project proposal has been reviewed by the teachers, the
project will be given the sign Project
GO on 17th November.
Each group has a budget of 1500 SEK. Expenses will be
covered by handing in receipts. Each group should collect all their
receipts, and hand them over to Lalya Gaye together with name,
adress, and bank account of the person who shall collect money for
is recommended that you check with Lalya Gaye or Annika
you buy any electronic components. We might already have them. It is
also wise to check for other things as well.
The main criteria for grading the project will be:
- Concept - originality, development etc
- Realisation - how the project work is carried out
- Presentation - the result displayed at the end of the
- Documentation - the quality of the project report.
The projects must be documented in a project
report. The report consists of two parts: (1) a website
giving a brief description of the project, (2) a full paper report
delivered as a PDF-file. The paper
report must be available for download from the website part of
The written report should contain:
The contents could be arranged in any suitable order. A possible
traditional report outline could be:
- project concept
- an introduction to the context of your design
- main goals of the project
- possible related work
- the design process and critical design decisions made
- how the project was realized, including a description
of the technology behind it
- evaluation against goals
- discussion: what worked, what did not, possible
improvements, interesting findings, etc
- conclusion, lessons learned
- technical documentation, as appendix
- project plan as appendix.
The website should contain the following:
- Related Work
- Appendix: Technical documentation and project plan
The purpose of the website is to draw attention to
your project and
create an interest for reading your report for further information. The
website will be read by future students, media and people without your
- Short abstract in Swedish and English
- Description of the project
- Video (if there is one)
- Pictures and/or powerpoint
- Downloads of source code, technical specifications
etc, required to re-create the project.
The project report is submitted by handing in an electronic copy of the
project website no later than 19th
Note that no changes or corrections to this version will be allowed.
Conference Paper Submission / Design
Student groups are required to either write a short paper (2 pages ACM
their projects, to be submitted to suitable conference if available
(submission optional). Students are also encouraged to submit to the Index Aiga:
Challenge about Designing Water's Future if their project suits the
call for participation, in which case submitting to the design contest
can be done instead of writing the short paper.
Below are some up-coming deadlines for relevant conferences:
14 December 2008
- Persuasive 2009:
- LOCA 2009:
- NIME 2009: 24 January
- Pervasive 2009:
January (late breaking results, posters, demos, videos)
- Nordic Design Research
- HCI International:
23 February (posters)
- Interact 2009:
- Ubicomp 2009:
(papers, notes) + 18 May (posters, videos, demos)
- SIGGRAPH 2009:
- UIST 2009:
- NordiCHI 2009: TBD
About Writing Papers