close
Welcome

Login is for licensed XVT users and provides
access to your records, licenses, downloads,
and to your interactive, online help desk.
Thank you! 

Login

Google Translations

Who is Using XVT?

Aviation/Aerospace
Boeing

Communications & Media
Acquire Media

Government
Department of Defense

Higher Education
UC Berkeley

Insurance
Allstate Insurance

Manufacturing
Caterpillar

Services
Cendant

Technology
ExxonMobil Upstream

Utilities
Fischer-Uhrig Engineering

The XVT Edge

Leverage Your Expertise
Developers only need to be experts on a single platform for development.
Short Learning Curve
With XVT, programmers only need to learn a single API.
Higher Productivity
Choose the development platform that's best for the task and maximize development throughput.
Focus on Business Logic
Now, programmers are able to focus on application features and not on platform porting issues and GUI Coding.
Agile Friendly
Development teams can focus on solving customer problems and rapidly delivering next feature sets.
Shneiderman's "Eight Golden Rules of Dialog Design" Print E-mail
User Rating: / 1
PoorBest 

Ben Shneiderman proposed this timeless collection of principles, which is derived heuristically from experience and applicable in most interactive systems after properly refined, extended and interpreted. With so much emphasis on the web, with its limited UI powers, it is good to recall the principles that (still) apply to the richer application UI world.

1 Strive for consistency.

Consistent sequences of actions should be required in similar situations; identical terminology should be used in prompts, menus, and help screens; and consistent commands should be employed throughout.

2 Enable frequent users to use shortcuts.

As the frequency of use increases, so do the user's desires to reduce the number of interactions and to increase the pace of interaction. Abbreviations, function keys, hidden commands, and macro facilities are very helpful to an expert user.

3 Offer informative feedback.

For every operator action, there should be some system feedback. For frequent and minor actions, the response can be modest, while for infrequent and major actions, the response should be more substantial.

4 Design dialog to yield closure.

Sequences of actions should be organized into groups with a beginning, middle, and end. The informative feedback at the completion of a group of actions gives the operators the satisfaction of accomplishment, a sense of relief, the signal to drop contingency plans and options from their minds, and an indication that the way is clear to prepare for the next group of actions.

5 Offer simple error handling.

As much as possible, design the system so the user cannot make a serious error. If an error is made, the system should be able to detect the error and offer simple, comprehensible mechanisms for handling the error.

6 Permit easy reversal of actions.

This feature relieves anxiety, since the user knows that errors can be undone; it thus encourages exploration of unfamiliar options. The units of reversibility may be a single action, a data entry, or a complete group of actions.

7 Support internal locus of control.

Experienced operators strongly desire the sense that they are in charge of the system and that the system responds to their actions. Design the system to make users the initiators of actions rather than the responders.

8 Reduce short-term memory load.

The limitation of human information processing in short-term memory requires that displays be kept simple, multiple page displays be consolidated, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.


Ben Shneiderman, Designing the User Interface - Strategies for Effitive Human-Computer Interaction, second edition, Reading, MA: Addison-Wesley Publishing Company, 1992

Discuss in the Forum

Last Updated ( Wednesday, 19 November 2008 )
 
< Prev
Phone: 919.854.1800 - Cary, NC, US
Copyright (c) 2008 Providence Software Solutions, Inc. All rights reserved.