Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

Geek Culture / Shneiderman's Rules...programmers, this will interest you!

Author
Message
JD Programming
21
Years of Service
User Offline
Joined: 22nd Nov 2003
Location: United Kingdom
Posted: 27th Nov 2003 00:17 Edited at: 27th Nov 2003 00:25
Today in Computing we learnt about Shneiderman's "Eight Golden Rules of Dialog Design", and I must say that it was most interesting; and just thought I'd posted it

Shneiderman’s – “Eight Golden Rules of Dialog Design�

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 consolidates, window-motion frequency be reduced, and sufficient training time be allotted for codes, mnemonics, and sequences of actions.

Hope you guys will learn something from this

Also...happy programming

Programming is one of the first steps to become an individual...
http://www.jdpgamestudios.co.uk
CattleRustler
Retired Moderator
21
Years of Service
User Offline
Joined: 8th Aug 2003
Location: case modding at overclock.net
Posted: 27th Nov 2003 00:57
Good rules to follow.
I would also add the K.I.S.S. Rule...

keep it simple, stupid!

-RUST-
JD Programming
21
Years of Service
User Offline
Joined: 22nd Nov 2003
Location: United Kingdom
Posted: 27th Nov 2003 00:57
Lol, I like that rule

Programming is one of the first steps to become an individual...
http://www.jdpgamestudios.co.uk
JSN
21
Years of Service
User Offline
Joined: 8th Nov 2003
Location: 127.0.0.1
Posted: 27th Nov 2003 00:59
I actually think colour is a good use of dialog...

Red - Warning
Blue - Input
Green - Process
Yellow - Information.

~ J ~
Easily Confused
22
Years of Service
User Offline
Joined: 22nd Oct 2002
Location: U.K. Earth. (turn right at Venus)
Posted: 27th Nov 2003 01:02
...not if you are color blind

Programming anything is an art, and you can't rush art.
Unless your name is Bob Ross, then you can do it in thirty minutes.
JD Programming
21
Years of Service
User Offline
Joined: 22nd Nov 2003
Location: United Kingdom
Posted: 27th Nov 2003 01:12
...but it is if your not

Programming is one of the first steps to become an individual...
http://www.jdpgamestudios.co.uk
JD Programming
21
Years of Service
User Offline
Joined: 22nd Nov 2003
Location: United Kingdom
Posted: 30th Nov 2003 17:10
I must stress the importance of these rules...trust me, they do help!



Programming is one of the first steps to become an individual...
http://www.jdpgamestudios.co.uk
Megaton Cat
21
Years of Service
User Offline
Joined: 24th Aug 2003
Location: Toronto, Canada
Posted: 30th Nov 2003 17:38
lol JD, I just saw 8 of your threads lined up in a row on the general talk page...some one is on a roll..

Visit our new site! : http://www.megatoncreations.tk
If life throws you a grenade...pull the pin and throw it back!
JD Programming
21
Years of Service
User Offline
Joined: 22nd Nov 2003
Location: United Kingdom
Posted: 1st Dec 2003 11:47 Edited at: 1st Dec 2003 11:49
Lol! The reason for this is that because when I come online I decide to check and sometimes update my threads Like I am here!

Te he

Programming is one of the first steps to become an individual...
http://www.jdpgamestudios.co.uk

Login to post a reply

Server time is: 2024-11-28 00:03:31
Your offset time is: 2024-11-28 00:03:31