site map
 
  SIMS Home | IS 214 Home | Textbooks | Schedule | Readings | Assignments | Class Notes | Grading  

 

 

IS 214: Needs Assessment and Evaluation of Information Systems

Assignments and Final Project

Your project is to perform a preliminary needs and usability assessment on a software product or web site. You may choose an existing system or service, or one under development. The more real it is, the better the project. You will write a plan and document the results of your assessments in a report to be used by the design and management teams.

Your report should include, at a minimum:

  • A statement of the purpose of the user interface to be evaluated.
  • A plan including objectives and schedule for assessments.
  • A description of the target users.
  • A list of tasks being addressed in the assessments.
  • A plan and partial results for assessments in at least three of the following categories:
    • High-level design evaluation
    • Competitive evaluation
    • Inspection / heuristic evaluation
    • Iterative usability tests
    • Guidelines evaluation

For each assessment method you use, document the following:

  • Your rationale for choosing the method, why it is appropriate for this site and this audience.
  • Any assessment materials, e.g. scenarios and user questionnaire from usability test.
  • Results from performing the assessment. These can be partial, e.g., one or two users when you intend to test or survey many more.
  • Recommendations for design changes based on the assessment results.

Your report should detail and justifying further assessments that you plan to undertake. Include in your justification the likely benefits of the assessment for the organization, the service or site assessed, and the target users. Also include in your report a discussion of possible larger impacts and issues that might result in revised goals for the site, or a revised implementation. The idea is to consider issues at many different levels, not to be stuck in only looking at, say, the interface.

Don't consider yourself limited to what's described above. Part of your responsibility is to determine what will be most useful in matching this site to its users' needs.

Assume that your management is skeptical about the benefits of what they fear could be a time-consuming and costly project. You must both answer their concerns and ensure that the project is as lean and fast-paced as possible to get good results.

Due Date
Assignment
Feb 7
Project choice and UCD plan with objectives and dates (draft)
Feb 14
Target users defninitions / matrix (draft)
Feb 28
Task list for project, methods for gathering/prioritizing tasks (draft)
Mar 14
High-level design exploration and/or competitive evaluation results (draft)
Mar 21
Inspection / heuristic evaluation results (draft)
Apr 11
Iterative design plans and test results (draft)
Apr 18
Guidelines evaluations (draft)
May 2
Final project report