When each course project is submitted, submit documentation for it at the same time. (Each project posted on the COL course submission site has an accompanying document submission site). Submit the documentation as a MS Word .doc file.
The documentation for each project must contain the following sections.
Explain briefly why you made the choices you did in your design. Why did you reject other choices.
Draw a sketch or sketches by hand of your user interface. Then scan in your sketches include them in your document. Alternatively, include an MS Word drawing or drawings of the user interface. Also include comments that would help me understand your sketch.
Show your low fidelity designs and specifications to the other people in your small group to get feedback. You will similarly give feedback for the other people's designs in your group. In this section, explain how you used this feedback to alter your user interface design or confirm your choices. Also discuss the feedback that you did not use. You can also incorporate feedback from people outside of your small group.
Give any directions that are needed to properly use your prototype. If your directions are long, it probably means that the user interface for your prototype is too complicated. If you expect that it will be obvious to the user how to use your user interface, just write "self-explanatory" for this section.
Give very specific directions of controls to set and buttons and/or menu items to push to adequately test your application. For each action that the tester makes, also specify the response expected from the software.
Although this is not part of your submitted document, you will be graded on the postings that you make on the discussion board for your group when returning comments to other group members on their proposed designs.