Assigned Date: Wednesday, Oct. 14, 2015
Due Date (Phrase 1): Done (see Homework3)
Due Date (Phrase 2): Friday, Oct. 23
Due Date (Phrase 3): TBA
Due Time: 11:20am
Last modified on October 25, 2015, at 04:11 AM (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 1 (where you proposed an innovative application combining a smartphone and a computer and received some feedback via a design critique session and paper prototyping).
Develop and refine a task hierarchy (i.e., hierarchical task analysis), for your particular user audience and application.
Given the application that you and your teammates have selected to work on, identity the following:
- User audience - the target audience for your application.
- User goal - the goal the user is trying to achieve (e.g., "I want to swing like a pro"). As discussed in class, a user goal is independent of a particular device (or application). You hope the user will choose to achieve this goal through the application you are developing (if you do your job well).
- Hierarchical Task Analysis (HTA) - identify main tasks (4-8 or so), and subdivide them into subtasks (4-8 or so, per higher task). Continue the analysis until you reach actions (low-level tasks which require no problem solving). Specify plans associated with each task, when necessary. Use the examples / guidelines provided in class to guide you.
Phase 2 requires no traditional implementation (i.e., coding), but is full of important, meaningful implementation activities that will set the stage for what follows. Be very attentive and careful. Your success depends on the quality your infuse to your product / idea at this stage.
Produce a report (PDF), with the above outline.
As usual start with:
- Names, class, date, homework number, etc.
- 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?
Submit your report in class on the due date to be graded. Also upload it on OAKS in PDF format.
Bring your task hierarchy as a paper prototype (using sticky notes) to class and be ready to discuss it / refine it with sample users.
Failure to follow these instructions will result in reduction of grade.