TA06+Final+Interactive+Prototype

= Final Interactive Prototype =
 * Deadline: **** May 8 (firm) **

Note: this assignment goes with TA07 Usability Testing and Final Report and TA08 Final Video. They will be posted soon. 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. 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 go about your specific implementation).



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) **So far, you were 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.
 * 1) **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!).
 * 1) **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. 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. You can hard-wire data so that the app works for anyone as long as their name is "John Smith," for example. The important point is to try to convey a realistic experience of how the system would work for the specific tasks.
 * 1) Once you have the three primary tasks implemented, you need to **perform a usability test with three individual users**. See TA07 - Usability Testing & Report for more details on this. The final presentation will be in the form of a short video (see TA08 - Final Video).

= The Report = The report for the final interactive prototype is described in TA07 - Usability Testing & 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 Meethu and me before your demo session.

At least two of your four group members must schedule a 15 minute demo session with me during the last full week of class. 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 office (3217 AV Williams) unless we make other arrangements. I'm also happy to schedule an earlier meeting with you if you'd like some pre-due-date feedback. I'm available for that on Wednesdays, or before or after class.

Available times are: Tuesday, May 6: 8:30, 9:00, or 10:45 Wednesday, May 7: 11:00, 11:30, 12:00, 12:30, 1:00 , 1:30, 2:00, 2:30 , 3:00, 3:30 , 4:00 or 4:30 Thursday, May 8: 8:30, 9:00 , 10:45 , 11:15 , 11:45 , 12:15 or 12:45

Please arrange a time as soon as possible by sending me an email or filling in your slot in the table below:


 * ~ Project Team ||~  ||~ Date ||~   ||~ Time ||~   ||~ Location ||
 * League of Legends Fantasy League ||  || 5/7 ||   || 12:00 ||   || AVW 3217 ||
 * FRESH Stats ||  || 5/7 ||   || 1:00 ||   || AVW 3217 ||
 * Card Trading App ||  || 5/7 ||   || 2:30 ||   || AVW 3217 ||
 * Commute UM ||  || 5/7 ||   || 3:30 ||   || AVW 3217 ||
 * Gamigotchi ||  || 5/8 ||   || 8:30 ||   || CSIC 1122 ||
 * Quest Complete ||  || 5/8 ||   || 9:00 ||   || CSIC 1122 ||
 * Mobile Diner Menu ||  || 5/8 ||   || 10:45 ||   || AVW 3217 ||
 * UMD GPS ||  || 5/8 ||   || 11:15 ||   || AVW 3217 ||
 * Oarcall ||  || 5/8 ||   || 11:45 ||   || AVW 3217 ||
 * Order Up! ||  || 5/8 ||   || 12:45 ||   || AVW 3217 ||