** Screenshots of your high-fidelity prototype*** '''Arrange these screenshots in terms of the most important prioritized user tasks'''. *** Identify a task, and then show the user flow through the prototype, in terms of screen shots. Repeat for a couple of other tasks.*** It is OK to include the same screenshots across different tasks. Your goal is to best communicate to the reader what they would see if they were using your system interactively. So, such repetition is useful.

** the complete outline of material (see last version)** the UI prototyping tool you used (name / URL)** the rationale as to why you picked it (e.g., see email you sent earlier)** an online link to your prototype (if your prototyping tool allows this)*** if your prototyping tool does not allow this, provide an explanation as to why this is not available.

# Video of your system. This should be like a Kickstarter video that presents your concept, and your work to the world. See useful [[https://www.youtube.com/watch?v=L3h828EtWoA | Kickstarter video instructions]].

# Video of your system. ** This should be like a Kickstarter video that presents your concept, and your prototype to the world. See useful [[https://www.youtube.com/watch?v=L3h828EtWoA | Kickstarter video instructions]].** A target duration is 3 minutes in length (+/- 2 minutes or so). But use as much time as you feel is needed.

Changed lines 50-51 from:

More information will be provided soon.

to:

* You should include some of the material / outline in the final project document.

In this phase, we will finalize your high-fidelity prototype, finalize the project document to be consistent throughout, and create a video that demonstrates your work to the world (due on day of final).

to:

In this phase, we will finalize your high-fidelity prototype, finalize the project document to be consistent throughout, and create a video that demonstrates your work to the world.

Changed lines 19-20 from:

The first two items are due Friday, Nov. 18 (as mentioned above).

to:

The first two items are due Friday, Dec. 7 (as mentioned above).

Changed line 30 from:

** the rational as to why you picked it (e.g., see email you sent earlier)

to:

** the rationale as to why you picked it (e.g., see email you sent earlier)

This is a group assignment - you must work in teams of 2 or 3. See course collaboration policy for details.

!!Assignment

This is the final phase of the semester project.

In the previous phase, we focused on bringing your project document up-to-date, and creating a high-fidelity UI prototype.

In this phase, we will finalize your high-fidelity prototype, finalize the project document to be consistent throughout, and create a video that demonstrates your work to the world (due on day of final).

!! Deadlines

The first two items are due Friday, Nov. 18 (as mentioned above).

The video is due two hours before the final exam. It should be uploaded in the Projects folder (Google Drive).

# Final project document. This should include:** the complete outline of material (see last version)** the UI prototyping tool you used (name / URL)** the rational as to why you picked it (e.g., see email you sent earlier)** an online link to your prototype (if your prototyping tool allows this)*** if your prototyping tool does not allow this, provide an explanation as to why this is not available.

# Video of your system. This should be like a Kickstarter video that presents your concept, and your work to the world. See useful [[https://www.youtube.com/watch?v=L3h828EtWoA | Kickstarter video instructions]].* Here are some examples of UI prototype videos: [[https://www.youtube.com/watch?v=rdXz5HdW3oE | video1]]* Your video should start with a title page, and include screens with words to separate video into meaningful sections (e.g., see [[http://www.cs.cofc.edu/~manaris/?n=Main.ResearchProjects | these videos]]).

More information will be provided soon.

!!!Notes

* As per course collaboration policy, there should be no discussion of any kind about this assignment (and possible solutions) with any person outside your team other than the instructor. '''You are not allowed to discuss/look at someone else’s solution (including material in books and the Internet) or show your solution to someone else outside your team other than the instructor'''.

* Include references''' on materials (other than the textbooks and handouts) you consulted to do the assignment.

!!Grading

Grading will be based on your ability to carefully and succinctly identify the above key points. * Work for clarity, succinctness, and effectiveness. * ''Hint'': It might help to think of your report as a (meta) user interface, and your classmates as your end-users. What is their goal in reading your work? What tasks they would want to accomplish? Help them achieve those tasks.

Grading may also be based on the quality of your evaluation of others' work (e.g., 10% to 20% of your grade).

!!Submission

# Submit your final project document in class on the due date to be graded.

# Also upload it on OAKS in PDF format.

# Upload your video to the Projects folder on Google Drive (due on day of final).

To be eligible for full credit you must follow these instructions carefully.

!!Relevant Quote

"Any amount of work can be done in any amount of time... only the quality varies." ~Joao Meidanis