Skip to main content
Get your Wikispaces Classroom now:
the easiest way to manage your class.
Pages and Files
Accessibility - math department website
Accessibility - Philosophy Department
Accessibility - Tammy Tran
Accessibility Assignment SEE
Accessibility Submission, Andrew Palma
Accessibility Submission, Ghassan Abu-Ghaida
Accessibility Submission, Ian King
Accessibility Submission, Janahan Sivaraman
Accessibility Submission, Kevin Van
Accessibility, Jennifer Gorski
Accessibility, Mark Stewart
Accessibility, Matt Orlove
Aida's Home Page
Aida's Login Page
Add "All Pages"
30%: Phase #6: Project Conclusion
This concludes the project. In this final phase, you will make final revisions to your software prototype, make a presentation to the class, and write a report about your project. The teams will be split randomly with half presenting on Monday (Dec 5) and half on Wednesday (Dec 7). To balance the extra two days the Wednesday teams get to prepare their presentation, their report will be due on Monday while the teams presenting on Monday will have until Wednesday to submit their reports.
10%: Updated Prototype
You should improve the software prototype, addressing the key usability problems you discovered in the user test.
Each team will have about 10 minutes for their presentation including questions, so you should plan on talking for no more than 7 minutes for your presentation, leaving 2 minutes for questions. You should cover the following points in your presentation:
Name of projects, and team members
Statement of the problem & current competitive solutions
Approach to solution
Demo (or slides of application)
Usability test method
Usability test results
This should be a standalone report that can be read on its own. You are free to copy and reuse elements from previous phases of the project. Your report should include the following points:
Introduce the problem you are addressing
Credits: describe who did what
Describe who your audience is
Describe competitive solutions and what deficiencies are with those solutions.
Describe your solution.
Give overview of your approach
Present all screens you have designed with commentaries to explain (do screen grabs).
Show transition diagram for screens i
n your design. It is sufficient to use screen names instead of screen grabs as long as it is unambiguous what screens are being referred to.
Describe the tutorial, help, or any assistance you gave to learners of your system
Describe your usability study including how you ran it, how many participants there were and their demographic characteristics (but don't include personally identifying information!). Summarize the problems you discovered and describe what you changed in your final prototype to address those problems.
Finally, describe open issues you are aware of, and what the next things you would do if you were to continue working on this project.
Link to your updated project, presentation, and report from your project page
Fitness Buddy Finder
The Any Key
help on how to format text
Turn off "Getting Started"