ICS 667: Advanced Human Computer Interaction Design Methods

General Info

Overview

Readings

Format

Projects

Assessment

Instructor

Course Management

News

Schedule

Assignments

disCourse

 

Assignment 9: Project Requirements Analysis Results

The purpose of this assignment:

  • To gain practice with various data gathering and requirements analysis methods
  • To document the results of your data gathering and requirements analysis
  • To evaluate the utility of the various requirements gathering and analysis methods
  • To prepare for conceptual design

Please do the following:

You will have two weeks to do this assignment, including spring break. It requires that you work with actual users, and then analyze the data gathered. Plan ahead and get started early!

The details of this assignment depend on your project. (If your project is following an entirely different trajectory through the star model, just let me know and we'll negotiate different requirements for this assignment.) In the normal case there will be two parts to your requirements analysis.

1.The raw data you got from your interviews and/or usability testing.

This might include responses to questions, artifact analysis, workpace observations, usability defects noted, and/or benchmark data. Summarise your results, or show us as much as you think is useful for us to see.

2. The requirements you derived from this data.

You may choose to represent your requirements in any of the following ways:

  • Claims Analysis. (Scenarios MUST include claims analysis. However, you can do claims analysis without scenarios if you are getting the features to analyze from some other method.)
  • Problem Scenarios with claims analysis (SBD). Don't forget that in addition to the stories you will describe the fictional users.
  • Hierarchial Task Analysis (for functional requirements)
  • User Role Models (UCD)

We did not study these but you could also try:

  • Dataflow Diagrams (for functional requirements)
  • Entity-Relationship Diagrams (for data requirements)

Other notations will be considered as well. Post questions to disCourse under Assignment 9.

3. Discussion of methodological lessons learned.

A discussion of what you learned about the value (or lack thereof) of the requirements analysis methods you tried for this particular project. Which seemed to better capture the requirements of your project? Which led you to realize something unexpected about the requirements? This will be a few paragraphs to a page written by your entire group. Please do not delegate this part to one person: it is important for your learning that you evaluate the methods together.

Compile this material into a web page and post to disCourse under Assignment 9. Then view and comment on the requirements for some other projects. Remember, online discussion is part of your grade! I will comment quickly on your assignment, but don't wait for my comments: start on Interaction and Information Design, as time is tight.

Due midnight 3/26

To be discussed in class 3/28, so we need to review them 3/27


Back to Top