|
|
1.1 root 1: .\" @(#)p4 6.1 (Berkeley) 5/23/86
2: .\"
3: .NH
4: Experience with Students.
5: .PP
6: .I
7: Learn
8: .R
9: has been installed on
10: many different
11: .UX
12: systems.
13: Most of the usage is on the first two scripts, so these
14: are more thoroughly debugged and polished.
15: As a (random) sample of user experience,
16: the
17: .I learn
18: program has been used at Bell Labs at Indian Hill
19: for 10,500 lessons in a four month period.
20: About 3600 of these are in the files script,
21: 4100 in the editor,
22: and 1400 in advanced files.
23: The passing rate is about 80%,
24: that is, about 4 lessons are passed for every one
25: failed.
26: There have been 86 distinct users of the files script,
27: and 58 of the editor.
28: On our system at Murray Hill, there have been nearly 2000 lessons
29: over two weeks that include
30: Christmas and New Year.
31: Users have ranged in age from six up.
32: .PP
33: It is difficult to characterize typical sessions with the
34: scripts;
35: many instances exist of someone doing one or two lessons
36: and then logging out, as do instances of someone pausing
37: in a script for twenty minutes or more.
38: In the earlier version of
39: .I learn ,
40: the average session in the files course took 32 minutes and covered
41: 23 lessons.
42: The distribution is quite
43: broad and skewed, however; the longest session was
44: 130 minutes and there were five sessions shorter than
45: five minutes.
46: The average lesson took about 80 seconds.
47: These numbers are roughly typical for non-programmers;
48: a
49: .UX
50: expert can do the scripts at approximately 30 seconds
51: per lesson, most of which is the system printing.
52: .PP
53: At present working through a section of the middle of the files
54: script took about 1.4 seconds of processor time per lesson,
55: and a system expert typing quickly took 15 seconds of real time per lesson.
56: A novice would probably take at least a minute.
57: Thus a UNIX system could support ten students working simultaneously
58: with some spare capacity.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.