overview
schedule
tutorials
project
resources

 

 
 PROJECT OVERVIEW 2011/12 Term 2  

 
 
General information

The course requires completion of a team project, which has five milestones that are marked. The 444 project is very similar in both structure and content to the 344 project. The key differences for the 444 project are: (1) advanced methods are used, (2) your project topic is not constrained to improving an existing interactive system, and (3) greater depth and quality of work are expected. You will participate in the same team throughout the course.

 Please consult the course schedule (early and often) for timing of the milestones.

Overview
 milestone
 components
I. proposal
[details]
[10 %]
  • individual work
  • propose an idea for a new (or revised) interactive system by identifying a human activity that could be better supported through interactive technology
  • describe the interface/system and its users and conduct a preliminary task analysis of the activity it is intended to support

MS I: DELIVER brief written proposal

DESIGN REVIEW (full course staff)

The most promising proposals will be chosen by the course staff to form the basis of the team work, starting in MSII.

II. field study, requirements & design alternatives
[details]
[15 %]
  • team work from this point forward
  • conduct small field study to inform your system concept and proposed tasks
  • define system requirements
  • brainstorm design alternatives that meet the requirements

MS II: DELIVER brief written report

DESIGN REVIEW (full course staff)

III. prototyping & experiment design
[details]
[30 %]
  • create a low-fidelity prototype of the design and conduct a cognitive walkthrough
  • plan an experiment that evalutes the new system (to be run in MS IV)
  • create a testable prototype using medium fidelity method of your choice

MS III: DELIVER experiment design and prototype  

DESIGN REVIEW (full course staff) - team demos working prototype

IV. experiment analysis,  recommendations, & project video
[details]
[30 %]
  • carry out the experiment, first by running a small pilot study
  • analyze the results
  • draw recommendations that would be used in a final design implementation (which you do not have time for in this course)
  • create a 3-5 minute video that documents your project

MS IV: DELIVER: written report and project video

DESIGN REVIEW (full course staff)

V. presentation
[details]
[15 %]
  • design and deliver a team presentation of your entire project

MS V: DELIVER: presentation to class and design jury

Formatting

Constraints on the page length of components of each deliverable are given in the Milestone description, under specific deliverable components.

For all milestones, use the following formatting:

  • Single-spaced, 12 point font
  • 1" margins
  • Double-sided pages
  • Page numbers

Your Milestone documents should include:

  • Cover page: For team milestones list the name of your group, the members' names and photos of all team members (or one photo including all of you, clearly identified) and the date. For individual milestones, list your name, provide a photo, and the date.
  • Deliverable reports: Begin each deliverable (A1, B1 etc) on a new page, with clear section headings.
  • Appendices: Complete as indicated in the milestone descriptions. Clearly mark the appendices (e.g., separate each appendix with a title sheet). Unless otherwise specified, appendices will not count towards the page limit. They should be a reasonable number of pages, and if they are deemed to be excessive, marks will be docked.

Submitting

Both an electronic and a hardcopy version of each Milestone deliverable must be submitted BEFORE the start of your tutorial/lab/lecture on the due date, as posted on the schedule page.


Protject Protfolio (required for Milestones II, III, and IV)

As in 344, you will use a Project Portfolio: a 2 inch 3-ring binder with tabbed dividers (supplied by your team), which will hold the paper version of each of your project deliverables. This binder will be kept in your team folder in the secure cabinet in the HCI Studio (X360).


Hardcopy submission instructions

What?

The hardcopy version goes directly into your teams' project portfolio binder. (Binder is not required for MSI -- project proposal.)

In addition to the material described above, the hardcopy Milestone Portfolio should include, in clearly marked (please use tabbed divider sheets) sections:

  • Tabs for portfolio sections for Milestones II-IV
  • Previously marked Milestone documents, which have been returned to you by course staff
  • The current Milestone being handed in

The hardcopy version goes directly into your teams' project portfolio binder. (Binder is not required for MSI -- project proposal.)

Where?

Place the hardcopy into the box labelled CS444 on the top of the black metal filing cabinet near the door in x360.


Electronic submission instructions

Format: All electronic submissions must be in PDF format.

Size: It is important to minimize file size to reduce course disk space needs. Use Acrobat's "Reduce File Size" option (or similar option in whatever software you're using) to compress your PDF and down-sample all images to 150 dpi and black-and-white or grayscale, whenever appropriate.

Filename: Project proposal filenames should be in the format <name>-<assignment name>.pdf. All team milestone filenames should be in the format <team name>-<assignment name>.pdf. Use web-friendly filenames (under 20 characters, no spaces or funny characters). For example: TheGoGetters-MSIII.pdf.

Test: Ensure that your submissions are viewable on a departmental machine before using handin.

Number of submissions: Make only one submission per team: choose one team member to submit.

Handin: Use the handin utility for submission, using the command:

handin cs444 project_<milestone>
e.g., handin cs444 project_MSIII

Marking

The tentative high-level marking scheme for each milestone is provided in the milestone description.

You will be marked on the basis of:

  • originality and insight into problem definition
  • completion of required items
  • appropriate maturity of the work (i.e., clearly thought through and iterated rather than first pass, tossed together ideas)
  • quality of writing, clarity of exposition, and usefulness of supporting figures

A penalty will be assessed:

  • for improper use of handin or inability to use handin
  • for not adhering to the submission criteria and formatting requirements (e.g., page length and font size)
  • not producing professional documents (e.g. inconsistent formatting, missing page numbers)

Late submissions will not be accepted.

 
 

Advanced Methods for Human Computer Interaction - McGrenere 11/12