Assigned Date: Wednesday, Oct. 14, 2015
Due Date (Phrase 1): Done (see Homework3)
Due Date (Phrase 2): Done (see Homework4)
Due Date (Phrase 3): Monday, Nov. 16
Due Date (Phrase 4): TBA
Due Time: 11:20am
Last modified on November 11, 2015, at 11:24 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 2 (where you created a hierarchical task analysis for an innovative application you proposed, combining a smartphone and a computer).
Develop and refine a new paper prototype, informed by your hierarchical task analysis, for your particular application. This paper prototype should include any menus present, and should identify all JythonMusic GUI library objects used to build it (as annotations).
The goal of this activity is two-fold:
- improve / refine your design as a result of your task analysis; and
- identify GUI implementation components (functional feasibility)
Given the application that you and your teammates have selected to work on, create a paper prototype of your UI. This prototype should fully support / implement at least two of the user tasks analyzed in the previous phase.
In other words, via your paper prototype the user should be able to achieve at least two distinct user tasks (as identified in the previous phase).
At least one of the tasks should make use of the smartphone part of the UI (where the smartphone use is integral in achieving the task - not contrived, or peripheral / superficial use).
Phase 3 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 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
- User tasks supported by the prototype (include full specification - copy from last phase - it is OK to refine / improve). In bold (or some other way), identify which task subhierarchies are meant to be supported by your UI prototype submission (below). Also include plans (if any - see lecture notes).
- Paper Prototype (provide full illustrations, e.g., take photos with a camera and paste into the document - provide meaningful captions for all figures included, so someone outside of your team can figure out what they are seeing).
- 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 paper prototype 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.