Swedish web site
TDDD26 Development of Interactive Systems
Examination
The examination of the course consists of two parts:
- Project work in group. This receives the grade Fail (E) or 3 (C).
- Individual report. This receives grade Fail, 3 ,4 or 5 (E, C, B or A)
To pass the course with grade 3 (C) both project work and individual report must receive grade 3 (C). For grade 4 or 5 (B or A) the project work must receive grade 3 (C) and the individual report grade 4 or 5 (B or A). Thus, the individual report is the base for individual examination. As a complement to this we will use a survey for self and peer assessment. This can be used to corroborate the grading of the individual reports. Here you can find the survey.
Below are more detailed information on the requirements for the different grades for the project work and the individual report.
Project work in group
- Actively participate in all aspects of project work: design workshop, planning game, design, coding, testing.
- Actively participate in the supervision meetings.
- Hand in the code and documentation for the project work at the demo session:
- Name, personnummer (social security number), liu e-mail for all participants
- Project specification
- All written work material, for example user stories, acceptance tests, sketches.
- Results from discussions, planning games and tests with users
- Instructions for how to start the prototype (and technical requirements)
- Prototype (code)
- A printed version of the peer assessment survey that you have filled in.
Individual reports
The report should answer two questions:- What is the most important thing you has personally contributed to the project work?
- What is the most important thing you have learned in the course?
To recieve the Grade 3 (C) the report must:
- be handed in as a PDF file to the tutor via e-mail latest 25/5 at 13.00.
- be 1500 - 2300 words. The number of words must be stated in a footnote.
- be written entirely individual.
- be well-written. It must be spell checked and thoroughly proof read. Spoken language is not acceptable. A report with poor language is returned immediately without review.
- use correct terminology according to the course literature.
- have a clear structure and theme.
- clearly justify why the described contributions have been important for the project work results.
- clearly justify why each reported lesson learned is important.
- clearly refer to the course literature (with page number in the case of books).
To recieve the Grade 4 (B) the report must also:
- demonstrate that the student has made outstanding efforts in the project work.
- describe your own contribution and lessons learned in a way that demonstrates an excellent understanding of the course content.
To recieve the Grade 5 (A) the report must also:
- clearly show how the lessons learned are linked to relevant previously, or at the same time, read university courses (two courses, which are referred to by name of course).
OBS!
Note that if the report shows a poor level of effort in the project work, it will result in the grade Fail (U/E) on the project, and thus the grade for the course as a whole will be Fail (U/E). The only possibility to pass the project and the course is to to take the course next time it is given.
General tips
Write the report in a way that allows for an external reviewer (without deeper insight into the specific project group) to form a good idea of how you have worked and what you have learned. You can however expect that the examiner has an approximate picture of what the project work is about, so you need not start from scratch, about 4-5 lines of concise description of the project work should be enough. Likewise, you can assume that the reviewer has very good knowledge of the subject. Basic concepts need not be explained.
Remember that the person grading the report (and indirectly the individual contribution to the project work) only consider the text in the report. What is not shown in the report is not included in the grading process.
Be sure to include the most important contributions and lessons learned in the report. Personal contributions are reported by the 3-5 most important contributions to the project work described in detail. Be sure to justify why and how the contributions were important. Try to highlight what is unique to you. Have you made any important decision? What were its consequences? Have you taken responsibility for something specific? Contributions made with another person, where it is difficult to tell who did what exactly, may also be described, but then it should be clear who the other person is and how the collaboration came about.
Explain why each reported contribution and lesson learned is important. Do not assume that the reader draws the exact same conclusions as you. Try to avoid a description of the form "First I did si, since I did so ...". It can of course be important to use a chronological order in certain cases, but it is not an exhaustive list of what you've done in the course that is requested. As for contributions, focus on the 3-5 extra important activities (as you judge it) and spend plenty of room to discuss and illustrate these, and explain why you believe these to be extra important. Please describe a specific event in the project work and explain clearly how you would have acted instead to get a better result, given the lessons you've learned. A common failure here is that the description of how you would do instead is too superficial. It's much better to focus properly on a few lessons than to list 30 very specific lessons that are not generalized or exemplifieras. The described lessons should be applicable to course content and the stated learning objectives.
Note that 2300 words is a limited space. It's about carefully deciding what should be included and how it is presented. Remember that it is much easier to write a long and unstructured report than a short and koncis. The report should not follow the classical report template with the purpose, method, etc. It is not the type of report simply. Often it works well to have two parts: one part with contributions and one part with lessons learned. The basic rule is that the reader should be able to follow a line of argument through the report and not feel that it jumps back and forth.
Total grade for course
The grade for the course is based solely on the grade on the individual report.
Note that if the report shows a poor level of effort in the project work, it will result in the grade Fail (U/E) on the project, and thus the grade for the course as a whole will be Fail (U/E). The only possibility to pass the project and the course is to to take the course next time it is given.
Page responsible: Annika Silvervarg
Last updated: 2012-04-16
