Please enable JavaScript.

Coggle requires JavaScript to display documents.

Human Computer Interaction (10 Heuristics (Jakob Nielsen (error prevention…

- - - - The system should either remove frequent error conditions or check for them and ask the user if they want to continue eg a confirm box for entering a name with a number. Why? Because this is most likely an error as humans dont have names with numbers in them
    - - User should be capable of stopping the function at all times eg a skip or close prompt button. Why? Because users tend to have a short attention span and don't really care for reading all the information that has been prepared
    - - The user should be capable of understanding the error even without any experience Eg 404 Not found Why? Because if the user gets attacked with complex information they will not understand what to do
    - - When the user needs to do something there must be options available Eg a drop down box for possible options Why? So the user understands what is supposed to be filled into the possible option boxes
    - - Key binds that allow advanced users to do actions quickly
        eg Ctrl + S for save. Why? Because this allows the advanced user to get simple task get done much quicker.
    - - The system should not have multiple variations of symbols for the same action. And should not differentiate between other systems Eg the Cog to open up the systems settings Why?So the user never gets lost and when wanting to run a function will only have to look for one variation of the symbol instead of multiple and using guess and check methods
    - - There should be no extra text or information that is not relevant as it decreases the value of valuable information eg Googles home page. Why? Interfaces need to clear of things that do not support the goal & tasks
    - - The system needs to communicate appropriately with the user through recognizable symbols & language. Eg The Trash symbol for deleting stuff Why? This is so the user can understand basic functions of the system even if it is in another languge
    - - The help and documentation should not have waffle and should have precise, easy steps for the user to follow. eg. GoDaddy’s Help page. Why? This is so the user can use your system and if in trouble get information from the system itself to continue
    - - The user should be informed and know what going on within the system in reasonable time eg Loading bar Why? This is so the user does not get confused when the system doesn't is showing a blank page while loading. Otherwise the user may think the system is unresponsive and leave