CSCI 588
CSCI 588 Fall 2002

General
   Course Description
   Course Syllabus

Fall 2001

   Contact Information
   Announcements
   Class Materials
   Class Project
   Grading Criteria
   Team Projects
   Bulletin Board
   Links

Previous Terms
   Fall 1998
   Fall 1999
   Fall 2000

Last modified on
11/29/2001

Computer Science 588
(NTU SE 735-SC)

Specification and Design of User Interface Software
Fall 2001

                       

Description of Class Project and Reading Assignments

Purpose:

The purpose of this class project is to provide the student with hands-on experience with the specification and design of user interface (UI) software. Assignments are handed in for feedback on progress. Reading assignments and lecture information is applied to the project.

  Schedule: 

Week 1:
8-28-01
  Class Project Kickoff
- Go over this handout

 

Week 2:
9-4-01 
  Form teams
- Form teams of 2-3 persons (prefer 3). Begin topic selection.
Read Shneiderman Chapters 1 & 3.  

 

Week 3:
9-11-01
  Topic Selection
- Example: automated drive-through at McDonald's discussed in class
- Student teams can select another topic. It must be a new system.
- Hand in names of team, topic description, and location
Read Shneiderman Chapters 9, then 6,7 & 8.

 

Week 4:
9-18-01 
  Generate top-level system requirements. Alsogenerate a one-page navigation map for your system. 
Read Shneiderman Chapters 10, 11, 12 & 16.

 

Week 5:
9-25-01 
  Use Shneiderman’s discussion on dialogue styles to select your project's interaction styles. Present in tabular form and explain why you chose your dialogue style(s) for your project's UI.
Also, perform a user characterization. Use "User Profile Checklist" to identify:
- user characteristics
- user tasks
- user workload
- user environmental considerations
Read Shneiderman Chapter 5.  

 

Week 6:
10-2-01
  Specification of the user interface. - Apply Hix and Hartson's User Action Notation techniques to a portion of your project's.
- Web page review homework. Critique a web page design using what you have learned.
Read Shneiderman Chapters 2, 4 & 13.

 

Week 7:
10-09-01 
  Midterm examination at campus location to be announced.

 

Week 8:
10-16-01 
  Prepare for Project Status Review.
Finish reading Shneiderman (Chapters 14, 15 & Afterward)

 

Week 9:
10-23-01 
  Class Project Status Review I
- Selected project teams will present portions of their results to the class. A specific outline of what is expected will be distributed. In summary, you will prepare an executable version of prototype user interface. This includes static screens with sequence of interactions that are expected. Hand in hardcopy of screens. State how the user proceeds from screen to screen, e.g. menu tree. Follow design guidelines discussed in class. 
Week 10: 10-30-01   Class Project Status Review II
- Selected project teams will present portions of their results to the class.

 

Week 11:
11-6-01
  Individual reading assignments due.

 

Week 12: 
11-13- 01
  Requirements verification and evaluation of project products. 
 

 

- Determine if your system met (or will meet) the requirements you developed on Week 4. Use Inspection, Analysis, Demonstration or Test
- Based on relevant evaluation criteria, select a method to evaluate your project and conduct that evaluation, i.e. perform a usability study of your project.
Week 13:   
11-20-01  
  Evaluate an existing system using the methods you just performed last week for your projects. Continue working on projects. Entire reading of class text should be completed.
Week 14:
11-27- 01
  Prepare for class project presentations next week. Review lecture material. 
Week 15:
12- 04- 01
  Class Project Presentations. Selected project teams will present portions of their results. (Thurs.12/6/01 is an optional project discussion day).
Week 16:
12-11-01 
    Final examination, 7-9pm, campus location to be announced.
    IMPORTANT: Please mark all homework and exams with "Campus" or your off-site location code on the front page, upper-right corner.


Send questions or comments to Steve.Jacobs@trw.com

The University of Southern California does not screen or control the content on this website and thus does not guarantee the accuracy, integrity, or quality of such content. All content on this website is provided by and is the sole responsibility of the person from which such content originated, and such content does not necessarily reflect the opinions of the University administration or the Board of Trustees