Final Interactive Prototype

Deadline: Finals Week (12/16 - 12/19 before class)

Note: this assignment goes with TA09 Final Report and TA10 Final Video. Please read them in concert. The focus for this assignment in particular is on the design, engineering, and implementation of the final interactive prototype.

Assignment Overview
You've nearly made it. As Paul Laseau (1980) notes, the design process is a symbiotic relationship between idea elaboration and idea reduction (recall Chapter 1 of this Greenberg et al. reading). From the course-long project perspective, we are at the end of the elaboration phase, so your ideas are to be reduced/manifested into a final interactive prototype (though, of course, even here there will be a micro-elaboration/reduction phase as you brainstorm how to go about your specific implementation).

ElaborationReduction.png

The interactive prototype can be built in any programming language of your choice based on the needs of your application; however, your grade will be based on the following: (i) the technical sophistication of your prototype, (ii) the way in which you apply IxD and visual design principles from class, (iii) how you've integrated findings from previous assignments, and (iv) how well you support your three primary tasks. Thus, the design choices you make for the interactive prototype must be well justified from the literature we've read, lecture content, and from user testing and design critiques of earlier prototype versions.

What To Do

  1. For TA06 (the Mid-Fi Prototype assignment), you were still working with two prototypes. It's time now to take the findings from your previous user studies and design critiques and settle on a final design. You should also apply IxD and visual design principles from lectures and the readings to create a usable, engaging, aesthetic, and enjoyable interface.

  2. Each team can decide on their own implementation strategy. As we are time constrained in this class, it might be best to settle on a programming language or framework that at least one teammate has experience using. Also, your choice of implementation should fit your project. If you are working on a mobile app, you could develop it in iOS7, Android, or HTML5. As most of you are seniors, these sorts of decisions will be similar to what you face in the "real world" as developers or project managers (and you'll face time constraints there too!).

  3. Your entire focus should be on supporting the three primary tasks identified in earlier project assignments. You do not have to implement anything beyond that necessary to accomplish these tasks. As with the mid-fidelity prototypes, it's up to you how you want to constrain user interaction. For example, you could disable buttons, show a "not-implemented" page or dialog box with a back button, etc.

  4. Once you have the three primary tasks implemented, you need to perform a usability test with three individual users. See TA09 - Final Report for more details on this.

The Report

The report for the final interactive prototype is described in TA09 - Final Report. The primary deliverable for this team assignment is the interactive prototype itself. See below.

Deliverable

The primary deliverable for this assignment is the interactive prototype itself. You must post your code to your Wiki or a link to a Github repository (or similar). If you do not want your code accessible online, you can email a .zip to Matt and I before your demo session.

At least two of your four group members must schedule a 15 minute demo session with me before our final exam slot (Dec 19th at 10:30AM). For the demo session, I will serve as a "participant" using your system to accomplish your project's three primary tasks. This demo will take place in my HCIL office (2117f Hornbake Library, South) unless otherwise noted below.

Please fill in a cell with your project name to schedule your demo session. The "XXXXXX" cells correspond to times when I cannot meet.


Dec 16, Monday
Dec 17, Tuesday
Dec 18, Wednesday
Dec 19, Thursday
08:00AM
XXXXX
XXXXX
XXXXX
XXXXX
08:15AM
XXXXX
XXXXX
XXXXX
XXXXX
08:30AM
XXXXX
XXXXX
XXXXX
XXXXX
08:45AM
XXXXX
XXXXX
XXXXX
XXXXX
09:00AM
XXXXX
XXXXX
XXXXX

09:15AM
XXXXX
XXXXX
XXXXX
TerpGenius
in Jon's AVW Office (3173 AVW)
09:30AM
XXXXX
XXXXX
XXXXX
XXXXX
09:45AM
XXXXX
XXXXX
XXXXX
XXXXX
10:00AM
XXXXX
XXXXX
XXXXX
XXXXX
10:15AM
XXXXX
XXXXX
XXXXX
XXXXX
10:30AM
XXXXX
XXXXX
XXXXX
XXXXX
10:45AM
XXXXX
XXXXX
XXXXX
XXXXX
11:00AM
XXXXX
XXXXX
XXXXX
XXXXX
11:15AM
XXXXX
XXXXX
XXXXX
XXXXX
11:30AM
XXXXX
XXXXX
XXXXX
XXXXX
11:45AM
XXXXX
XXXXX
XXXXX
XXXXX
12:00PM
Neon Bats
in Jon's HCIL Office
Waitless
in Jon's AVW Office (3173 AVW)
Team Rhotic Vowels
in Jon's HCIL Office
XXXXX
12:15PM
Kinect Drums
in Jon's HCIL Office
SmartRide
in Jon's AVW Office (3173 AVW)

XXXXX
12:30PM

LitterLess
in Jon's AVW Office (3173 AVW)

XXXXX
12:45PM



XXXXX
01:00PM
GroupShare
in Jon's HCIL Office


XXXXX
01:15PM



XXXXX
01:30PM



XXXXX
01:45PM



XXXXX
02:00PM



XXXXX
02:15PM



XXXXX
02:30PM



XXXXX
02:45PM



XXXXX
03:00PM



XXXXX
03:15PM



XXXXX
03:30PM



XXXXX
03:45PM



XXXXX
04:00PM


GNOTES
in Jon's HCIL Office
XXXXX
04:15PM



XXXXX
04:30PM



XXXXX
04:45PM



XXXXX
05:00PM



XXXXX
05:15PM



XXXXX
05:30PM


Team Vector
in Jon's HCIL Office
XXXXX
05:45PM



XXXXX