MCS Design rules
Shneiderman, Nielsen and Norman
Shneiderman, Nielsen and Norman
-
- 1 / 25
-
Lernkarten
Strive for consistency
Enable frequent users to use shortcuts
Offer informative feedback
Design diaglogs to yield closure
Offer error prevention and simple error handling
Permit easy reversal of actions
Support internal locus of control
Reduce short-term memory load
Use both, knowledge in the world and knowledge in the head
Simplify the structure of tasks
Make things visible: bridge the gulf of execution and evaluation
Get the mappings right
Exploit the power of contraints, natural and artificial
Design for error
When all fails, standardize
Visibility of system status
Match between system and real world
User control and freedom
Consistency and standards
Error prevention
Recognition rather than recall
Flexibility and efficiency of use
Aesthetic and minimalistic design
Help for users to recognize, diagnose and recover from errors
Help and documentation