Online Shopping, Prototyping, and Exam 1 Review

1
Online Shopping, Prototyping, and Exam 1 Review

• MIS 441 Information Systems Design and
  Implementation
• Class 12 - February 22, 2000

2
Outline

• Milestone 3 questions?
• Assignment 1 Online Shopping
• Prototyping
• Changes to the Schedule
• Access workshop next week, 2/29 and 3/2
• Meet in MH 214
• Exam 1 - Next class

3
Milestone 3 Test the low-fi prototype

• Identify and recruit three (3) evaluators
• Create three (3) scenarios of various difficulty
  levels
• Prepare and conduct a user test (or evaluation)
• Discuss the results
• Both positive and negative comments
• See example of results from Clothes Shopper
• Discuss likely or potential changes to the design
  for the next low-fi iteration

4
Evaluating results

• Sort prioritize observations
• What was important?
• Lots of problems in the same area?
• Create a written report on findings
• Gives agenda for meeting on design changes
• Make changes iterate
• Remember the Clothes-Shopper example

5
Stuff to include in Milestone 3 appendix

• Signed consent forms from the three (3) testers
• Roles of design team members
• Who was the greeter? facilitator? computer?
  observers?
• Briefly explain why?
• Orientation script
• Brief written explanation of the purpose of the
  test which is read to the tester before the
  evaluation takes place
• Background of project, reason for low-fi, purpose
  of test, expected time it will take, rules of the
  game, etc.
• Scenarios handed to the tester to complete
• Post-test questionnaire if one is administered

6
Summary

• Testing of the prototypes should be performed
  immediately after the exam (or sooner)
• Writing up the results and recommendations should
  take a few days
• Read Milestone 4 as preparation for Milestone 3
• Milestone 3 is due on Tue, March 7

7
Online Shopping Assignment

• Product
• Budget
• 3 sites
• Compare and contrast
• Policies, usability, content
• What did you like? Dislike? Why?
• Would you purchase an item from this site?

8
Review of Prototyping

• High Fidelity
• prototype looks like the final product
• computer-based prototypes
• provides version of the system with limited
  functionality so that users can interact with it
• more polished and aesthetically pleasing
• Low Fidelity
• artists rendition with many details missing
• paper-based prototypes
• quick and inexpensive, provide valuable insights,
  does not really demonstrate functionality

9
Forms of Prototyping

• Rapid Prototyping
• also used to collect information on requirements
  and on adequacy of possible designs
• prototype is thrown away and not developed into
  the final product
• Incremental Prototyping
• allows a large system to be installed in phases
• enables installation of a skeleton system
• Evolutionary Prototyping
• most extensive form of prototyping
• the intial prototype is constructed, evaluated,
  and evolved continually until it becomes the
  final system

10
Prototyping Less Than the Full UI
Horizontal Prototype
Different Features
Scenario Prototype
Functionality
Vertical Prototype
Full System
11
More Terminology

• Chauffered Prototypes
• involves user watching while another person
  drives the system
• Wizard of Oz
• man behind the curtain
• use of 3rd party, but the user is unaware of it
• user interacts with screens
• a developer at another screen answers the queries
  and responds to the user

12
Advantages of Lo-Fi Prototypes

• Take only a few hours
• Very cheap no expensive equipment is needed
• Can test multiple alternatives
• fast iterations
• Provides a shared understanding of goals for both
  designers and users

13
Advantages of Hi-Fi Prototypes

• Must test and observe ideas with users
• Paper mock-ups dont go far enough
• Perceptions
• Time

14
Prototyping Tools

• Hypermedia Systems
• computer apps that structure information in a
  navigable form
• e.g., HTML, Hypercard for Mac
• common, relatively low cost, easy to learn, use,
  maintain, and reach a high level of software
  quality
• Director
• most commonly used by designers
• intended for sophisticated multi-media
  designers
• advanced animation, graphic design, etc.

15
Prototying Tools

• Visual Basic
• designer created standard interface elements
• sets and modifies properties
• SILK
• http//guir.cs.berkeley.edu/projects/silk/
• Access, Powerbuilder, Excel, etc.
• allows easy connections to code via callbacks

16
Exam Review
17
Material covered on the exam

• Everything!!!!!
• What is the order of importance??
• What I say
• What the class slides say
• What the reading packet says
• But, everything is important and everything is
  fair game

18
Format and length of the exam

• Format
• Essays
• Short answer questions
• M/C, Fill-In, Matching - few
• Length
• Honestly, I dont know
• Some students have considered my exams long in
  the past
• Maybe 7 - 12 questions ???

19
My expectations

• Show me that you
• Are thinking
• Understand the concepts in the class
• Can use these concepts to address the questions
• Can pull together various things from the class
• Have learned something
• DO NOT assume I know what you are thinking when
  you answer the question
• Always provide solid support for your answers

20
Some test taking hints

• DO NOT leave questions blank
• I am usually pretty generous with partial credit
• Manage your time!!!!
• Make sure to get through all of the questions
• Some students like to answer the first questions
  very thoroughly, often including irrelevant and
  unnecessary info.
• Student doesnt have time to finish the exam
• There may not be a right or wrong answer
• Convince me that you understand the issues
• Read the instructions