View this PageEdit this PageAttachments to this PageHistory of this PageHomeRecent ChangesSearch the SwikiHelp Guide
Hotspots: Admin Pages | Turn-in Site |
Current Links: Cases Final Project Summer 2007

Discussion 4 -- Joseph Earle

Exam Answers – Discussion 4

1. What are some things to consider when developing a UI for K-12?

Need to aim for lowest common denominator, thus aim at K/1 children.
They have lower vocabulary than adults so must be careful of any large/complex words/ideas.
They do not have the fine motor control of adults and should therefore be presnted with big buttons.
At the same time, if it's too stupid 12 won't want to use it.
Thus allow for a (blatanly visible) advanced mode with more complex controls/phraseology.

2. What are some things to consider when developing a UI for senior citizens?

bad eyesight: large text. arthritis: few subtle controls/ mouse moves/ quick key types.
unfamiliar with technology: carefully explain all concepts without using jargon (move the mouse to orient the cursor on screen vs. move the mouse over the button.)

3. What are ways to test your user interface? Both before the users are involved and after?

surveys, cognitive walkthrough, talk aloud session, wizard of oz testing (fake up your interface with paper so they can see it work before you make it), diary studies.

4. What is a cognitive walkthrough and when is it useful?

having an HCI expert take a series of planned questions and using them to evaluate a system.
it is useful at any time you have a user interface (prototypes/wizard of oz scenarios are ok) that needs testing.

5. What is wrong with the UI for the clock on page 187?

you only gave me three pages of test: it doesn't exist!
buttons are larger than they need to be: distract from the main interesting part.
no way to alter seconds.

6. What is a process that you could follow for developing a good user interface?

you need to follow a series of creating prototypes (mock ups) of your intended design and allowing actual users and experts to examine/use the system and provide feedback on how to improve it, and then improve the system into a new prototype for testing. you continually repeat this process until you are satisfied with the system.

Links to this Page