Processes%20of%20Design%20Fifth%20lecture:%20Evaluation%2024%20October%202003 - PowerPoint PPT Presentation

About This Presentation
Title:

Processes%20of%20Design%20Fifth%20lecture:%20Evaluation%2024%20October%202003

Description:

... you could do is, presumably you could just whisk your card through, rather than ... And I don't see why they don't do that always, anyway. ... – PowerPoint PPT presentation

Number of Views:22
Avg rating:3.0/5.0
Slides: 14
Provided by: Will304
Category:

less

Transcript and Presenter's Notes

Title: Processes%20of%20Design%20Fifth%20lecture:%20Evaluation%2024%20October%202003


1
Processes of DesignFifth lectureEvaluation 24
October 2003
  • William Newman

2
EvaluationWhat do we Mean?
  • In the dictionaryDetermining or estimating the
    value of
  • In interactive system design
  • Identifying faults
  • Testing perfor-mance
  • Rating quality,egfrom 1 to 10

3
Evaluation in the Inner Loop
  • Assessing design options
  • The ATM design session
  • D. Well, one of the things you could do is,
    presumably you could just whisk your card
    through, rather than have to put it in the slot
    and get it back, and that might be quicker than
    waiting for it to come out. And I dont see why
    they dont do that always, anyway. I suppose
    its so they can chew it up if they want to.
  • J. Yes.
  • Evaluating by simulating.

4
Alternatives to simulation
  • Evaluating with theory-based lawse.g. Fitts
    LawTpos K log2(A / W 1)
  • Evaluating with an informal rule or heuristic
  • The quest for accuracy and completeness.

5
Two ways to evaluate
  • Empirical conduct an experiment
  • Analytical evaluate on paper
  • Why two ways?
  • Cost of simulation.

6
What do we simulate?
  • The technology
  • The user
  • The context
  • The task
  • Why are these familiar to us?

7
Evaluating in terms of requirements
  • The problem statement
  • Design a camera-based text-capture system to
    enable students in libraries to copy text from
    paper to word processor in less time than by
    typing.
  • A concise statement of requirements
  • As we expand requirements, we refine our
    evaluations

8
Simulating the technology
  • How to avoid building the complete and final
    system?
  • Working and non-working simulations
  • Whats missing from non-working sims?
  • Wizard of Oz methods.

9
Xerox Star
  • Designed in the late 1970s
  • Technology performance problems
  • Escalating costs
  • Never fully evaluated

10
Simulating the User
  • Youre not them!
  • Knowing the user
  • Xerox Star again

11
Simulating the Context
  • Taking account of
  • Other systems (Airport control, Aegis)
  • Other people (GPs)
  • Physical environment

12
Simulating the Task
  • Sets up the process of evaluation
  • Easy? We design the task
  • Not so easy? The user can redesign it(the
    computer game)
  • and may never learn it.

13
The Limits of Evaluation
Write a Comment
User Comments (0)
About PowerShow.com