Xref: utzoo comp.software-eng:4195 comp.sw.components:508 comp.misc:10193 comp.groupware:298
Path: utzoo!attcan!uunet!aplcen!samsung!rex!ames!amdahl!pacbell!pbhyg!epfra
From: epfra@PacBell.COM (Ellen P. Francik)
Newsgroups: comp.software-eng,comp.sw.components,comp.misc,comp.groupware
Subject: Re: Prototyping and the Development Process
Keywords: prototyping, development, tools, literature, environments
Message-ID: <2257@pbhyg.PacBell.COM>
Date: 19 Sep 90 18:26:36 GMT
References: <3839@se-sd.SanDiego.NCR.COM> <6260@vanuata.cs.glasgow.ac.uk>
Reply-To: epfra@PacBell.COM (Ellen P. Francik)
Followup-To: comp.software-eng
Organization: Pacific * Bell, San Ramon, CA
Lines: 64

Here are some references on rapid iterative design, including
low-tech (paper & pencil) and high-tech (UIMS) prototyping.
I've found them to be practical guides in daily design, as
well as helpful in explaining the ideas to others.

Good, M., Spine, T.M., Whiteside, J., and George, P. (1986).
User-derived impact analysis as a tool for usability engineering.
In {Proceedings of CHI 86, Human Factors in Computing Systems}.
New York:  ACM, pp. 241 - 246.

Whiteside, J.A., Bennett, J.L., and Holtzblatt, K.A. (1988).
Usability engineering:  Our experience and evolution.  In
M. Helander (Ed.), {Handbook of Human-Computer Interaction.}
Amsterdam:  North-Holland, pp. 791 - 817.

	(The two above discuss how to set usability goals,
	 test for them, and iterate to meet them.)

Gould, J.D., Boies, S.J., Levy, S., Richards, J.T., and
Schoonard, J. (1987).  The 1984 Olympic Message System:
A test of behavioral principles of system design.
{Communications of the ACM} (September), pp. 758 - 769.

Gould, J.D., and Lewis, C. (1985).  Designing for usability:
Key principles and what designers think.  {Communications of
the ACM} (March), pp. 300 - 311.

	(These two are *highly* recommended.  The Olympic
	 Message System paper is a wonderful case study
 	 of rapid iteration and an integrated approach
	 to usability covering everything from on-line
	 help to training of overseas operators.)

Karat, C.-M. (1990).  Cost-benefit analysis of usability 
engineering techniques.  To appear in {Proceedings of the
Human Factors Society 34th Annual Meeting} (Orlando, FL:
October 8 - 12).

Mantei, M.M., and Teorey, T.J. (1988).  Cost/benefit analysis
for incorporating human factors in the software lifecycle.
{Communications of the ACM} (April), pp. 428 - 439.

Nielsen, J. (1989).  Usability engineering at a discount.  In
{Proceedings of the Third International Conference on Human-
Computer Interaction} (Boston, MA:  September 18 - 22), pp. 85 - 93.

	(These are good for The Big Picture.  Mantei & Teorey
	 expand on Boehm's software lifecycle to include
	 both formal prototyping and early, rough mockups.
	 Good summary of what kinds of usability activities
	 take place at different stages.  Read it side-by-
	 side with the Gould et al. Olympic Message System
	 paper.  Mantei & Teorey also show sample calculations
	 of the cost of various usability activities:  focus
	 groups, surveys, lab experiments, and so on.  Your
	 mileage may vary.  Nielsen argues that most people's
	 mileage *does* vary, and shows quick-and-dirty
	 techniques for getting useful information rapidly.
	 Finally, the Karat paper shows the impact of small
	 usability improvements on big systems:  big $$$$$.)

Ellen Francik
epfra@pacbell.com
Speaking from, but not for, Pacific Bell.