CS 92 Educational Software
Some notes for discussion on learning from interface re-design.
Samuel Spitzer
March 10,1998

Since we are all working on distinctly different projects, I thought that this would be a good place to gather a set of routines/questions might help you evaluate your interfaces without having to redesign (which you probably don't have time for). So if you have anything to add to this list please email me.

Here some usability guidelines from the actual article(*):

Menu headings should be visually distinct from menu items.

Information should be arranged to support intended usage of hypertext.

Readers should be able to tell which screen items are buttons.

Readers often return to the main contents screen for reorientation.




A few useful self critiques I often use.

1. Is the structure of your program clearly defined?

2. Is every pixel of the screen accounted for ?

3. Are all functional components obvious and communicate their functionality to the user in the most effective manner?

4. Are all other informational/communicative elements as clear as possible?

5. Does the overall environment of your program suit the needs and goals of your program, and how does it reflect its structure.

 
Lessons learned from redesigning Hypertext User Interfaces
from Cognitive Aspects of Electronic text Processing. pp.265-286.