Log on to edit
Wiki
User Experience Engineering

2019 Archive
Week 1: Affective Interfaces
Week 2: Augmented Reality
Week 3: Intelligent Systems
2018 Archive
Jan 2-5: Mental Health Applica​tions and Affective Computing
Jan 8-12: Augmented Reality
Jan 15-19: Adaptive Systems an​d Beyond
Historical Wiki for 02266 User​ Experience Engineering
2020 Archive
Wk01: Augmented Reality
Wk02: Social Robots
Wk03: Affective Computing
2021 Archive
Background knowledge
Wk01: Augmented Reality
Wk02: Social Robots and Agents​
Wk03: Affective Computing
Week 3: Intelligent Systems
Page last edited by Per Bækgaard (pgba) 24/01-2019

Intelligent Systems are (in this context) broadly referring to systems that e.g. learns from its context and (the behaviour of its) users, oftentimes adapting hereto or containing predictive elements in its interaction with its users. 

This weeks project will focus on creating systems that in some way act, or are perceived to act, "intelligently" by its users.

Notice: This page will be updated throughout the week with additional information and material.

Learning objectives
  • Identify, model and validate user needs and goals for specific market segments, using an iterative hierarchical process
  • Design and validate MVP UX prototypes building upon established interface paradigms
  • Design and validate MVP UX prototypes for emerging and novel types of interfaces
  • Design methods to rapidly measure and validate such hypothesis, facilitating a data driven decision process
  • Map out user needs, existing alternatives, market segments, unique value propositions and solutions provided by your augmented reality app using a lean business model canvas
  • Create user story maps for your augmented reality app in order to hierarchically model high level goals, activities and tasks as basis for scoping the prototype
  • Prioritize what slices of the user story map tasks you would translate into the wireframes and storyboard that would make up a first teration for your augmented reality app prototype
  • Define how your augmented reality app prototype will enable you to validate whether it solves a user "problem" for a specific market "segment" and to what degree that is reflected in your MVP minimum viable product "solution"
  • Use UX prototyping techniques to communicate with a diverse set of stakeholders

Monday

08:00: Introductory lecture on Intelligent Systems (B341#A021)

09:00: Group work (B358#H064, #H067, H068)

12:00: Lunch break

13:00: Sharing Ideas (B341#A021)

13:30: Group work (B358#H064, #H067, H068)

17:00: Hand-In to DTU Inside of a Poster showing your solution; print your poster afterwards and bring it next day

Tuesday

08:00: Poster Sessions (B358#H064, #H067, H068; setup from 08:00, start presentations at 08:15)

10:00: Group work (B358#H064, #H067, H068)

12:00: Lunch break

13:00: Lecture on Eye Tracking and Cognition (B341#A021)

14:00: Group work (B358#H064, #H067, H068)

17:00: Hand-In (LC, LP, USM, WF) to peergrade.io 

Wednesday

08:00: Summary Lecture (B341#A021)

08:45: Giving feedback via peergrade.io (until 10:00)

10:00: Group work (B358#H064, #H067, H068)

12:00: Lunch break

13:00: Short Feedback/Discussion/Overall Q&A Session (B341#A021)

13:30: Group work (B358#H064, #H067, H068)

17:00 EOD

Slides: Morning summary

Thursday

08:00: Group work (B358#H064, #H067, H068)

12:00: Lunch break

13:00: Continued Group work (B358#H064, #H067, H068)

17:00: Hand-In (Presentations for Friday morning in pdf format!)

Note: There will be no lectures today. Use the extra time for your individual reflection reports instead!

Friday

08:00: Group Presentations (B341#A021). Give feedback using this google form. Results will be visible here.

11:00: Group work (B358#H064, #H067, H068)

17:00: Hand-In of

  • Group report (0.5 page/group member) with Lean Canvas, Landing Page, User Story Map and Annotated (Micro-interactions/Back-end) Wireframes as appendices in one pdf file to DTU Inside. Name your file "GroupNN_title.pdf" (where title is a description of your work). Include also links to POP/Marvell/Invision "executable prototypes" but make sure you have all details of the wireframes readable in the PDF file you hand in.
  • Individual reflection reports (0.5 page in the same ACM format as above).

See further details in the assignments in DTU Inside ().

Literature

d.school at stanford: Design Thinking Bootleg (main page here).
Support: +45 45 25 74 43