![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() | |
| By N2H | ||||||||||||||||||||||
Principles of good interface design
June 24, 2008
If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting and have a nice day!
-
Natural
A good interface appears to be natural; it should be seen to be the appropriate way of performing a task. It should reflect the users’ task, syntax and semantics and might use the jargon of the user but not IT jargon.
-
Consistency
It should reinforce the user’s expectations from any previous interaction with that system or indeed with simulations
-
Relevance
The interface should not ask for redundant material. On- screen information should be short and relevant while still making sense. Key press should be reduced to a minimum.
-
Supportive
The system should provide adequate information to allow the user to operate and perform the task. Thus there should have:
a. Adequate help facilities
b. Adequate system feedback which should provide information to help the user continue with the task
-
Flexibility
The interface should accommodate differences in the user requirements, preferences and level of performance. Users should be able to create their own personalized settings, however, it should not be at the expense of consistency or the organizations’ needs.
Comments
Got something to say?
























