Utah School of Utah School of ComputingComputing

Class Email List Design

CS5540 HCICS5540 HCIbyby

Rich RiesenfeldRich RiesenfeldFall 2007Fall 2007Le

ctur

e S

et 6

Lect

ure

Set

6

Student Name ServerUtah School of Computing slide slide 22Fall 2007

Issues

• Functional Needs- Current, reliable class mailing list

• Users- Students- Staff- Faculty

Student Name ServerUtah School of Computing slide slide 33Fall 2007

Student Basic Needs

1. Occasionally broadcast short messages to all classmates

2. Receive timely information re course

Student Name ServerUtah School of Computing slide slide 44Fall 2007

Staff Basic Needs

1. Occasionally broadcast short messages to entire class

2. Receive and monitor all mail sent to class

Student Name ServerUtah School of Computing slide slide 55Fall 2007

Faculty Basic Needs

1. Occasionally broadcast to entire class

2. Receive all mail sent to class

Student Name ServerUtah School of Computing slide slide 66Fall 2007

Administrative Basic Needs

1. Receive all mail sent to class

2. Create a repository of all class mail

3. Provide access

Student Name ServerUtah School of Computing slide slide 77Fall 2007

Desired Features of the Utility

• Students1. Ability to filter email

2. Convenient accessi. Venues: home, school, work

ii. Permissions: authorized access

• Staff1. Reliable mail list

2. Stable, always available

Student Name ServerUtah School of Computing slide slide 88Fall 2007

Aversive Characteristics For: - 1• Students

1. Want freedom of choice2. Don’t like being told where to get mail

• Staff1. Need 24 / 7 access2. Want to avoid clumsy, time consuming,

mail system (PeopleSoft) solution to simple utility

3. Don’t want a system of remailing, or bothersome and untidy shortcomings

Student Name ServerUtah School of Computing slide slide 99Fall 2007

Aversive Characteristics For: - 2

• Faculty1. (same as Staff 1-3)

4. Dealing w bounced mail from bad addr’si. annoying, time consuming, and distracting

• Admin1. Complicated system

2. Bothersome, inconvenient, inaccessible

1-3.

Student Name ServerUtah School of Computing slide slide 1010Fall 2007

Summary of Issues

Studs Staff Faculty Admin

Send Receive Monitor Archive Filter Login Choice Mobile Access

Student Name ServerUtah School of Computing slide slide 1111Fall 2007

Summary of Issues

Studs Staff Faculty Admin

Authorization Single List

Satisfactory to Others

No bounced email to clear

Student Name ServerUtah School of Computing slide slide 1212Fall 2007

Failures in Modeling the User - 1

• Student Model Flawed?- This is a bigger issue than Instructor

perceived??- Did not consider the issue of filtering mail

Do not account for this aspect when assuming that CS students can fwd mail

Student Name ServerUtah School of Computing slide slide 1313Fall 2007

Failures in Modeling the User - 1

• Instructor Model Flawed?- There was some rationale, although

possibly inaccurate- It was not an abritrary and capricious act

• He IS concerned with student happiness

Student Name ServerUtah School of Computing slide slide 1414Fall 2007

Failures in Modeling the User - 1

• Staff Model Flawed?- Students likely had not considered this

• Administrative Model Flawed- Students likely had not considered this

Utah School of Utah School of ComputingComputing

End Class Email List Design

End

Lec

ture

Set

6