Fall 2017»CSCI 380 Homework 4

CSCI 380 Homework 4

Assigned Date: Monday, Oct. 9, 2017
Due Date: Monday, Oct. 16
Due Time: 2 hours before class time

Last modified on October 09, 2017, at 02:06 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.

Continue development of an innovative user interface.


For this assignment you are to specify the following:

  • User Scenarios: Develop at least three user scenarios that demonstrate how users may flow through the user interface to achieve their tasks. (First, make sure you update your personas!)

    Each scenario is a story involving one of your user personas, which describes how that persona flows - in terms of tasks - through your app to achieve their goals.

    For example, think about the following brief outlines of different user scenarios for Amazon. Each of these would be used to create a separate scenario:
    • searching for a particular item, looking at a few options, and saving something for later (but not buying)
    • trying to return a purchased item
    • looking through earlier orders for a missing invoice
    • checking when something will arrive
    • leaving comments for a purchased item
  • Prioritized User Tasks: Create a prioritized list of tasks - 7 +/- 2 (or so) for your app. Most important should be listed first.
  • Paper Prototype: Develop a paper prototype of a UI that supports the above user scenarios and prioritized user tasks.
    • Include clear photographs carefully labeled (e.g., 1st screen, 2.1 screen, 2.2 screen, and so on), so one can easily follow the user flow through them.
    • State the user action that leads to a transition between your screens (e.g., user selects... or clicks on..., etc.).
    • Let the above user scenarios guide you on how to order your screens.

This assignment 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.


  1. Bring your paper prototype to class on the due date.
  2. Update your report on Google Drive to include the above. Also update the original material to reflect your new, improved understanding of your system. In particular,
    • Update things that were noted as "(fix)" in graded work.
    • Incorporate other comments contributed by evaluators.
    • Update evaluation heuristics, as there is new stuff to evaluate (hint: conceptual model!).
    • Failure to do so will result in reduction of grade.

Everything in your report should be consistent and fit smoothly together (including your evaluation rubric).


  • Your report should have sections that follow the specified outline. If you include figures and illustrations, you should do so only if they give substantive help to the reader in understanding the concepts presented. You should 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.


  • Bring your paper prototype to class.
  • Bring a hard-copy of your report in class, on the due date, to be graded.
  • Also, upload your report to the shared Google Drive folder, called 'Hmwk3'.
    • Name your report 'AppName.CSCI380-hmwk4', where
      • 'AppName' is your application name;
      • for example, YouTube.CSCI380-hmwk4 or Snapchat.CSCI380-hmwk4.
  • You can see others' reports, but do NOT modify them in any way. (Google Drive keeps track of all changes - so be careful.)
  • Do not make any changes to the shared folder structure (e.g., do NOT create any other subfolders, rename files, etc.).


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., 20% of your grade).

To be eligible for full credit you must follow these instructions carefully.

Relevant Quote

"Any amount of work can be done in any amount of time... only the quality varies." ~Joao Meidanis