Design Project 2


This course requires m1 students to design, prototype, develop and evaluate an interactive system that will be part of their BDLabs cours. Students will work in groups of 3.


The deliverable will consist of original software, 3 intermediate reports and a final paper and defence.

The final documentation is a paper that describes, analyzes, and discusses the design choices embedded within the system, conceptually, technically, and critically, and the resulting user evaluation.

Intermediate Reports: We will distribute the load of documentation of the work over the 4 week through intermediate reports that are due on the Friday after class: 

    • 1st report: 9/03 
    • 2nd report: 16/03 3rd report: 23/03 

Paper: The formal writing of their project should be in the form of an interactivity paper, preferably in the CHI extended format

Reference: Galvan, J. (2006). Writing literature reviews: a guide for students of the behavioral sciences (3rd ed.). Glendale, CA: Pyrczak Publishing.

Defence of the Design Projet : 16 of March at 4PM.

Grading Criteria: Students will be graded on the quality of the work, the written paper and oral presentation of project.

The criterion will be the effective understanding and application of Design and HCI concepts in designing and developing and evaluating their interactive system. The user evaluation will rely on qualitative or quantitative methodologies of the student’s choice and is not mandatory but highly suggested.

If appropriate, students should also prepare a video of their project, preferably with narration.

Learning Outcomes

The students will be able to:

  • Apply HCI and Interaction Design principles in the design, development and evaluation of your interactive system.
  • Prepare and deliver a short oral presentation and written paper demonstrating your application in the design of the interactive system.
  • Conduct an in-depth project about the design and evaluation of an interactive system.

Design: Material for framing the Design Process is based on the design of interactive systems bootcamp

Course of the month’s classes

Week 1: 07/03 (Sarah):  From Brainstorming to Low Fi Prototype

  • During:
    • Brainstorming, select your project focus and describe it to us.
    • Possible proposal topic + plan of attack.
    • Feedback, refine proposal + plan of attack
  • After report 1,
    • Send us the concept + plan of attack + a beginning low-fi version of your system

Define the problem: Develop a deep understanding of your users and the design space and, based on that understanding, come up with an actionable problem statement: your point of view.

Generate radical design alternatives: Explore a wide solution space. From this vast depository of ideas you can build prototypes to test with users.

Prototype: Get ideas and explorations out of your head and into the physical world. Use post-it notes, a role-playing activity, a space, an object, an interface, or even a storyboard. This is a low-fi Resolution. In early explorations keep your prototypes rough and rapid to allow yourself to learn quickly and investigate a lot of different possibilities.

Week 2: 14/03 (Sarah) From Low Fi to High Fi Prototype

The objective is to have go from a low-fi to a High-fi prototype. We will give you feedback and highlight problem areas to work on

  • Before:
    • the concept + plan of attack + a low-fi version of your system
  • During:
    • Testing the prototype
    • Feedback, refine proposal + plan of attack
    • Refine & reiterate on the prototype
  • After: report 2
    • Write brief report on low-fi prototype, the results/decisions based on user testing + high-fi version of your system

Test: It is the chance to get feedback on your solutions, refine solutions to make them better, and continue to learn about your users. The test mode is an iterative mode in which you place your low-resolution artifacts in the appropriate context of the user’s life. Prototype as if you know you’re right, but test as if you know you’re wrong.


Prototype: at this point you need to start working on a high fi resolution of your prototype. Prototypes are most successful when people (the design team, the user, and others) can experience and interact with them.

Week 3: 21/03 (Anastasia) From High Fi Prototype to Interactive System 

The objective is to go from a high fi prototype to an interactive system. We will give you feedback and highlight problem areas to work on 

  • Before:
    • The high-fi prototype of the system 
  • During:
    • Testing the prototype
    • Feedback 
    • Refine & reiterate on the High-fi prototype
  • After: report 3
    • Write brief report on your high-fi prototype, results and decisions based on user testing + a version of your interactive system. 

Week 4: 28/03 (Sarah) Last testing 

The objective is to test your solution with real users among each other or external people and iterate. 

  • Before:
    • Prepare for user tests
  • During:
    • Feedback on user tests
    • Run user testing
    • After (due the day of the defence): Paper! 
    • write a paper, include user testing results + future works and possible improvements

For evaluating the system, you can use:

  • Structured interviews
  • Observational task analysis
  • Ethnographic field studies
  • Controlled experiments
  • Surveys and Questionnaires
  • Think‐aloud / Wizard of Oz
  • Field Testing