* Full: fully functional but with restricted performance
* Horizontal: displays full range of system without details in any area
* Vertical: fully functional for only part of the system

Prototypes can be high or low fidelity, defined by the degree of approximation to the final system, and classes of prototyping techniques include:

* Visual: slide shows or storyboards or wireframes, etc
* Wizard of Oz: human taking the role of the system
* Simulation: executable prototype using prototype-specific techniques
* Partial implementation: executable prototype using implementation-specific techniques

For this project we recommend avoiding high fidelity prototyping, particularly simulation, as it can easily be misinterpreted as the final system. The limitations of low fidelity prototypes and partial implementations are clearer to users and clients, as well as being more cost-effective than high fidelity prototypes. We also understand that the short time available and the complex technologies of physical computing make it difficult to produce a partial implementation.

The Roman architect Vitruvius identified three qualities of good buildings, firmness, commodity and delight, corresponding to structural stability or strength, fitness for purpose, and attractive appearance. Somewhat similarly, usability guru Jakob Nielsen identifies two aspects of interactive systems to be considered: utility (what the system does) and usability (how the system looks and feels). (Nielsen has the soul of an engineer so he didn't consider delight, although he would probably argue it's a factor in usability). Any of these can be used to restrict the scope of a prototype or partial implementation, providing a focus for exploring particular aspects of a design. One of the aims of this project is to be very clear about which aspects of a design are being interrogated by the prototype or partial implementation.
Deliverables

The deliverables for this project are a demonstration of your prototype or partial implementation, and a pinup or poster documenting your work.

Your prototype or partial implementation is not expected to work perfectly or contain all of the final content or functionality. It should focus on particular aspects of the design, providing a basis for subsequent work to develop a full implementation. You should use it to interrogate and evaluate the design,

The pinup should identify what aspects of the design you are exploring (for example, commodity, firmness, utility, usability, etc) and show how your prototype or partial implementation explores the design. The pinup should document the limitations of your prototype or partial implementation as a basis for further work. It should also refer to the sources you have used in developing your prototype.
Schedule

This project spans weeks 10 to 12 inclusive. The detailed schedule will vary depending on the scope of your prototype or partical implementation. The overall schedule should be as follows:

* week 10: decided class of prototype to be built and initial overall work complete
* week 11: prototype ready for integration or evaluation
* week 12: pinup and demonstrator complete

For a partial implementation exploring utility the following items might be discussed each week with teaching staff:

* week 10
o overall architecture, including subset of functionality to implement
o list of proposed technologies, particularly those with risk such as lack of familiarity or novel application
* week 11
o separate pieces of partially implemented functionality
o documentation of research to gain knowledge, with identification of remaining gaps
* week 12
o pinup
o integrated of functionality into overall demonstrator

In contrast, a schedule for developing a visual prototype exploring commodity might involve completing the following items for discussion with teaching staff:

* week 10
o who will use the system? how? (user personas and/or scenarios)
o how will the prototypes be used to evaluate the design (evaluation plans)
* week 11
o separate initial paper prototypes
o user evaluations of design by prototypes
* week 12
o pinup
o integrated demonstrator of paper prototypes

For week 10 you should decide your overall approach and schedule for the project, and be prepared to discuss your initial work during the feedback sessions.
Assessment

The following criteria will be considered for assessing your work in this project:

* teamwork: team member engagement
* evidence of iterative process
* pinup: identification of design exploration and remaining work
* demonstration: evidence of research and completeness
* flair, originality, creativity (delight)