Bureaucrats, emailconfirmed
1,221
edits
→User Interface Principles
| Line 373: | Line 373: | ||
# '''Visibility of system status''' is further explained [[IFD:Course_Interaction_Design#Feedback| here]] | # '''Visibility of system status''' is further explained [[IFD:Course_Interaction_Design#Feedback| here]] | ||
# '''Match between system and the real world:''' the user should not have to learn a lot to use the system. The system should be designed in a way that allows to draw form real world experiences and not to contradict those. | # '''Match between system and the real world:''' the user should not have to learn a lot to use the system. The system should be designed in a way that allows to draw form real world experiences and not to contradict those. | ||
# User control and freedom | # '''User control and freedom:''' Sometimes the user will find the interface or the things in an undesired stage. It needs to be possible to "escape" from unwanted stages the program is in (see as well: [[IFD:Course_Interaction_Design#Modeless_Design | modes]]) and Undo/Redo should be provided as well. | ||
# Consistency and standards | # Consistency and standards is further explained under [[/IFD:Course_Interaction_Design#Standards_and_Consistency| Standards and Consistency]] | ||
# Error prevention | # '''Error prevention:''' Design should prevent errors. Some examples are [[IFD:Course_Interaction_Design#Safety| here]] | ||
# Recognition rather than recall | # Recognition rather than recall | ||
# Flexibility and efficiency of use | # Flexibility and efficiency of use | ||