Project Requirements

The project will follow a Goal Directed Design (GDD) process as described in class. This document describes:

Getting Started

Find a team. Send an email with: your team name, a brief description of your project, and a list of team members.

The Design (36 points)

The design process will be divided into 3 steps. Although a few activities (e.g., interviews) may be done individually, only one copy of the design documents is needed per group. All submissions should be made in a standard document format (e.g., .docx, .odt, .pdf) unless otherwise stated.

Design Step 1 (6 points)

This is the initial stage of your design. You may want to refer to: Understanding Users.

Specific requirements:

Here are some examples from this year's projects:

Design Step 2 (14 points)

This continues the initial design, also from Understanding Users.

Specific requirements:

Design Step 3 (16 points)

During this step your design should start to take shape. Your submission may include .ppt or some other format for the visual design (but the grader should not have to install software in order to grade your submission).

Specific requirements:

System Justification

The final program is worth 65 points. The rubric for the final program is:

When you turn in your final product, you will also submit a document that justifies the points. To ensure that your product has sufficient depth, for now you will turn in a justification of just the functionality/feature points. If you have 3 or more people, your justification should list roughly what each person will be responsible for. The purpose of this is to ensure that larger teams have correspondingly larger requirements.

You may want to review this example justification based on a project done in a previous semester. Note that the rubric was different (fewer points for UI principles, included a separate challenges area)

Bring a hard-copy of your justification to class.

Implementation

The system implementation component has 3 major milestones:

Demo (5 points)

Each team must schedule a demo/usability test with me. These demos will be scheduled on Nov 19/20 if possible. Note that it's best if all team members can attend, but if scheduling becomes an issue we will waive that requirement.

The team should be prepared for me to do a think aloud. That is, you should have a set of tasks for me to complete. You should explain the purpose of the think aloud, and treat me like a normal test user. Nothing to submit, but you should address any concerns raised.

One member from each team should sign up on this doodle.

System Usability Test (10 points)

You may want to refer to: Usability testing notes.

Your usability report should include:

Submit your usability test on Blackboard.

Final Project (65 points)

Final projects will be presented the last week of class. Each team should also submit a CD containing the project code and a text file with brief instructions for using the product. NOTE: Most of the grading will be done based on the presentation. I may not require CDs for every project, please check with me.

You should submit your System Justification along with your project. Update your system justification based on what you actually accomplished. If you removed functionality, include an explanation of why, including why your project functionality is still worth 40 points. You should also very clearly state the UI principles for your project. Please bring five copies to the presentation (I will solicit other teams to help critique). Provide detail - this is your chance to justify your grade for the final project.

The Presentation(10 points)

This presentation consists of short demonstrations of the product, along with discussion of: how this product adheres to good UI principles, tools used, what was easy, what was difficult, lessons learned, etc.

Length: ~10 minutes (depends on the number of teams)

NOTE: Since we won't have much time, you should do most of your discussion of how you adhere to UI principles while you do your demo. You will probably have one slide with your team name, one slide with the user goals for your system, then a demo. During the demo you can talk about tools you used, what you had trouble with, etc. as well what UI principles you followed. You may follow up with one slide on usability results, or you may want to talk about your usability results during the demo.

Tuesday December 4

Thursday December 6

Peer and Project Evaluations (5 points)

To ensure that all team members have contributed equitably, download and fill out this Peer Evaluation form. Submit the .doc file on Blackboard.