Homework D2

From Cmsc434_s10
Jump to: navigation, search

Due: 5/11 (the last day of the class)

In this design homework, your mission is to design a computer prototype of an application to support post-disaster family reunification. The learning objective of this homework is to give you an opportunity to practice the skills and knowledge you have acquired from this course in a real-world interaction design problem. You will go through an iterative design process similar to that for your team project. To limit the scope of this homework, the computer prototype only needs to be high-fidelity in appearance. The design document only needs to include the following parts:

  • User Classes: Identify distinct user classes. For each user class, list its defining attributes including age, education, job, computer skill, computer experience, location, motivation, attitude, social context, and usage pattern. Each attribute can be expressed as a range of values (e.g., age: 18-22), a general term (e.g., job: small business owners), an abstract quality (e.g., usage pattern: frequent), or a list of possibilities (e.g., location: home and office).
  • Personas: For each user class, create a persona. The persona should include a concrete and representative value for each class attribute, for example, an actual age (32), an actual job (manager of a Starbuck), and a concrete quantity (ten times an hour).
  • Tasks: List all the tasks you’ve identified. Name each task, describe its goal, preconditions, and subtasks. Also indicate its complexity (e.g., low, medium, high), frequency (e.g., only once, a few times, often, every time), and potential user errors (e.g., user entered a wrong password) if any.
  • Scenarios: Identify the three most important tasks. For each task, create a scenario to illustrate how a typical user may use the application to accomplish it. Each scenario should be centered on a persona you’ve created.
  • Major screens: Design the major screens to support the scenarios. For each major screen, create a preliminary design sketch by hand. Then, implement the look and feel of the design using a computer software (e.g., Flex builder or Photoshop). Include the pictures of the design sketches and the screenshots of the computer rendered screens in your design document.
  • Computer storyboard: For each major task, include a series of screenshots showing how the UI changes as a typical user goes through the steps involved in the task.


Unlike other homeworks, you will NOT submit to the course Wiki directly. Instead, you will submit a pdf of your design document by emailing it to tomyeh @ umiacs.umd.edu


Five outstanding design awards will be selected by a panel of judges including HCI professors and members of the Maryland Emergency Management Agency. Each award recipient will receive a 2% boost to the final grade. In addition, announcements will be made on the course Wiki and on the HCIL's homepage for bragging right.


People who have submitted:

  • Robin Brewer
  • Corey Richardson
  • Joseph Isaac Jr.
  • Jeff Jacobs
  • Frank Cannavo
  • David Forsythe
  • Mekias Yohannes
  • Jason Covey (am I supposed to add my name here after submitting or does the Professor do that?)
  • Luis Sanchez (I assumed he would but just in case I guess)
  • Asmi Joshi