Bureaucrats, emailconfirmed
1,221
edits
Line 376: | Line 376: | ||
# '''Consistency and standards:''' is further explained under [[IFD:Course_Interaction_Design#Standards_and_Consistency| Standards and Consistency]] | # '''Consistency and standards:''' is further explained under [[IFD:Course_Interaction_Design#Standards_and_Consistency| Standards and Consistency]] | ||
# '''Error prevention:''' Design should prevent errors. Some examples are [[IFD:Course_Interaction_Design#Safety| here]] | # '''Error prevention:''' Design should prevent errors. Some examples are [[IFD:Course_Interaction_Design#Safety| here]] | ||
# Recognition rather than recall | # '''Recognition rather than recall:'' Users should not to have remember things they from other parts of the program [[IFD:Course_Interaction_Design#Visibility|Visibility]] and [[IFD:Course_Interaction_Design#Modeless_Design | Modeless design]] are ways to support this via design. | ||
# Flexibility and efficiency of use | # '''Flexibility and efficiency of use:''' The system should not be only easy to learn but to be efficient to use for advanced and professional users. Keyboard shortcuts are a good example for such an mechanism. More on Efficiency [[IFD:Course_Interaction_Design#Efficiency| here]] | ||
# Aesthetic and minimalist design | # '''Aesthetic and minimalist design:''' Let form follow function and dont add visual clutter by over-advanced visual design. | ||
# Help users recognize, diagnose, and recover from errors | # '''Help users recognize, diagnose, and recover from errors:''' In case an Error cant be prevented or handled by the application itself, the error message should state problem and possible solutions in plain, non-technical terms. | ||
# Help and documentation | # '''Help and documentation:''' It is good if no help is needed to learn the program but some questions will appear, so provide searchable, easy to access information how to use the product | ||
==Introduction to prototypes== | ==Introduction to prototypes== |