Homeworks > Homework 4

Homework 4: Implementation of the Prototype

Assigned: Mon, June 10, 2013; Due: Mon, June 17, 2013 at 10:30am EDT (note: no late turn-ins for HW4!)

Using the design that resulted from all your testing and revisions from Homework 3, you are now going to implement the interface. You can use any way to implement your prototype such as those that were discussed in class (see Lecture 7 which includes links to various places to download versions of the implementation tools).

PART A: There is only one part to this assignment: to implement your interface. You should implement at least enough that all your user tasks can be completed, with sufficient feedback so the users can see what the system's responses are. You should simulate actions of your device. For example, if you were doing a copier, when the user clicks "Start" you might display a screen or dialog boxes that says everything about the current operation, for example: "now copying, 2-sided, no staples, using paper tray #1". If there are parts of your user interface you do not implement, there should still be controls (buttons, sliders, etc.) that would lead to those parts of the interface, but instead lead to screens or dialog boxes that say "not implemented yet" or something. That is, all of the screens you show should look complete, even if all the operations do not necessarily function. As another example, if you have a "search" button, it is fine if the search-results screen always shows the same thing, no matter what is searched for. As we have said a number of times, the complexity of the interface should be: "At least 30 “controls” (widgets: buttons, text fields).  About 10 different screens/pages/windows/modes".

Also create a short "readme.txt" file that describes what one can do with the prototype. This will guide the TAs on what is supposed to work. For example, tell what paths through your interface are working. If you pretended that the user searches for "aspirin", mention that kind of thing in the file. The "readme.txt" file should also contain your task test script that you will use for the user test, so the TAs and others will know what you will tell users to do. Put the readme.txt file in the top level folder where the implementation is so it will be at the top level of the .zip file.

  1. The deliverable for PART A is the complete implementation. Just zip up your entire directory structure including project files, the readme.txt file, etc. Name your file: HCI-HW4-lastname-firstname.zip, for example: HCI-HW4-myers-brad.zip. Put this file on blackboard in the Assignment 4 area. NOTE: Make sure it will be easy for us to run your system, and to see the source code. Make sure any required images are included in the zip file, and include the "readme.txt" file explaining how to run your application.

Important Notes:

  • It must be easy for us to run your implementations. Note that it should be runnable on either a PC or a Mac. Points will be taken off if we have trouble making it run. Points will also be taken off if you forget to include your source code. It would be a good idea for you to test your zip file on another computer to make sure you remembered everything.
  • Make sure all the pathnames (filenames) of any pictures or sound files you use are relative pathnames, so the project will run when it is moved to the TA's computer. For example, the filenames should not start with C:\ or file://c:/
  • We really need everyone to turn in this assignment on time, so we can give your final implementation to your classmates.
Back to Homework Page