last update: October 12, 2009

DA308: Discrete Interaction Design 2

Instructor:     

Prof. Dr. M. Rauterberg, Full Professor
Faculty Industrial Design,
Designed Intelligence Group, Technical University Eindhoven

Benefits

This assignment need 40 hrs work in total (about 10 hrs work per week), the total number of weeks depends on the actual period length (min 4 weeks).

After following this assignment students should be able to:

  • specify the discrete interaction structure of one or more new and so far unknown interactive products based on validated design knowledge provided by literature (e.g. ISO9241 parts 14, 15, 16);
  • create a mid-fidelity prototype with a prototyping tool based on a formal specification;
  • conduct a small usability test and translate the results as possible input for a re-design;
  • prepare and give four presentations, write a final report.

Previous Knowledge

  • successful participation of the assignment DA301 Interaction Design 1
  • good knowledge about PowerPoint, Flash, MacroMind Director, Java or any other Prototyping Tool
  • digital video recording and editing
  • planning and conducting a small usability test (formative evaluation)

Abstract

The assignment will start with an overview over different discrete interaction styles, and will introduce the design of a command language, menu and desktop user interfaces. The students will apply this design knowledge on a new design of a not yet existing interactive product and come up with a full specification of the interaction structure, which can be used to build a prototype for user testing.

The first part of this assignment consists of creating a new interactive product idea, design the command language interaction style for the planned functionality with one of a formal specification method from DA301 (or in addition with BNF), and present the specification document/diagram of this command language interface at the second meeting.

The second part of this assignment consists of creating a new interactive product idea, design the menu interaction style for the planned functionality with one of a formal specification method from DA301, and present the specification document/diagram of this menu interface at the third meeting.

The third part of this assignment consists of creating a new interactive product idea, design the direct manipulation interaction style for the planned functionality with one of a formal specification method from DA301, and present the specification document/diagram of this direct manipulation interface at the fourth meeting.

The last part of this assignment consists of implementing one of the three discrete interactions style in a mid-fidelity prototype, and test the result with several users. Based on the recorded users' reactions/comments, recommendations for a possible re-design have to be drawn. The final prototype and the main results of the user tests are presented in the final meeting.

Students will learn to design three different interaction styles as input for the implementation of a mid-fidelity prototype. They will gain hands-on experience in (1) using validated design knowledge as input for creating a interactive prototype, and (2) planning and conducting an empirical evaluation. They will experience how to optimise the trade-offs inherent in conducting prototyping and usability testing under 'real-life' constraints.

Literature is provided through this web-page (see below). Additional information throughout the assignment will be provided via the assignment emails distribution list DA308 (make sure that your email address is on this list!).

Assignment work

The feedback for this assignment will be determined by the work done on the set of deliverables (Dx; see below). Each deliverable (Dx) will cover a number of steps relevant for planning, applying and conducting a combination of formal and empirical methods. Furthermore, they will include discussions about the trade-offs of the decisions taken and the validity of the findings of the evaluation. Feedback will be determined based on the rigour with which the work is done, whether relevant concepts discussed in the assignment are embedded in the work and the report, and extra initiative to ensure good quality of work.

Deliverables

Date due

1.   A complete specification of the new command-language interaction structure described in a document/diagram (with at least 20 different user actions and 10 different system states)
Short description of the idea and purpose of the new interactive product (200-500 words)
[included in the final report].

2nd meeting

2.   Presentation of the specified syntax plus examples
      [
D1: delivered in electronic form as a separate PPT]
2nd meeting

3.   A complete specification of the new menu interaction structure described in a document/diagram (with at least 20 different user actions and 10 different system states)
Short description of the idea and purpose of the new interactive product (200-500 words)
[included in the final report].

3rd meeting

4.   Presentation of the menu design
      [
D2: delivered in electronic form as a separate PPT]
3rd meeting

5.   A complete specification of the new desktop interaction structure described in a document/diagram (with at least 20 different user actions and 10 different system states)
Short description of the idea and purpose of the new interactive product (200-500 words)
[included in the final report].

4th meeting

6.   Presentation of the desktop design
      [
D3: delivered in electronic form as a separate PPT]
4th meeting

7.   Mid-Fidelity Prototype with one of the three interaction styles (in case of an updated specification of the interaction structure, this updated document as well with a short description of what and why the changes were made; if you created more than one prototype, each version has to be delivered).
[D4: executable program file, eg. PPT or FLASH (plus source code)]
[design description included in the final report].

4th meeting

8.   Short description of the user test (number of  test subjects = 5) including users' profiles, task(s) description, results and recommendations for re-design; each user test has to be documented via video recording including audio records of the users' comments.
[
included in  the final report: (1) description of task(s), (2) user profile, (3) results, and (4) conclusions for possible re-design];
[D5: in addition at least five video files of user tests including audio of user comments].

4th meeting

9.   Final presentation
[
D6: delivered in electronic form as a separate PPT]

4th meeting

10. Final report in electronic form  
[D7: delivered as DOC, RTF or PDF file] according the proposed structure (see above) and format (see Report Writing Guide)

4th meeting

11. D8: a CD with all deliverables (D1)-(D7) handed in to the assignor's secretariat HG 2.34 or my letter box in HG 2.33

two days after final meeting

Assignment schedule

 

Date

Topic

Literature

kick-off

Introduction in the design of a command-language interface.

lecture-1 [PDF]

extra presentations:

Command-0, Command-1, Command-2, Command-3, BNF, Interface breakthrough

all relevant literature is provided at the begin of the following power point presentation, plus

obligatory:
ISO 9241 part 15

Backus Naur Form Syntax [txt]
K. Slonneger (2001) Specifying Syntax.

extra readings:
Compiler
PASCAL Report (1972) Wirth
CACM(1989) Grudin

MITRE(1986) Smith & Mosier
UNIX quick reference guide
Barnard et al (1981) Learning and remembering interactive commands.

2nd meeting

Each student present the command language interface.

Introduction in the design of a menu interface.

lecture-2 [PDF]

 

all relevant literature is provided at the begin of the following power point presentation lecture-2

obligatory:
ISO 9241 part 14

extra readings:
Button Design

Eric S. Lee & Raymond (1993) 'Menu-Driven Systems', The Encyclopedia of Microcomputers, Volume 11, Allen Kent and James G. Williams (eds.), p. 101-127 (1993).

3rd meeting

Each student present the menu interface.

Introduction in the design of a desktop interface.

lecture-3 [PDF]

 

all relevant literature is provided at the begin of the following power point presentation lecture-3

obligatory:
ISO 9241 part 16
GUI-Design Guide

extra readings:
APPLE GUI Design [online]
MS GUI Design [online]
Icon Design

Touch Screen Design
other guidelines

final meeting

Each student present the desktop interface.

Each individual student presents the final design and results of the user tests.

reservations of the Usability Lab at IPO building and borrowing of video cameras can be done via
Nico van den Ven
tel 040 247 -5229 
or -5200

n.l.j.v.d.ven@tue.nl

 

further information about infrastructure of all IPO labs via
Martin Boschmann

tel 040 247 -5210 or -5200

m.c.boschman@tue.nl

 

Student Feedback

Students work individually throughout the whole assignment; s/he will be graded based on the quality of the written reports/documents and the presentation given using a 2 point grading scale [Yes/No] and in constructive written feedback via the assignment feedback form.