|This module is 100% CA (“continuous assessment”); there is no exam.
Seminars (30% for NM5215/24% for NM5215R)
Participation: forum, in-class discussions, etc.
Mid-term report/project (30% for NM5215/24% for NM5215R)
Students will choose one design methodology and create formal design knowledge for a specific interactive design problem. The report will consist of the proposed solution and student reflections on the process/result.
Final report/project (40% for NM5215/32% for NM5215R)
Students will apply, evaluate, and reflect on the formal design knowledge they have created for a specific interactive design problem. The final report will consist of documentation and student reflections on the process/result.
Essay (20%, for NM5215R only)
A short essay reflecting on a topic relevant to the module, to be chosen in consultation with the lecturer.
Depending on the number of students in the module, there may be group-based projects. Group size will depend on the number of students in the module, but it will never be larger than 4 students to a group. Also, if there is group-based work, grading will be based partly on individual performance (70%) and partly on team performance (30%). An individual grade means that each individual needs to work alone on that component -- each student will be evaluated separately for that component. A group grade means that every individual in the team receives the same marks for that component.
Everything due in this module has a deadline. Unless there are truly exceptional circumstances, late delivery of a particular deliverable is marked down 10% for each hour it is late. See the Lesson Plan for a week-by-week snapshot of deliverables.
Warning: students may not use a project they have created (or are creating) for another module as a project submission for this module. If students want to build upon a project they have created earlier, they need to:
seek approval from the module instructor before starting to work on the project
provide information about other modules where the project has been submitted, and
clearly describe what is new about the project for this module (note that "what is new'' must be significant and must be equivalent in scope to other module projects that are not based on pre-existing projects)