Assignment 6 - Design Revisions or Radical Revision
In this assignment, you will choose one of two deliverables. Either design revisions (in which you make changes to your project) or a radical revision, in which you drop all of your project deliverables and continue forward. Read on for more instructions.
Design Revisions (Choice 1)
For this task, you are going to make revisions and design a new version of your paper prototype on the computer. Your goal is to build a digital version of your paper prototype on a digital interface. This is still a low-fidelty prototype however (no code).
- Build a digital wireframe emulating your paper prototype. You may use HTML, Powerpoint, or other wireframing softare. You should not use C++, Java, SQL, or other technologies you would implement your prototype with.
- You can use "canned data" within your prototype, just as you did with your paper prototype.
- You should have a discussion of changes you made based on your pilot study with your paper prototype. The discussion will include
- What changes have you made to your design, task list, script, and questionnaires after your revision?
Radical Revision (Choice 2)
Sometimes a product does not work, and you would rather find this out sooner than later. That is why we do things like paper prototyping (Imagine you had spent 7 weeks programming an interface, when you could have made a paper version in a day!)
- Project Postmortem - A postmortem in the software/hardware industry is a report of what did not work well. You will write 2-3 paragraphs about why you are abandoning the project. What challenges were you facing, why was this project going to not work, and what lessons did you learn going forward.
- Because you are starting from scratch, you will write a brief design document of your new project (maximum of two pages). It will include the following:
- A few sentences about your new product.
- A bulleted list of the user analysis.
- A task analysis with 2 usability goals (The goal, what the user does, and what the system does).
- One functionality of the system, and 2 usage scenarios.
- Finally, you will draw a mockup of what your interface looks like on a whiteboard or paper and take screenshots of it.
- You will capture one of your team members using or walking through your interface in a one minute video.
*One rule with the radical revision. All of your team has to commit to the radical revision.
Change Log, Guidelines, and update
Provide a list of changes if you have made any (If you did the radical revision, then your log will be empty). Also spend time updating your guidelines document from the previous assignment. If you have made any major changes in your assignment, include a brief paragraph or bulleted list as well.
Assumptions
Throughout your assignment, state any assumptions that you may have. In each catagory, the goal is that this is self-evident, but you may add additional information as you see fit.
Organization
Please use bulleted lists and tables where appropriate. Start to think of your deliverables as a blueprint, such that another team in the class could follow along with your project. Use pictures, video, and add elements as you see appropriate. Be sure to cite all references!
Grading Rubric and Submission
You will submit your homework as a pdf on Blackboard for the CS 5340 course. Please do not e-mail me your submission. You may use tools like Google Docs, Microsoft Word, or Libre Office to generate .pdf files for submission.
The following rubric will be used to evaluate your work for choice 1:
- 40 pts for at least 3 screenshots of your wireframe.
- 20 pts for a one minute video of one of your teammembers using the prototype (This is an in-house usability test).
- 40 points for the discussion of changes you made and things you learned since your paper prototype.
The following rubric will be used to evaluate your work for choice 2:
- 20 pts for a project postmortem.
- 40 pts for at least 3 screenshots of your mockup and the 1 minute video.
- 40 points for the design document