Conduct a heuristic evaluation to critically evaluate the selected application
Activity Week 6: Heuristic evaluation
Name of the application (It needs to be related to programming):
Evaluator Name:
Aim:
The aim of this assignment is to conduct a heuristic evaluation to critically evaluate the selected application
The task:
Your task is to perform a heuristic evaluation to critically evaluate the selected application.
- Select a task on the team’s selected application:
- You need to identify 10 examples (any combination of followed or not followed)
- examples of where the usability principles have been followed and
- examples of where they have not been followed.
In each case, you should identify
the beneficial or detrimental consequences associated with adherence or non-adherence.
Assessment:
In marking your document, the following will be taken into account:
- For each usability principle tested:
- A clear description of the design principle should be provided.
- An example should be provided of a page that adheres to the usability principle. Critically discuss the beneficial consequences associated with the use of the design principle in relation to the application.
- An example should be provided of a page that does not adhere to the usability principle. Critically discuss the detrimental consequences associated with not using the design principle in relation to the application.
Your discussion of each usability principle should be no less than 100 words.
Inclusion of a screen shot for each example of adherence and nonadherence is recommended as a means of clarifying discussion.
- Suggested redesign of one page or web site that fails a principle (note thatthe web page or web site should be different to those described in 1 above.)
- For each principle:
- Justify why it fails the principle
- Describe how the page/site it may be changed
- Justify why the page/site would pass the principle after its modification
- System status visibility. The system should provide appropriate feedback.
1. Is status feedback provided continuously (eg progress indicators or messages)? |
2. Are warning messages displayed for long enough? |
3. Is there provision for some form of feedback? |
- Match between system and real world. Use language familiar to the user and follow conventions.
1. Are the words, phrases and concepts used familiar to the user? |
2. Does the task sequence parallel the user’s work processes? |
3. Is information presented in a simple, natural and logical order? |
4. Is the use of metaphors easily understandable by the user? |
5. Does the system cater for users with no prior experience of electronic devices? |
6. Does the system make the user’s work easier and quicker than without the system? |
7. Does the system fit in with the environment in which the user’s tasks are carried out? |
8. Can the system realistically reflect real world situations and appear to respond to the user? |
9. Are important controls represented on the screen and is there an obvious mapping
between them and the real controls? |
- User control and freedom. Provide emergency exits, undo, and redo.
1. Are facilities provided to “undo” (or “cancel”) and “redo” actions? |
2. Are there clearly marked exits (for when the user finds themselves somewhere unexpected)? |
3. Are facilities provided to return to the top level at any stage (eg links back to homepage)? |
- Consistency and standards. Things that appear the same should behave the same.
1. Is the use of terminology, controls, graphics and menus consistent throughout the system? |
2. Is there consistency between data entry and data display? |
3. Is the interface consistent with any platform standards? |
4. Have ambiguous phrases/actions been avoided? |
5. Have color and style conventions been followed for links (and no other text)? |
- Error prevention. Don’t just let users escape from errors: help users avoid them.
1. Is a selection method provided (eg from a list) as an alternative to direct entry of information? | ||
2. Is user confirmation required before carrying out a potentially ‘dangerous’ action (eg deleting something)? | ||
3. Does the system ensure work is not lost either by user or system error? | ||
4. Does the system prevent calls being accidentally made? | ||
5. Are the options given in dialog boxes obvious? | ||
6. Has the possibility of the user making errors been removed? | ||
- Recognition rather than recall. Options should be visible. Instructions should be easy to find. Don’t make the user have to remember information.
1. Are help and instructions visible or easily accessible when needed? |
2. Is the relationship between controls and their actions obvious? |
3. Is it possible to search for information (eg a phone number) rather than entering the information directly? |
4. Is the functionality of the buttons on the device obvious from their labels? |
5. Are input formats (eg dates or lengths of names) and units of values indicated? |
6. Is the functionality of novel device controls (eg gestures) obvious?
|
- Flexibility and efficiency of use. Support shortcuts for expert users.
1. Does the system allow for a range of user expertise? |
2. Does the system guide novice users sufficiently? |
3. Is it possible for expert users to use shortcuts and to tailor frequent actions? |
4. Is it possible to access and re-use a recent history of instructions (eg recently called numbers)? |
5. Does the system allow for a range of user goals and interaction styles? |
6. Does the system allow all functionality to be accessed either using function buttons or using the stylus? |
7. Is it possible to replace and restore default settings easily? |
8. Have unnecessary registrations been avoided? |
- Aesthetic and minimalist design. Avoid providing irrelevant information.
1. Is the design simple, intuitive, easy to learn and pleasing? |
2. Is the system free from irrelevant, unnecessary and distracting information? |
3. Are icons clear and buttons labelled and is the use of graphic controls obvious? |
4. Is the information displayed at any one time kept to a minimum? |
5. Is the number of applications provided appropriate (and has ‘featuritis’ been avoided)? |
6. Has the need to scroll been minimized and where necessary,
7. Are navigation facilities repeated at the bottom of the screen? |
8. Is the system easy to remember how to use? |
9. Have excessive scripts, applets, movies, graphics and images been avoided? |
- Help users recognize and recover from errors. Error messages should be helpful.
1. Do error messages describe problems sufficiently, assist in their diagnosis and suggest ways of recovery
in a constructive way? |
2. Are error messages written in a non-derisory tone and refrain from attributing blame to the user? |
3. Is it clear how the user can recover from errors? |
- Help and documentation. Ideally, the system should be usable without documentation, but help should still be available and task oriented.
1. Is help clear and direct and simply expressed in plain English, free from jargon and buzzwords? |
2. Is help provided in a series of steps that can be easily followed? |
3. Is it easy for the user to search, understand and apply help text? |
Navigation
1. Is navigational feedback provided (eg showing a user’s current and initial states,
2. where they’ve been and what options they have for where to go)? |
|
3. Are any navigational aids provided (eg find facilities)? | |
4. Does the system track where the user was in the last session (and any progress made)? | |
5. Has opening unecessary new browser windows been avoided?
|
Use of modes
|
|
|
Extraordinary users
1. Is the use of colour restricted appropriately (and suitable for colour-blind users)? |
2. Do the buttons allow for use by older, less agile fingers or people wearing gloves? |
3. Do buttons give tactile feedback when selected? |
4. Is the touch-screen usable by people of all heights and those in wheelchairs? |
5. Are equivalent alternatives provided for visual and auditory content? |
6. Have accessibility and internationalization guidelines been applied if appropriate? |