729G22 Interaction Design
The course has two types of examination: a project (in group) and an individual report. Course grade Pass (G) requires a passed project work and a passed individual report. For course grade Pass with Credit (VG) a passed project work and passed with credit individual report is required for the course grade Pass with Credit (VG).
For a project work to pass, the following is required:
- Active participation, i.e. you need to be both physically and mentally present, at all checkpoints, if you have not been excused for a valid reason by the supervisor in advance (i.e. for having a fever).
- Passed User and Domain Analysis Report. Deadline: Friday 2016-09-09, 17.15. Supplementary examination deadline (if you have bee asked to revise or supplement the report): Friday 2016-12-02, 17.15.
- Passed final oral presentation (Thursday 2016-09-29, 13-17).
- That produced material is delivered to the external client in a structured form. i.e. the user and domain analysis report, the suggested paper prototype design with descriptive annotations, (including optional supplementary sketches), and usability test results. Delivery to clients takes place over email and the examiner should get a CC. Deadline for delivery to clients is Friday 2016-09-30, 17:15. The clients may also wish to get an oral presentation, but that is not part of the course.
The report, written in Swedish or English, should answer the following question: What is the most important you have learnt in the course?
Friday 2016-09-30, 17.15.
Supplementary examination deadline
Applies if you have been asked to supplement or revise the report, or if you miss the deadline. If you also miss that deadline, or is failed again, you have to do the examination for the course the following year.
Friday 2016-12-02, 17.15.
The report should meet the following criteria for the grade Pass (G):
- The report should be written entirely individually.
- The report should be at the most 2.500 words, and the number of words should be stated in a footnote.
- The report should clearly refer to the mandatory course literature, including page number if it is a book.
- The report should clearly state what grade (Pass/G or Pass with Credit/VG) you strive for, preferably in a footnote or similar.
- The report is handed in as a PDF to the supervisor over e-mail.
- The report should be well-written, with a clear structure and line of thought.
- The report should be spell-checked and proof-read. Make sure you use written language and not spoken language in the report.
- The report should use correct terminology in accordance with the course literature.
- The report should clearly motivate why every reported lesson learned is important.
- Reported lessons learned should be clearly connected to the course content and learning objectives (examples concerning for example project management and group dynamics are hence of questionable relevance).
- Lessons learned should as far as possible be illustrated using examples from the design material from the group project work, such as sketches, scenarios, transcripts etc.
The report should fullfil the following criteria for the grade Pass with Credit (VG):
- The criteria for the grade Pass (G) stated above.
- The report should clearly show how the lessons learned relate to university courses that the author previously have taken (at least three courses, referred to by course name). This should be done with some analytical depth, and the contents of the previously taken courses should be addressed. Simply name dropping the courses is not enough.
- The identified usability problems from the usability testing should be reported and assigned a severity rating. The reports should also contain design sketches that present suggested solutions to the most important usability problems. The way in which sketches solves the observed problems should be clearly motivated. Please note: Severity ratings, sketches, and motivations should be made individually.
If the report is failed there is one (1) chance to supplement and revise it, and the deadline for supplementary examination applies for that. If the supplemented and revised report also is failed, then the student has to do the examination for the course the following year.
A report that is handed in at the supplementary examination deadline will be given the grade Fail/U, Pass/G or Pass with Credit/VG. A report handed in at this deadline cannot be supplemented or revised further.
You cannot try for a higher grade (eg. from G to VG) at the supplementary examination deadline.
- Keep a personal journal or idea log during the project work. This will make it easier to write the individual report at the end of the course. You will otherwise forget things along the way.
- Write the report so that it is possible for an external reviewer (without any insight into you project) to get an understanding of how you have worked and what you have learnt. The reviewer will have an approximate idea of your project, so you do not need to start completely from scratch. 4-5 lines of concise description of the project/brief should be enough. You can also assume that the reviewer have a very good understanding of interaction design. Basic concepts do not have to be explained.
- Keep in mind that the reviewer only have the report as a basis for grading. What cannot be seen in the report cannot be considered in the grading. Make sure to include the most important lessons learned in the report.
- Focus on 3-5 lessons learned that you find extra important, and discuss them and give examples at some length. Explain why you feel that these are extra important. Describe preferable a hands-on event from the project and explain clearly how you should have acted instead to get a better result, given what you now have learnt. A common mistake is to be to shallow in the description of how you should have done.
- It is a lot better to focus properly on a few lessons learned, than to prove 30 very specifik points that are not generalised or exemplified.
- Note that 2.500 words is a limited space. You need to assess the significance of what you write, and how it is presented. It is easier to write a long unstructured report than a brief and succinct report.
- The report should not follow a classic report outline with purpose, method, etc. It is simply not that kind of report. It usually works well with two parts: one part that describes the project, and one that describes the lessons learned. For Pass with Credit (VG) there is also a third part with usability problems and design suggestions. The basic rule is that a reader should be able to follow a line of thought and not feel that the text jumps back and fourth between different things.
- It may feel a little strange to explicitly announce what grade you strive for, but the purpose of that is that you should think through you level of ambition early on and stand by it. It will also make the assignment more clear for you, since you need to be able to make a case for yourself why you should get a certain grade. This does not mean that you necessarily will get the grade you strive for.
- This kind of project made towards an external client is very easy to get caught up in, and spend even more amount of time to make the client happy. However, do not forget the individual report; it is after all the foundation for you grades. Make sure to make a time plan and budget based on the timetable of the course and other activities so that you really have time to write the report before deadline.
The following set of rules applies to the assignments in this course. It is a slightly modified version of IDA's general rules for labs.
Rules for examination
The assignments are in a group or individually, according to the instructions given for the course. However, examination is always individual.
It is not allowed to hand in solutions copied from other students, or from elsewhere, even though modifications have been made. If unauthorized copying or other forms of cheating is suspected, the teacher is required to make a report to the University Disciplinary Board.
You should be able to explain the details of the assignment. It is also possible that you may have to explain why you have chosen a specific solution. This applies to everyone in a group.
If you anticipate that you can not meet a deadline, contact your teacher. You may get some support and possibly a deadline at a later date. It is always better to discuss problems than to cheat.
If you do not follow the university and a course examination rules, and try to cheat, by for example plagiarizing or using unauthorized assistance, then it may result in a complaint to the University Disciplinary Board. The consequences of cheating can be a warning or suspension from studies.
Policy for presentation. A definite end date, deadline, generally apply to the submission of assignments in the course. This deadline may be during the course or at the end. If presentation is not done in time,you may have to do a new set of assignements the next time the course is offered.
Page responsible: Mattias Arvola
Last updated: 2016-08-23