Project - User and Task Analysis

From Cmsc434_s10
Jump to: navigation, search

(Due: 3/1, 2pm)

Ucd requirement.png


The second deliverable of the term project is a detailed user and task analysis. The objective of the analysis is to understand users, their tasks, and the context in which the tasks are performed. A sound analysis will allow your team to come up with good initial designs in the next step.

  • In the lecture, we've covered several data gathering techniques for user and task analysis, such as interview, focus group, questionnaires, direct observation, indirect observation, studying documentation, and researching similar products. Identify 3 techniques that you believe are applicable to your project. For each technique, describe how you would apply it. For example, for interviews, you can prepare a list of questions you would ask and decide whom you would interview. For questionnaires, you can design a questionnaire, decide to whom you would distribute questionnaires, and plan how you would distribute them. For direct observation, you can describe where you would observe users and what you would observe.
  • Carry out one of the 3 techniques you've identified. Indicate which technique you’ve decided to use. The technique should involve at least one subject, more the better. Describe your subjects and indicate their types (e.g, clients, existing or potential customers, friends, colleagues, user representatives).
  • From the data you’ve elicited from the subjects about the users, identify at least three 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).
  • 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 (three times a week).
  • Identify other potential stakeholders who are not users of your system but may be indirectly affected by the success or failure of the system.
  • 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.