INL 650                  Summer 2003               Project – Initial Report

 

Assigned: 5/22/03

Due: 6/05/03

 

This is the first stage of a semester-long project. You should work in groups of 2-3 people.

Choose a project. Try to make your choice 1) not routine, 2) not something that is already done successfully, 3) not of proprietary interest  - we will be sharing these projects; 4) Of some complexity; interesting from an interface standpoint (processing is not a focus); and 5) it will be useful to have a project that is not too specialized (i.e. there are many potential users) as you will need access to prospective users for some aspects of the project.

            Over the course of the semester you will be developing prototypes and evaluating your design, and presenting your work. You will not create a full system.

 

In the initial report, you need to understand the tasks being supported and prospective users. If practical for your project, it is desirable to a) see current interfaces if they exist, and b) interview possible prospective users. Your report should include:

·        Problem statement (or product concept)

·        User analysis – what are the characteristics of the prospective users?

·        Needs analysis – what do the users need?

·        Task analysis – what tasks will be supported? – what are their steps? Further questions to consider are listed below.

·        General approach to be taken, with rationale

 

As you study existing interfaces or interview prospective users, ensure that your observations / results are maintained in a form that they could be included as an appendix later.

This paper is not expected to be particularly long. Your emphasis should be on creating a good foundation for your future work.

Some questions related to user and task analysis (these do not necessarily have to be answered in Q/A format):

  1. Who is going to use system?
  2. What tasks do they now perform?
  3. What tasks are desired?
  4. How are the tasks learned?
  5. Where are the tasks performed?
  6. What’s the relationship between user & data?
  7. What other tools does the user have?
  8. How do users communicate with each other?
  9. How often are the tasks performed?
  10. What are the time constraints on the tasks?
  11. What happens when things go wrong?

Turn in four (4) copies (one for me to keep, one for each of two future design reviewers, one to be returned to you)(or one copy plus a softcopy – softcopy including post-able html/pdf would be ideal).