IEEM 552 - Human-Computer Systems

IEEM 552 - Human-Computer Systems Dr. Vincent Duffy - IEEM Week 13 - Working in Groups May 4, 1999 http://www-ieem.ust.hk/dfaculty/duffy/552 email: vduffy@ust.hk

tonight • recall Visual C++ demo • presentations 5 - 10 minutes • video • Electronic meeting room at GM • QOTD • questions related to ‘Working in Groups’ • after break • arrange subject testing schedule • let me know if there is a problem with your scheduled time

Last papers for reading/presentation • No papers presented in week 13 • Week 14 - delayed presentation by 1 week • Read paper by Chi, C.F. and Lin, F.T., 1998 • ‘A comparison of seven visual fatigue assessment techniques in three data acquisition VDT tasks’, Human Factors, Vol. 40, no.4, 577-590. 35

In the coming weeks • wk13 4 may - present Visual C++ modifications • read ‘usability testing’ & ‘working in groups’ on reserves, • lecture on ‘working in groups’ & video • schedule participation as subject (#2), W5,F7,S8,M10, T11 • wk14 11 may - Review • read final paper, project rept. due • discuss take home exam question 10 points • related to your participation as subject (#2) & ‘software evaluation’ • you will get to try some analyses related to that data • xxx no meeting wk 15,18 may - no presentations • wk16 25 may -final exam - rm2302 6:45-9:30 36

small software development project and ‘thinking aloud evaluation • As a group member you will participate in • software development • ‘thinking aloud’ evaluation, analysis • using minimum of 2 subjects (15 minutes) • software modification/improvement • presentation of before/after interface • 4-5 minutes …during week 13. • report …due during week 14 • 1 -2 page summary, 1 page figures screen captures 31

report format • 1-2 page written • describe in bullet format • process, what helped? • what did you need to be careful of? • what were the main improvements made • who were the subjects in your study • presentation • during class in week l3, Apr. 5 • report • during class in week 14, May. 12 • please include your slides from the presentation in an appendix

based on video and discussion tonight • see HBS case study - not required reading • (11 pages) • ‘The Center for Machine Intelligence: Computer Support for Cooperative Work’ (on images reserve) • p.499-513 from the book by Alan Dix called ‘Human-Computer Interaction’ (on images reserve) • QOTR need not be submitted

Group work - in electronic forum • group dynamics- roles and relationships within a group may change dramatically within the time of the task • physical layout - advantage of where to sit, etc. is leveled, particularly when the screen can be controlled from any terminal • experimental studies - can be of two types • discover how to gain acceptance of the technology • compare systems to find impact on effectiveness

Experimental studies of groups • more difficult than for individuals • differences in groups are more extreme than those of individuals • subjects? • for individual, 10 experiments means 10 subjects • for group, 10 experiments of group size 3 requires 30 • additional time needed to get familiar with others • more disruption, coordination, and expense • many reports of group work include only 3 or 4 groups • task - choosing a suitable task is difficult as well

analysis - if you test multiple conditions, your number of groups and subjects increases dramatically to have any chance of getting statistical significance • for example • if you want to measure the difference between two sets of groups in ‘microsoft net meeting’ • with 3 individuals in a group • to see performance in ‘chat only’ and ‘audio’ conditions • minimium of 5 teams in each condition • you would need 30 subjects (as noted earlier). • if you add any other conditions, you would add many subjects to the experiment

Organizational issues of group work • critical mass • need a certain number of users to gain the benefits of the system • for example think of the telephone. if your friends don’t have one, the benefit is limited. • conflicting goals • (CSCW) cooperative work? • people in organizations have conflicting goals • the electronic system must consider these realities

video • Center for Machine Intelligence - General Motors

while viewing: Consider for discussion • 1. What are the benefits of the system in this work environment? • 2. What problems were encountered? (what are the limitations?) • 3. How is this system used? • 4. Who are the stakeholders that are affected by the system? • 5. How did they judge if the system was effective?

1. What are the benefits of the system in this work environment? • sometimes encourage and sometimes discourage consensus • helped see areas of agreement and uncovered areas of strong disagreement, • find the holes in the process • 2. What problems were encountered? (what are the limitations?) • who should pay? • how to determine if benefit/cost justified? • 3. How is this system used? • determine if vehicle architecture meets objectives • include cross-functional views- techn. and h.r.m.

4. Who are the stakeholders that are affected by the system? • engineering, manufacturing, financial • each has own independent operations but common objective - satisfy customers • 5. How did they judge if the system was effective? • note the relationships between technology and culture • time to complete task improved

QOTD • 1. What would be the benefits of a system of this type in your work environment? • 2. What problems would be encountered? (what are the limitations? • 3. How would this system be used, or how should this system be modified if it were to be used in your workplace? • 4. Who are the stakeholders that would be affected? • 5. How would you know if the system were effective?

1. What would be the benefits of a system of this type in your work environment? • 2. What problems would be encountered? (what are the limitations? • 3. How would this system be used, or how should this system be modified if it were to be used in your workplace?

4. Who are the stakeholders that would be affected? • 5. How would you know if the system were effective?

IEEM 552 - Human-Computer Systems