Scribd
Upload
34 views3 pages

Interface Design Guidelines1

The document outlines 10 principles for general interaction design guidelines: 1) Be consistent in formatting, 2) Offer visual and auditory feedback to users, 3) Ask for confirmation of critical or irreversible actions, 4) Allow for easy reversal of actions through undo functions, 5) Minimize the amount of information users need to remember between actions, 6) Seek to reduce keystrokes, mouse travel, and user confusion, 7) Protect against user errors, 8) Classify activities by function and establish screen layout accordingly, 9) Provide context-sensitive help, and 10) Use simple verbs or phrases for command names.

Uploaded by

Maria Ana Amolo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
34 views3 pages

Interface Design Guidelines1

The document outlines 10 principles for general interaction design guidelines: 1) Be consistent in formatting, 2) Offer visual and auditory feedback to users, 3) Ask for confirmation of critical or irreversible actions, 4) Allow for easy reversal of actions through undo functions, 5) Minimize the amount of information users need to remember between actions, 6) Seek to reduce keystrokes, mouse travel, and user confusion, 7) Protect against user errors, 8) Classify activities by function and establish screen layout accordingly, 9) Provide context-sensitive help, and 10) Use simple verbs or phrases for command names.

Uploaded by

Maria Ana Amolo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as RTF, PDF, TXT or read online on Scribd
You are on page 1/ 3

C.

Interface Design Guidelines- General Interaction

1st Principle: Being consistent


- Use a consistent format for menu selection, command input, data display and the
myriad other functions that occur in a HCI.

-Users should not have to wonder whether different words, situations, or actions mean
the same thing. Standards and conventions in product design should be followed.One important
aspect involves the consistent display of information. This requires that the system dependably
use standard formats, fonts, line spacing, letter spacing and page lengths when displaying
relevant information. The same information should appear in fixed places across all screens

2nd Principle: Offering significant feedback.

-Provide the user with visual and auditory feedback to ensure that two way
communication (between user and interface) is established.

-Users should be informed of the system status that results from their actions.
-Presenting status information to users facilitates their next actions and should
improve operating efficiency.It presents the user with the information needed to
understand where they are in the system and to how perform further actions.

3rd Principle: Asking for authentication of any non-trivial critical action.


If a user requests the deletion of a file, indicates that substantial information is to
be overwritten, or asks for the termination of a program, an "Are you sure ... message
should appear.

4th Principle: Authorizing easy reversal of most actions.

UNDO or REVERSE functions have saved tens of thousands of end users from
millions of hours of frustration. Reversal should be available in every interactive
application.

5th Principle: Reducing the amount of information to be remembered in


between actions
The user should not be expected to remember a list of numbers or names so that
he or she can re-use them in a subsequent function. Memory load should be minimized.
6th Principle: Seeking competence in dialogue, motion and thought.

Keystrokes should be minimized, the distance a mouse must travel between picks
should be considered in designing screen layout, the user should rarely encounter a
situation where he or she asks, "Now what does this mean "

7th Principle: Excusing mistakes.

The system should protect itself from errors that might cause it to fail.

8th Principle: Classifying activities by function and establishing screen


geography accordingly.
One of the key benefits of the pull down menu is the ability to organize
commands by type. In essence, the designer should strive for "cohesive" placement of
commands and actions.

9th Principle: Delivering context sensitive help services.

is a kind of online help that is obtained from a specific point in the state of the
software, providing help for the situation that is associated with that state.

10th Principle: Using simple action verbs or short verb phrases to name
commands.

A lengthy command name is more difficult to recognize and recall. It may also
take up unnecessary space in menu lists.

You might also like