CS 352 Project: Winter 2017

CS 352 Project, Winter 2017

Your mission is to design a substantial user interface, carefully and thoroughly following the methods and principles from CS 352. Guide your efforts by following the PRICPE process.

Project Ideas

As announced in class, any software project with a reasonably big user interface is fine. It can be a project you are involved in elsewhere, or not. HOWEVER, you do need to be able to observe/interview potential users.

Project Parts 1, 2, and 3: Proposal: (PRICPE)

Due date: See the main class web page. For the electronic part, use Canvas.

Your proposal should include the following:

  1. Name of team members
  2. Project description (what do you want to do)
  3. "P": predispositions. (From the perspective of factors that could affect USABILITY, what do you know, what do you NOT know?)

Typical length: About 1-2 pages for parts #1-#2, and about 1-2 pages for part #3.

Samples: Parts #1-#2, and Part #3.

Note about part #2: If you have doubts about the suitability of your project idea for this class, feel free to ask during office hours before the due date, so that you don't waste time developing an idea that I'm not likely to approve.

Grading Criteria for Proposal Parts 1 and 2

Graded by: Dr. Burnett, Total of 20 points

Grading Criteria for Proposal Part 3

Graded by: Charles Hill, Total of 20 points

Project Part 4: Your users (PRICPE)

Due date: See class schedule. For the electronic part, use Canvas

This is the "R", mainly from your formative empirical work, stemming from the "P" part of your proposal above. Note that since the process is iterative, it is indeed allowable to expand the "P" (research questions) as you progress with finding out more about your users.

The "R" will consist of in-the-field observations or in-the-field interviews of people who could be your users doing the task you are trying to support. (For example, if your users are supposed to be students planning their classes, then you should observe or field-interview students planning their classes. If your users are supposed to be grocery shoppers shopping, then you should observe or field-interview grocery shoppers shopping. Etc.) In addition, you may want to include other forms of research such as web research for additional concept ideas and so on, but we will not grade these other forms of research.

NOTE: Please avoid CS students as the users you observe/interview. You need experience learning to understand users not so much like you.

What to turn in:

  1. What are the research questions/goals (initially derived from the "P" in your proposal).
  2. Process: How did you proceed to answer these questions? Be detailed. For example, if you conducted an interview, list all the questions. Where and when did you collect the data? How did you set up to allow triangulation, etc.
  3. An exhaustive inventory of the elements we discussed in class:
    • The people in the space
      • 1. Who are they, what are they like?
      • 2. What are they doing?
      • 3. How are they doing it?
      • 4. What do their emotions, purposes, reactions seem to be?
      • 5. What problems do they encounter with their activities?
    • The objects (technological and otherwise) in the space and with the people
      • 1. What are the functional elements of the objects?
      • 2. What are the decorational elements?
      • 3. Which objects do people look for (perhaps to somehow interact with)?
      • 4. Which objects do people bring with them that matter to the activities they are trying to do?
    • The environment: spaces, architecture, lighting etc
      • 1. What is the layout?
      • 2. What is the environment like?
      • 3. How does it influence the activities people engage in?
      • 4. How does the environment support the objects above?
  4. Attach your raw data: detailed observations or interview responses (verbal and non-verbal)
  5. With the detailed observations/responses, point out the places that provide Results/Insights and say what they are ("I"):
    • What are the answers to your research questions?
    • What other insights did you get from this that are relevant to your design?

What am I looking for:

Expected length: 6-10 pages, including words and sketches. For sketches, feel free to scan them in instead of drawing them on the computer.

Note: You can combine things into one file, or turn in separate files if it's easier (eg, a separate one for sketches?). The Canvas site will support several separate files.

Sample.

Grading Criteria for User Data Assignment

Graded by: Charles. Total of 30 points

Additional notes:

Project Part 5: Concepts and early Prototype #1 (PRICPE):

Your team will prepare a poster with the information below, to be presented at Design Studio 1, for brainstorming and feedback. See main class web page for the date.
Also turn in the pages from your poster electronically by 11:59 pm. Make sure everything turned in is readable. Use the Canvas hand-in page.

Present the following:

Notes on constraints on your concepts/prototypes:

How you will be graded: This prototype will be graded based on how well you addressed the details I asked you for (see list in this subsection). This score will contribute a portion of your eventual grade for the prototype portion of the project.

Expected length: enough to fill up a poster, which will probably be 6-8 pieces of paper containing sketches, justifications, explanations, background. As usual, feel free to scan in sketches instead of drawing them on a computer.

Sample from a prior year (not exactly the same as this year's specs, but gives some reasonable ideas).

Give feedback to other teams here from Design Gallery #1 (until Feb. 12)

Grading Criteria for Design Gallery #1

Graded by: Charles, Total of 100 points

Project Part 6: Evaluation preparation (PRICPE):

Due date: See main class web page for the date. Use Canvas hand-in page

In the assignment after this, you'll need to evaluate an updated version of the prototype you presented in Design Gallery #1. This assignment is to do some preparatory work to help make that possible.

Heads-up: By the time of your actual analytical evaluation (next assignment), your prototype will need to be in Mockups (even if it is just a scan in of sketches with widgets/transitions added). The updated prototype will need to support some user in your target population doing some task that's fairly central for your prototype (which we will call a scenario here). For example, if you are EmpCenter, your scenario might be "enter my hours for this week".

But for this assignment, all you need to turn in is:

Here is more information that will be true for every team's Abby:

Looking ahead: You will be using this scenario, this version of Abby, and your updated Mockups prototype in your upcoming analytical evaluation assignment.

Grading Criteria for Evaluation Prep

Graded by: Dr. Burnett, Total of 3 points

Project Part 7: Analytical Evaluation with GenderMag CW (PRICPE):

Due date: See main class web page for the date. Use Canvas hand-in page

Perform a GenderMag Cognitive Walkthough (CW) on an updated version of the prototype you presented in Design Gallery #1 that is now in Mockups (even if it is just a scan in of sketches with widgets/transitions added). If your scenario did turn out to involve at least 4 user actions that changed screen state, you'll be evaluating the scenario you turned in for the Evaluation Prep, from the perspective of the Abby you also turned in for the Evaluation Prep. (Otherwise, fix the scenario and Abby first.)

For example, if you are Augmented Reality Navigation team, you might be evaluating Abby driving from class to Starbucks on her bike using your system, which might involve the following 5 user actions:

  1. Abby getting the map going (eg, with a single voice command),
  2. Abby then pedaling her bike as per the map to the first turn,
  3. Abby then pedaling her bike as per the map to the second turn,
  4. Abby then having to turn quickly to avoid a huge obstacle she can now see through the glasses,
  5. Abby then turning her bike according to the map's rerouting.

To do the evaluation, follow the instructions in the highlighted GenderMag kit (Canvas).

Opportunity: Have this assignment be part of GenderMag research

Summary: If you wish, your work on this assignment can become part of the GenderMag research, by scheduling your work session in a particular lab in KEC. In exchange, each team member who does this will be paid $20 at the time they do the assignment. I won't be told who participated in the research vs. who just did the assignment on their own until after I turn in grades for Winter term. Details are here.

Hand-in instructions, what I'm looking for

Either way, here's what to turn in:

What I am looking for:

Grading Criteria for Analytical Evaluation

Graded by: Charles, Total of 50 points

Note: the 4 highest-graded actions were considered for the assignment's final grade. All actions were graded; even if your team scored 100% on the CW portion, there may be actions within the walkthrough about which you received some feedback.

Project Part 8: Empirical Evaluation (PRICPE):

Due date: See main class web page for the date. Use Canvas hand-in page

Perform a usability study, using the think-aloud technique, in which a user performs one or more tasks you give them on a portion of your Mockups prototype. As in other usability studies, your goal is to find out what usability problems this part of your prototype has. The user's task(s) must involve a total of at least 8 user actions.

What to turn in:

Samples: Sample #1. Sample #2. Note: the requirements for this assignment were different for these samples, but they will still give you some ideas.

Prototype #2 (Mockups) (PRICPE):

For brainstorming, feedback at our Design Gallery. See main class web page for the date.
Also turn in the pages from your poster electronically the same day. Use the Canvas hand-in page. (Although the runnable Mockups prototype needs to exist for your poster, you do not need to turn in the actual prototype.)

Present the following. All materials must be READABLE by human eyeballs. :-)

Sample. (Somewhat different specs that year and different prototyping tool, but still gives an idea.)

Give Design Gallery #2 feedback to other teams here (until March 12)

Final Prototype (Mockups) and Team Presentation:

Due date is on the main class web page.
Turn in your "runnable" Mockups prototype AND supporting documents electronically on the due date. Use the Canvas hand-in page.

In addition to the "runnable" Mockups prototype, the supporting documents are:

Give teams feedback on their presentations here (until March 17)

Your final prototype will be graded on the strength of connection between usability design principles and your users with the decisions you made. Be sure to include plenty of justifications from all three of: (1) design principles, (2) your analytical work (GenderMag), and (3) your user-based empirical work (early observations and later evaluation). Justifications based on other kinds of research/feedback are fine too, but don't neglect those first three. In summary, the more justification for each design decision based on HCI principles and the "Research" and "Evaluation" aspects of PRICPE you have experienced, the better your grade.


Date of last update: March 9, 2017