Bureaucrats, emailconfirmed
1,221
edits
→Usability Goals
| Line 90: | Line 90: | ||
===Efficiency=== | ===Efficiency=== | ||
[[File:ComandLine.png|thumb| | [[File:ComandLine.png|thumb|150px|Great efficiency but hard to learn]] | ||
Your product has a good efficiency if the user can archive a high productivity. This simply means he/she can do more in less time once it is known how one uses the product. | Your product has a good efficiency if the user can archive a high productivity. This simply means he/she can do more in less time once it is known how one uses the product. | ||
Efficiency can be archived with optimizing the ways the functions are accessed and with providing additional ways of interaction like keyboard shortcuts. | Efficiency can be archived with optimizing the ways the functions are accessed and with providing additional ways of interaction like keyboard shortcuts. | ||
| Line 96: | Line 96: | ||
===Safety=== | ===Safety=== | ||
[[File:SicherheitNutzerdaten.png |thumb| "Close" and "Save" close to each other: not save!]] | [[File:SicherheitNutzerdaten.png |thumb|150px| "Close" and "Save" close to each other: not save!]] | ||
Safety is protecting the user and his/her creations from undesired outcomes. Very basic is that you provide a product that does not crash and destroys the users data by doing so. | Safety is protecting the user and his/her creations from undesired outcomes. Very basic is that you provide a product that does not crash and destroys the users data by doing so. | ||
[[File:UndoRedo.png|thumb|undo-redo-buttons]] | [[File:UndoRedo.png|thumb|150px|undo-redo-buttons]] | ||
You should as well prevent that the user selects data-destroying functions by accident. E.g. putting the "save" and the "close" entry close to each other in a menu will cause data loss: if the user wants to save, he may press "no" after a dialogue window appears: "don't bother me now. I want to save my data!" - and the data is lost, "close" was selected by accident and the dialog-window that was dismissed by choosing "no" was the final warning. | You should as well prevent that the user selects data-destroying functions by accident. E.g. putting the "save" and the "close" entry close to each other in a menu will cause data loss: if the user wants to save, he may press "no" after a dialogue window appears: "don't bother me now. I want to save my data!" - and the data is lost, "close" was selected by accident and the dialog-window that was dismissed by choosing "no" was the final warning. | ||