Lecture 3: User Centered Design. February 1

Transcription

1 Lecture 3: User Centered February 1 1

2 Recap Five Usability Attributes 2

3 Recap Five Usability Attributes Learnability Efficiency Memory Few errors Satisfaction 3

4 Wiki vs. Forum Users? Tasks? Usability comparison? 4

5 Homework: Evaluation 1 Due next Monday (Feb. 8) beginning of the class Evaluate the website you visit the most often, as you said in Homework 0 Focus on the five usability attributes (about 100 words each) Add a H1 section for this homework and an H2 section for each usability attribute Make sure the link on the People page is working 5

6 Project: Team Assignment Due next Monday (Feb. 8) beginning of the class Choose the project themes you are interested Add your name to the list Team assignment will be randomly determined unless you already have a team 6

7 Micro Homework 1 Due next Monday (Feb. 8) beginning of the class 10 Micro Homework Assignments 0.5% each Easy 7

8 Lecture 3: User Centered February 1 8

9 Three principles of UCD 1. Early focus on users and tasks 2. Iterative design with prototypes 3. Empirical measurement on prototypes 9

10 Why build an UI? Computerize a logistical process E.g., inventory control, restaurant Upgrade an outdated UI E.g., Terminal to Web1.0 to Web 2.0 Expect some people will use it E.g., dot.com, iphone app Apply a novel technology Software: sentiment analysis Hardware: gyroscope 10

11 1984 Summer Olympics 11

12 Needs Athletes want to receive support from families and friends who are far away Athletes want to talk to other athletes in other villages 12

13 Solution: Olympic Message System 13

14 Challenges 10,000 Olympic athletes Many family members and friends 50 different languages No cell phones Many with no experience with computers Some with no experience with push button phone 14

15 Things at stake Everyone is watching No delay No second chance Subject to sabotage and abuse 15

16 Hard to train Hard to run training classes since the campus is large Impossible to train non-olympian callers 16

17 process Ran scenarios with the Olympic committee Wrote user guides Lab live simulations Consulted with ex-olympian Tested on friends and families Tested on users oversea Hallway Prototype Crash test Pre-Olympic field test 17

18 Benefits of UCD they found Prevented well-intended but counterproductive changes from bosses Pruned wrong directions early Sped up the development process 18

19 Farm to Folk 19

20 Identified three user groups Organizers Members Producers 20

21 Identified problems Accounting is manual and prone to errors Information update is manual and tedious Direct communication between producers and members is not possible 21

22 Identify requirements Web-based Accept member a la carte orders Accept addition of new members Maintain member and producer information 22

23 a prototype 23

24 Let s build an iphone App TV Remote control 24

25 In a perfect world Develop Deliver $$$$$$$ Users 25

26 In reality Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Code, Debug, Users Deliver $ 26

27 first 27

28 Waterfall model Develop Users Deliver $$$ 28

29 Waterfall model Code Integration Users Release $$$ 29

30 Waterfall model Proposed in the 70s Linear process Get 100% done before advancing to the next stage Each stage has a concrete deliverable Put emphasis on documentation 30

31 What if people don t want it? Code Integration Users Release $$$ 31

32 Get users involved early 32

33 Winter Olympics 2010 People need to know when and where a particular event is taking place Spring 2010 CMSC 434 Introduction to Human Computer Interaction 33

34 UCD in Waterfall model Code Integration Release $$$ 34

35 Users are not always right the first time Code Integration Release $$$ 35

36 More iterations 36

37 Spiral model Start Release $$$ 37

38 Spiral model Start Release $$$ 38

39 Spiral model Start Release $$$ 39

40 iterations: Rochester Digital Library Iteration 1 Iteration 3 40

41 iterations: Rochester Digital Library Iteration 37 Iteration

42 iterations: Rochester Digital Library Iteration 126 Iteration

43 UCD in Spiral model??? Start Release $$$ 43

44 Early focus on users Start Release $$$ 44

45 Prototyping Start prototype prototype Release $$$ Final product 45

46 Keep users in the loop Start Release $$$ 46

47 Meeting user s expectation Not about adding features Support users goals People will not form unreasonable expectations Adequate and timely training Ownership 47

48 Participatory design Start Release $$$ 48

49 Three principles of UCD 1. Early focus on users and tasks 2. Iterative design with prototypes 3. Empirical measurement on prototypes 49

50 Term project Start Release $$$ 50

51 Proposal Start Release $$$ 51

52 User and task analysis Start Release $$$ 52

53 sketches Start Release $$$ 53

54 Paper prototype Start Release $$$ 54

55 Computer prototype Start Release $$$ 55

56 Final implementation Start Release $$$ 56

57 User testing Start Release $$$ 57

58 Final presentation Start Release $$$ 58

59 Activity: UMD Shuttle Part 1: Planning Bus Routes 1. Early focus on users and tasks 2. Iterative design with prototypes 3. Empirical measurement on prototypes 59

60 Activity: UMD Shuttle Part 2: When is the next bus coming? 1. Early focus on users and tasks 2. Iterative design with prototypes 3. Empirical measurement on prototypes 60