Syllabus for IST 331: The User

(Full title: Organization and Design of Information Systems: User and System Principles)

Fall 2008 [recent press release on ist331]

Section 1: Tu 1:00PM - 2:15PM, 208 B.IST
Th 1:00PM - 2:15PM, 208 B.IST

3 credits

Frank Ritter
316G BIST
University Park
865-4453
College of IST
ritter@ist.psu.edu

Office hours:     Tu/Th 1415-1445, and by appointment

Teaching Associate: Dr. Olivier Georgeon
(olg1@psu.edu, phone 865-6166, 316E BIST)

Office hours: W 1300-1500, Fri 1500-1600 and by appointment

updated 8 Oct 08

TABLE OF CONTENTS

1. Course Overview
2. Course Objectives
3. Course Organization
4. Evaluation
5. IST 331 Class Schedule/Syllabus
6. Labs
7. Course Conduct
8.
Relevant University Policies

Feedback form

Please note, this is a live document. Changes announced in class and on the list server will be incorporated from time to time. Announcements in class and their mirror here are the definitive version.

1. COURSE OVERVIEW

This course provides students with theories, models, and analytic techniques regarding how users interact with information, and with Information and Communication Technologies (ICT). Basic concepts of use, tied to how humans process information, are developed through projects, cases studies, examples, and discussion. The course also covers aspects of how small groups process and share information, use ICT, and interact. The course serves as a focused introduction to the concept that people are important in technology systems and has become either a co-requisite or prerequisite to all other 300 and 400 level IST courses. It is now a required course for incoming IST students.

We will explore these topics through in-class presentations, discussions, readings (from both text and on-line sources), exercises (done in groups assigned the first week), and exams.  

2. COURSE OBJECTIVES

To provide an introduction to the idea that people are a core component in technical systems, and to provide real, descriptive information about those aspects of human behavior that influence the development, use, and accidents that will arise in such systems due to having people as part of the system. This course provides a balance between theory and practice, which are tightly intertwined in this area. Basic and more advanced readings will introduce the student to current thinking about facts, theories, and ways to gather new data. A small group project, drawing on the different backgrounds students bring to the program, will support integrating these various types of knowledge and applying them to an illustrative interface or system. The teaching philosophy includes working in groups and presentations.

Students in IST will benefit by being able to differentiate themselves from the traditional view in computer science of only focusing on computers, and MIS's rather "user-less" orientation. The IST degree is "not the technology itself, not the million bit per second router ... , but rather the effect that that will have on society, on ... individual[s], and on groups making decisions in an organization."

At the conclusion of this course, students will be able to:

  • Define in a quantitative and qualitative way some of the most relavent aspects of user's behavior.
  • Be familiar with theories, problems, and terms in the area of human-computer interaction.
  • Be able to gather data in several ways to explore how people individually and as a group use an interface.
  • Be able to prepare a report assessing a web site or other system providing concrete, objective support for good and bad aspects of the system.

3. COURSE ORGANIZATION

3.1 The IST 331 Web Site. This course has an active web page that contains the syllabus, assignments, links to useful sites, and other valuable material (such as how to correctly prepare assignments, citation templates, and other academic and recreational information). This page can currently be found at acs.ist.psu.edu/ist331, and later will be available through links from the IST home page via course listings.

3.2 The IST 331 Listserv. This course has a mandatory listserv that we use to post course and class information, conduct on-line discussions, and share information. You are encouraged to use your PSU account, and not a hotmail or yahoo account that cannot receive attachments. You should be added automatically to the list, but you can also remove yourself or update your address. If you are not subscribed, you can join by sending mail to L-IST331-1-FA08-subscribe-request@lists.psu.edu . Once you have subscribed, you can then send mail to the class at L-IST331-1-FA08@lists.psu.edu. More details at http://lists.psu.edu

If you send mail to me or the TA, please include "Ist331" in the subject, as this will help a filter bring it to our attention.

3.3 Required Texts

(ABCS) The ABCS of HCI. Ritter, F. E, & Churchill, E. 2008. Available from Kinko's (on the corner-ish of Atherton and College, ph. 238-2679) at cost, for about $30, approximately 270 pages.

Papers and online references are available as supplements.
  List of errata for all readings

Research Style & Usage: APA/MLA (SparkCharts) Available at bookstore and direct.

3.4 Required readings (handed out in class or available online)

The readings are linked below by class period. Some of these are password protected. The password will be sent out to the mailing list (save that email), announced in class, and available from Ritter or the TA.

 

3.5 Optional Texts and Interesting Resources

4. EVALUATION

You earn your grade but it will be assigned by me. The criteria for each assignment will be discussed in detail, as will the grading scheme. Each written assignment will be evaluated on how well it addresses the questions posed, the clarity of thinking, the organization and presentation of the material, the quality of writing, and its timeliness. 

Your grade will be based on 100 possible points. You earn points with each assignment (see below). As a maximum scale (i.e., cutoffs may be lowered): A: [100-94], A-: (93-90], B+ (89-87], B: (86-84], B-: (83-80], C+: (79-77], C: (76-70], D: (69-60], F: (59-0].  (The cutoffs for each grade is the lower number, without rounding.)

Your learning will be assessed in several ways. Please consult the schedule to see when papers / assignments are due and exams scheduled. You will receive more written instructions for each assignment well in advance of the due date. Here is a brief summary of each:
   

Assignment

Weight

Due Date

Labs

Tips on doing them

Notes on writing and doing labs

Marking scheme

Tool to help set up team meetings

25% 

You will do a variety of labs. Each lab writeup is nominally 10 points, 66 points total including an extra 5 extra credit points and the initial 1 point project writeup. 60 points will be taken to be the maximum lab grade (i.e., you can miss 6 points and get a perfect score). This score may be modified/moderated/adjusted by self and team evaluations.

Two copies required, one for TA/Teacher, one for peer comments.

Each lab/project needs this form included or a contract on file. [notes on generating a contract]

Typically Thursdays, as below

Resource talk

(up to 5 points added to lab grade)

Your group may find an additional resource that addresses or relies upon topics covered that week in class. In one page or less, you will comment on how that resource relates to the class.

You may be offered an opportunity for participating in a study for extra credit; details will be announced after the study is approved.

Once, varies by group

Mid-Term Exam

25% 

In class, taken individually

October 2008

Project

Comments on writing

Example template:

RTF

30%

Final web site analysis, including a table of suggestions

Example G2 from 2003

Example G1 from 2003

Example G4 from 2003

Example G9 from 2003

Example Group Micks from 2006

Example G6 from 2006

Examples from Fall 2007

Dec 2008

Second Exam

20% 

This will be an exam on social effects, taken individually. In class.

Dec 2008

Total 100%    
Extra credit 3% (pro-rated) Students can participate in a 5-7 session study. You must start by 10 November by emailing Dr. Jong Kim before 5 November to get a slot

A grade calculator is available. It assumes that you know Excel fairly well, and is subject to all known limitations of spreadsheets.

 

5. IST 331 CLASS SCHEDULE (subject to revision)

IST 331 Fall 2008 Calender

Date

In Class

Read/Prepare for this class

Due

Part I: Why

1

26/Aug/08

Kegworth video
More on Kegworth
BBC on Kegworth

First class, too early!

2

28/Aug/08

In class pub game

ABCS-preface

Part II: Human information behavior

3

2/Sep/08

Overview of the areas

Project step I - choice
1 point

ABCS 1, 2

4

4/Sep/08

Intro to information behaviour

Start IS lab in class
10 points

Example report (NB needs references)

Example report 2

Spink & Cole, 2001

Barnes et al. 1996

5

9/Sep/08

Further information behaviour

How to use
Word: Outline mode
XL: graphs

Optional: APA Manual

ABCS-Apdx3

6

11/Sep/08

End of information behaviour

Byrne et al, 1999

Project Step I due

Part III: Individual behavior

7

16/Sep/08

Overview of Individuals

ABCS 3

OPT:
Change blindness

More on change blindness and vision

8

18/Sep/08

Learning Lab
10 points

log-log graph paper
background paper
example report (NB still missing refs)
Ethics in running participants
Comments on writing up labs

ABCS 6.4

Learning paper

Online stopwatch

IS Lab due

9

23/Sep/08

More on individuals

OPT:
Guidelines - FSF

Eye-tracking video

10 

25/Sep/08

Problem Solving Lab

ABCS 6

11

30/Sep/08

More on individuals

ABCS 4, 5

OPT:
Colour wheel
(local copy)

Memory and hypertext

12

2/Oct/08

Working on labs

  

13

7/Oct/08

Decision making by individuals

ABCS 7, 8

Dawes Ch 3

Learning Lab due

14 

9/Oct/08

Perceptual Interaction Lab
10 points

This or similar approach

example old style report

Popout applet

Fovea applet

Colorblindness 1

Colorblindness 2

ColorJack

15

14/Oct/08

Review for exam

ABCS 11

Problem solving lab due

16

16/Oct/08

** In Class Midterm Examination **

Example midterm
Example midterm II
Example midterm III
Example midterm IV

 

Group feedback due

17

21/Oct/08

Task analysis - Intro

ABCS 12

KLM paper

GOMS papers

Local GOMS Guide

Example full analysis

18 

23/Oct/08

Task analysis II

OPT:
KLM notes

19

28/oct/08

Project II - draft plan
5 points

ABCS Appendix2

Perceptual Interaction Lab due

30/oct/08

Task analysis
10 points

Example report

20

Part IV: Group behavior

   

21 

4/nov/08

Groups - Overview

Theories, networks

ABCS 9, Appendix 2

McNeese on Jasper

Agre on networking

22 

6/nov/08

Group study
10 points

Project plan due

23

11/nov/08

Groups - details

Basics of relevant group behavior (e.g., social facilitation/loafing, group polarization, affiliation, social dilemmas in group ownership, and cooperation/competition - related issues such as helping behavior, prejudice, and attraction)

Task analysis due

24

13/nov/08

Group Lab discussions, readings

Activity Theory [Lect] [example paper]

Axelrod

25

18/nov/08

Group-level information problem solving

Group Lab due

 26

20/nov/08

Project - work/review

 

27 nov 08

Thanksgiving week

27

2/Dec/08

Project - Presentations

28 4/Dec/08

Interface evaluation post-hoc

ABCS 14, 16

29

9/Dec/08 Review session for exam    
  10/Dec/08 Office hours, 316g BIST, 5-7 pm    
30 11/Dec/08

In class exam on Social & task analysis

Example Social and TA exam

Example 2 Social and TA Exam

Example 3 Social and TA Exam

   
 

 

Project reports due

17 dec 2008 1700, email or paper

Allowed interfaces/web sites to analyse

Each semester each group does a useful project. They might as well have some impact. There should be the possibility that your report can have some impact, and most have had. Here are several examples of places that will have impact. My connection or interest is shown in ().

The Penn State Disability Resource Web Page (contact: "Erica Garner" <egarner@ist.psu.edu>)

The computer science Department at the University of Iowa (contact there)

Apple iPhone Application development Kit Build an application for the iPhone, using the iPhone emulator if you don't have an iPhone.

Disability Services at Penn State's web site.

The role of class reading lists at Downing Library at the U. of Cambridge (contact from Ritter)

The RSC and/or The New Globe (user)

earchives: e.g., http://www.informatik.uni-trier.de/~ley/db/ (user)

http://grey.colorado.edu/shortgut/index.php/Main_Page (colleague)

epsych.msstate.edu/overview/index.html, software for teaching psychology (user, know Bradshaw)
http://chronicle.com/free/2003/02/2003022801t.htm (also can look at Inquery, a similar tool at WU-STL)

www.gnu.org/directory, the GNU Free Software Foundation (user, supportor of FSF)

AISB and Cognitive Science web sites (member, member)

Emacs speaks statistics

 

A larger example of this type of work is available in the following report:

Ritter, F. E., Freed, A. R., & Haskett, O. L. (2002). Discovering user information needs: The case of university department websites (Tech. Report No. 2002-3). Applied Cognitive Science Lab, School of Information Sciences and Technology, Penn State. acs.ist.psu.edu/acs-lab/reports/ritterFH02.pdf. Ritter, F. E., Freed, A., & Haskett, O. (2005). User information needs: The case of university department web sites. ACM interactions. 12(5). 19-27.

 

FINAL EXAMINATION WILL NOT be held

 


6. Labs for IST 331

The laboratory portion of IST 331 provides students with the chance to become familiar with using the concepts and data about how people behave with respect to computers. It is absolutely essential for understanding the material and will be useful for passing the exams.

You have been put into small groups to do your labs because we believe this generally leads to better learning. Just one example, it leads to clearer writing and presumably clearer thinking [Murphy, 2000]. That means that you must turn in one lab report per group, that in this case conferring within your group is not a violation of academic policy or of ethics on the lab section of this course, and that conferring with other groups *is* a violation of academic policy and ethics if it results in reports that are noticeably similar without citation.

The best way is to work on the lab and then meet to discuss and proofread the report. The worst way is to have each member of the group do (and thus learn) one of the sections. This will result in a noticeably inferior product. We suggest that you trade who leads the preparation of each write-up.

As we explore these topics, we will also practice skills in working together, analytical skills, and information problem-solving approaches. 

7. COURSE CONDUCT

  • Classes will start on time and end as scheduled. Please take your seat prior to the start of class.
  • You should attend each class and actively participate in the discussions during class. University policy on class attendance is applied.
  • If you are uncomfortable with public speaking, or if English is not your native language, we must meet in the first two weeks of school to establish ways to make you more comfortable in speaking and interacting with your peers. I am happy to do this; I have been there myself (e.g., in Germany last year).
  • For every hour of lecture, I anticipate that you will need to budget about 3 hours of out-of-class time. This implies that you need to budget about 140 hours of out-of-class time over the course of the semester. This time estimate is a guide and you may need to budget more or less. For example, if the material is new to you or difficult to comprehend, it will require more of your time. 
  • You are responsible for all the readings, even if the material is not explicitly covered in class. You should read the class materials prior to class and be prepared to discuss and ask questions about the readings and assignments. You should also re-read the material after class as not every topic will be covered during class time. Many passages in the text may need to be read several times to gain clarity. Also, taking notes on the material you are reading and reflecting on the reading and these notes will help you better understand the issues, concepts and techniques that are being presented.
  • All work must be completed and turned in at the start of class on the assigned date. No late work will be accepted. Late means after the class has begun. Note that a computer's failure is not an excuse (it represents poor planning on your part). If you miss a deadline, a written explanation of a university recognized excuse and written request must be handed to me at the end of a lecture.
    Assignments that are simply late are very welcome to be turned in for feedback but 0 marks.
  • All assignment should be double-spaced (or 1.5 spaced where appropriate), on 8.5"x 11" or A4 paper. All pages should have 1" margins. Papers should be stapled and collated. Please do not use report covers; they will not be returned. Your group number and names should be on the cover, as well as an abstract (where appropriate).
  • Proofread your work. Mistakes include spelling, grammatical errors, and other typos. You should assume that your reader is about as smart as you, not smarter. You must also show your work, even if you just note 'by inspection'. The marker will want to know that you know how to get the answer.
  • I expect group work should be just that -- from all of the group. If I become aware that you are not contributing to your group equally, I will intervene. I expect individual work should be just that -- it should be done by you, alone. For more help, see this site and university policy.
  • Students who participate in University-sanctioned events (such as athletics) must make prior arrangements and give ample notice, but will be supported.
  • The official language of this course is English (e.g., you cannot turn the homework in here in translation for advanced language courses).
  • Requests for regrading must be turned in with this form.

8. Relevant University Policies