Assigned Date: Wednesday, Oct. 14, 2015
Due Date (Phrase 1): Done (see Homework3)
Due Date (Phrase 2): Done (see Homework4)
Due Date (Phrase 3): Done (see Homework5)
Due Date (Phrase 4): Monday, Nov. 30
Due Date (Phrase 5): TBA
Due Time: 11:20am
Last modified on November 29, 2015, at 01:19 PM (see updates)
This is a group assignment - you must work in teams of 2 or 3. It is not okay to work alone. See course collaboration policy for details.
You have been hired by Artle, a start-up, daughter company of G**gle (name withheld due to non-disclosure agreement), whose purpose is to explore the new, lucrative market in the intersection of art (music, visual, theater, performance, etc.) and computing. The belief is that this where the new multi-billion user market will emerge in the 21st century (the area is untapped territory), and G**gle is trying to develop a portfolio of possible projects / apps to capture a major share of it (in the spirit of G**gle innovation).
This is a continuation from Phrase 3 (where you created a new paper prototype, informed by your hierarchical task analysis, for your particular application combining a smartphone and a computer).
Select two representative user tasks, and then
- perform cognitive task analysis (GOMS), and
- apply the keystroke level model (KLM).
You are trying to measure (a) the high-level cognitive cost (GOMS), and (b) the time it takes to perform low-level actions at your UI. See provided handouts on how to do both techniques.
Your goal is to find ways to improve the UI by reducing:
- the cognitive cost (GOMS), and
- the number of low-level actions (KLM).
You will submit both analyses (GOMS and KLM).
Your goal is to demonstrate how these helped you to improve your UI.
Phase 4 requires no traditional implementation (i.e., coding). Your success depends on the quality you infuse to your product / idea at this stage. Treat this as an opportunity for improvement - even radical - no code has been written yet to cement things.
Produce a report (PDF), with the following outline:
- Names, class, date, homework number, etc.
- Name of application
- User goal
- Representative user tasks used in the analyses.
- The GOMS analysis (see provided handouts).
- The KLM analysis (see provided handouts).
- An explanation of how these analyses have helped you improve your UI (compare GOMS and KLM costs before and after the improvements).
- Your report should have sections that follow the above outline. Include figures and illustrations that give substantive help to the reader in understanding the user interface, etc. You are encouraged to use screen snapshots and other graphics (e.g., diagrams) for elucidation. However, avoid decorative graphics/pictures.
- 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 key points of your idea / work.
- 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 are the tasks they would want to accomplish with your report?
- Hand in your report printout in class on the due date to be graded.
- Also upload it on OAKS in PDF format.
- Bring your GOMS and KLM analyses to class and be ready to try it out / refine it with sample users.
Failure to follow these instructions will result in reduction of grade.