Assigned Date: Wednesday, Oct. 25, 2017
Due Date: Friday, Nov. 3
Due Time: 2 hours before class time
Last modified on November 06, 2017, at 01:37 PM (see updates)
This is a group assignment - you must work in teams of 2 or 3. See course collaboration policy for details.
This is the next phase of the semester project.
In the previous phase, we created and tested a paper prototype of your interface. This should have helped you refine the navigation, workflow, terminology and functionality of your UI.
In this phase, we will continue developing a higher-fidelity prototype of your system.
There are several environments out there for making medium-to-high-fidelity prototypes. These include Mockplus, InVision, Balsamiq, Proto.io, Fluid, Axure, Adobe Experience Design CC, Marvelapp, JustInMind, Form, and several others. Also see UpLabs.
Your first task is to select one them that supports higher-level prototyping of your system.
Search the web, and find the solution that works best for you. Then, provide your rationale for selecting it.
Each team should send a single email by Mon., Oct. 30, before noon. See below.
For this assignment you to do the following:
- Update your Google doc to reflect the latest version of all your materials, as they have evolved through heuristic and other evaluation and re-thinking. Things get refined. This document should hold the latest version.
- Select an environment for preparing medium-to-high-fidelity prototypes.
- Email your choice and rationale by Mon., Oct 30, before noon.
- State the name of your app.
- Include names and emails of all teammates.
- State the name of your prototyping system selection.
- Provide a URL.
- Explain what aspects of the environment made you select it.
- Prepare a demo of your higher-fidelity prototype to demonstrate in class on the due date.
- This prototype should support some (but not all) of your prioritized user tasks and user scenarios. In other words, you should implement some (but not all) of your user flows.
- Higher-fidelity prototyping requires more effort than paper-prototyping, so make sure you update everything you know needs updating *before* you start. Once you implement it, you can still make changes - but hopefully these will be smaller-scale (e.g., placement of things, icon choices, font choices, etc.).
- These prototypes will eventually be evaluated by your classmates for usability (e.g., see Norman's Design Analysis Concepts). So build with that in mind. Continue evaluation and refinement of your UI. Feel free to quickly paper prototype to try a few things out, before committing them to the higher-level prototype.
- By now you have realized that everything builds on everything else. So, be very attentive and careful. Refine. UI development is a living, breathing thing... Nothing is cast in stone, especially choices from earlier phases.
- Update your Google project document.
- Bring a hardcopy to class on the due date of your report, with:
- Application name, team names, class, date, etc.
- Be ready to demo your higher-fidelity prototype to the class.
- 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 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-20% of your grade).
- Submit your report in class on the due date to be graded.
- Again, this should include all components developed so far (updated to the latest, refined version).
- Also upload it on Google Drive.
- Update your Google doc to reflect the latest version of all your materials, as they have evolved now. Very important! It is OK to resolve earlier comments.
To be eligible for full credit you must follow these instructions carefully.
"Any amount of work can be done in any amount of time... only the quality varies." ~Joao Meidanis