Wiki
User Experience Engineering

Wk03: Affective Computing
Page last edited by Per Bækgaard (pgba) 21/01-2021

Affective computing are systems that either interpret, adapt to or influence our emotions. This week, we will work with such systems following a broad definition, and also allow for e.g. systems that adapt to cognitive state.

When you design your systems and ideas, make sure you BUILD ON VALIDATED RESEARCH. It may still be early research, but you HAVE TO find documentation that your idea could potentially work and that the assumptions you're building on have at least been suggested by literature.

The week will generally follow the overall concept of the course, with (daily) build-measure-learn cycles.

This page will be continuously updated through the week; the schedules below are therefore only tentative.

Monday

09:00: Lecture on affective and adaptive interfaces (recorded lecture)
10:00: Group work (discord)
12:30: Lunch break
13:00: Group work (discord; TA and lecturer will visit group rooms to discuss Q&A)
17:00: Hand-In to DTU Inside of your idea (presentation, named GroupNN_xxx.pdf). 

Slides: Morning Lecture

Assignment

  • You will this week create a system of your own choice that employs elements affective/cognitive interfaces, possibly adapting to your user(s).
  • Hold your own small brainstorming workshop within the group, identifying problems and pain points (define) that could benefit from employing affective/cognitive interfaces, and generate multiple ideas (ideate). You may benefit from observing or engaging with your intended users (empathise). Create whatever artefacts you think may be helpful to discuss your proposals, including snippets of LC, User Journeys, USM, Wireframes, etc.
  • As mentioned above: When you design your systems and ideas, make sure you BUILD ON VALIDATED RESEARCH. It may still be early research, but you HAVE TO find documentation that your idea could potentially work and that the assumptions you're building on have at least been suggested by literature.
  • Select one or two ideas, and generate a "poster"-like presentation that you hand-in by EOD (as PDF).

Tuesday

10:00: Continued group-work (discord)
12:30: Lunch break
13:00: Lecture on eye tracking (recorded lecture)
14:00: Group work (discord)

17:00: Hand-In to peergrade

Slides: Afternoon Lecture

Assignment

  • First, make a plan for what you want to do this week in terms of build-measure-learn cycles, and what methods you want to use -- pick what is best for your idea, and arrange them as needed (which could involve workshops, focus groups, prototyping, external visits, ...).
  • Then quickly iterate your ideas, taking input from the poster session into account. 
  • Also produce a lean canvas, user story map and initial sketches of wireframes in a storyboard and hand in to peergrade. ALSO INCLUDE YOUR PLAN (e.g. as a Gantt chart).
  • Peergrade will remain open until Wednesday 10:30, so you can either peergrade at your leisure in the evening or after the morning lecture Wednesday.

Wednesday

08:30: Group work / Peergrading (discord)
10:30: Peergrade closes
12:30: Lunch break
13:00: Guest lecture by Professor Jakob E. Bardram (recorded lecture)
14:00: Group work(discord)

17:00: Hand-In (LC, LP, USM, WF, Validation) to DTU Inside

Assignment

  • Continue working on your solution, creating prototypes and validating, following your plan.
  • Hand in the current set of all artefacts at the end of the day (LC, LP, USM, WF, Validation)

Thursday

08:30: "Wrap-up" Lecture/Feedback (recorded lecture)
09:30: Group work (discord)
12:30: Lunch break
13:00: Group work (discord)
17:00: Hand-In (Presentations for Friday morning in pdf format!)

Slides: Morning Lectures

Assignment:

  • Continue working on your solution, creating prototypes and validating, following your plan.
  • Also prepare and hand in a presentation for friday morning (similar format as previous week; only pdf!).

Friday

08:30: Group Presentations (zoom ( Gr 01-08 ), ( Gr 09-16 ) and ( Gr 17-25 ))
11:00: Group work (discord)

23:59: Hand-In of Group Report and your Individual Reflection Report by 23.59. Use the same format as in the previous weeks for the group report.

For the group presentations, please give feedback using this google form. Results will be visible here.

Individual report details

For the individual report, hand in 1/2 a page (not "normalsider" but a real page) in the same ACM format used above.

Each person may chose one topic from the list below.

Two persons in the same group are not allowed to pick the same topic.

For the chosen topic, please

  1. in our own words, briefly define “the concept”, possibly referring to course material,
  2. explain how it relates to the learning outcomes of the course, and
  3. reflect on how it has provided value to the assignments and what went well and that could have been improved with respect to the topic.

The topics for the individual reflections are:

  • Prototyping and Online Validation

  • Lean Business Canvas

  • Lean UX and the Build-Measure-Learn cycle

  • Wireframes and Non-screen Based Designs

  • Landing Page and Stakeholder Presentation

  • Human Centered Design

Additional Literature and references

Support: +45 45 25 74 43