ICS 667: Advanced Human Computer Interaction Design Methods

General Info

Overview

Readings

Format

Projects

Assessment

Instructor

Course Management

News

Schedule

Assignments

disCourse

Assignment 2: Requirements Analysis for Collaborative Calendars

The purpose of this assignment:

Learning by doing a variety of techniques for requirements analysis proposed by Rosson & Carroll, Constantine & Lockwood and Preece. By practicing the techniques on a "simple" problem we become clearer on how the techniques are to be used. We can then decide for ourselves whether these techniques will apply to our term projects.

Please do the following:

You should turn this work in as individuals, but may work with up to 2 other students to discuss the assignment and try the methods on each other.

• Read chapter 2 of Rosson & Carroll, Chapter 4 of Constantine and Lockwood, and the Preece et al. handout. Also review my lecture slides.

• Perform a requirements analysis for the following application:

  Collaborative Calendars: Analyze how people use their personal calendars, with particular attention to how they coordinate scheduling with others. Your objective will be to improve personal calendars to better handle collaborative aspects.

  (You have a choice: you may assume that the calendar is used in a business workgroup, or you may assume it is used for informal social schedules. Just make your choice clear in your Root Concept.)

  1. Prepare your project using the Root Concept document.
  2. Then use the Root Concept as a guide to develop an Interview Guide.
  3. Interview at least one user of calendars.
  4. Then create requirements documents reflecting what you learned in this interview. Ideally you would take your documents back to the user for a follow-up discussion and revisoin.

     Your analysis should include the following (the links are to template documents):

     • Root Concept (doc)
     • Interview Guide (doc)
     • User Role Model (doc) and User Role Map (ppt) if needed
     • Artifact Analysis (identify information and procedures implied by the artifact)
     • Problem Scenario (freeform text: no template needed) and Claims Analysis (doc)
     • Hierarchial Task Analysis (to model task)
• Make a web page that tells the story of your requirements analysis and includes all of the documents you created. Write a page (paragraph or two) summarizing your view of the utility of the methods, and how they might profitably be combined together on future projects.
• Submit your assignment in disCourse (the URL of your page will be the artifact).
• Comment (substantially) on the work of the person who posted before you (and any others you find interesting).

Due 2/2