Download Heuristic Review Assignment for week and more Lecture notes Computer Science in PDF only on Docsity!
Heutistic Review Template (Source: http://www.uxforthemasses.com/)
[Enter product name] Score
Features & functionality
1 Features and functionality meet common user goals and objectives.
Good
2 Features and functionality support users desired workflows.
Good
Moderate
Poor
Good
Homepage / starting page
Poor
Hover over a guideline for more information, examples of good practice and importance to the
overall user experience.
N/A = not applicable
or can't be assessed
Frequently-used tasks are readily available (e.g. easily accessible from the
homepage) and well supported (e.g. short cuts are available).
Users are adequately supported according to their level of expertise (e.g.
short cuts for expert users, help and instructions for novice users).
Call to actions (e.g. register, add to basket, submit) are clear, well labelled
and appear clickable.
The Homepage / starting page provides a clear snapshot and overview of
the content, features and functionality available.
Good
Good
Navigation
Good
Good
Moderate
Good
13 Links are clear, descriptive and and well labelled.
Moderate
Good
Poor
The home page / starting page is effective in orienting and directing users
to their desired information and tasks.
The homepage / starting page layout is clear and uncluttered with
sufficient 'white space'.
Users can easily access the site or application (e.g. the URL is predictable
and is returned by search engines).
The navigational scheme (e.g. menu) is easy to find, intuitive and
consistent.
The navigation has sufficient flexibility to allow users to navigate by their
desired means (e.g. searching, browse by type, browse by name, most
recent etc…).
The site or application structure is clear, easily understood and addresses
common user goals.
Browser standard functions (e.g. 'back', 'forward', 'bookmark') are
supported.
The current location is clearly indicated (e.g. breadcrumb, highlighted
menu item).
Moderate
Forms
Good
Good
27 Required and optional form fields are clearly indicated.
Excellent
Good
Very poor
Errors
Good
Good
Users can easily give feedback (e.g. via email or an online feedback /
contact us form).
Complex forms and processes are broken up into readily understood steps
and sections. Where a process is used a progress indicator is present with
clear numbers or named stages.
A minimal amount of information is requested and where required
justification is given for asking for information (e.g. date of birth, telephone
number).
Appropriate input fields (e.g. calendar for date selection, drop down for
selection) are used and required formats are indicated.
Help and instructions (e.g. examples, information required) are provided
where necessary.
Errors are clear, easily identifiable and appear in appropriate location (e.g.
adjacent to data entry field, adjacent to form, etc.).
Error messages are concise, written in easy to understand language and
describe what's occurred and what action is necessary.
Poor
33 Users are able to easily recover (i.e. not have to start again) from errors.
Good
Content & text
Good
Moderate
Very poor
Poor
Good
Help
Good
Common user errors (e.g. missing fields, invalid formats, invalid selections)
have been taken into consideration and where possible prevented.
Content available (e.g. text, images, video) is appropriate and sufficiently
relevant, and detailed to meet user goals.
Links to other useful and relevant content (e.g. related pages or external
websites) are available and shown in context.
Language, terminology and tone used is appropriate and readily
understood by the target audience.
Terms, language and tone used are consitent (e.g. the same term is used
throughout).
Text and content is legible and scanable, with good typography and visual
contrast.
Online help is provided and is suitable for the user base (e.g. is written in
easy to understand langugage and only uses recognised terms). Where
appropriate contextual help is provided.
hemasses.com/)
Enter score
Very poor
Comments
Poor
Moderate
Good
Excellent
Score Out of N/A
The webpage properly labels each of these.
Provide a short rational for the score (Very Poor, Poor and Moderate), such as a
description of the issues found; examples of good practice and the likely impact
for users.
Weighting
(out of 5)
Weighting
ratio
Rating
The sole aim and goal of the usual user is to make a purchase. The functionality
and attributes for those have been correctly implemented.
The procedure is easily realized because it follows a typical layout used by all e-
commerce websites.
Only occasionally, even after several efforts, are the frequently used tasks
immediately available. This trait is not very reliable.
Expert users cannot use any specific shortcuts, and there is very little support
available for new users.
More advertisements than actual product content can be seen on the
homepage.
Homepage has a good page layout with sufficient white space
The URL is quite simple and predictable i.e gearbest.com
The navigation is perfect and available at top of the page as a nav bar
All are standard functions and are well supported
Webpage has decent rating for directing users for the information and tasks
required
Navigation is only provided based on name. And we cannot have more than one
feature use for searching.
It is easy even for a new user to understand this webpage. Simply shoppping is
easier in this website
Links are clearly labelled and descriptive.But cannot fing out if it is link or text
unless you hover on it
The location where we are currently not not presented properly , we need to see
the URL to find this, which is not easy to all
Required input fields are given while joining as a new user.
Nothing like help and instructions are provided in the website
Erros are easily identifiable
Although there is a contact option, it can be challenging for a novice user to
locate.
Each step involved in purchasing a product is described in detail at the top of the
page. For new users, it also offers login and registration.
Website is asking to sigup with email id for providing minimal amount of
information requested by customer
Required and optional fields are mention with "*" symbol for required an none for
optional
When a wrong thing is done a clear error message pops up or displays on the
same page like wrong card details or trying to buy out of stock items
Users can easily continue from that point where it is stopped or broken
Seller details are provided and similar products will be displayed
The usage of a lot of jargon in the language confuses the users.
Font size and style is perfect and easy to visual contrast and typography
Help option is there to help understanding the website
This option is not at all present in this website, the company should work on this
feature
Good content available about the products, the specifications , images and
reviews
More words are displayed in the name of the product like including specification
in the name itself
Usability guidelines
Importance
Features & functionality
1 Very high
2 Very high
3 High
4 Medium
5 Medium
Homepage / starting page
Medium
7 High
Medium
Navigation
9 Low
10 High
11 Medium
Features and functionality meet common user goals and objectives
Key and common user goals and objectives (e.g. carry out some transaction, find some information, carry out some research
etc…) should have been identified and addressed. Ideally the site or application should allow users to meet all of their key goals
and objectives. Features and functionality support users desired workflows
The site or application should support or at least be compatible with the way that users wish to work. For example, users might
want to be able to carry out bulk transactions or be able to save and return to their work.
Frequently-used tasks are readily available (e.g. easily accessible from the homepage) and well supported
For example short cuts and a login to retrieve details might be provided to speed up the completion of frequently carried out
tasks. Users are adequately supported according to their level of expertise
For example, novice users are given help and instructions and features are progressively disclosed (e.g. advanced features not
being shown by default).
Calls to action (e.g. register, add to basket, submit) are clear, well labelled and appear clickable
Possible actions should always be clear and the primary call to action (i.e. the most common or desirable user action) should
stand out on the page or screen.
The Homepage / starting page provides a clear snapshot and overview of the content, features and functionality
available
For example, an introduction and overview of the site is provided together with section snapshots and example content. The homepage / starting page is effective in orienting and directing users to their desired information and tasks
Users should be able to work out where they need to go to complete a given task (e.g. carry out some research, complete a
transaction). The homepage / starting page layout is clear and uncluttered with sufficient 'white space'
Users should be able to quickly scan the homepage and make sense of both the content available and of how the site is
structured.
Users can easily access the site or application
For example, the URL is predictable and is returned by search engines. If a user attempts to find the site via a search engine, it
should ideally be returned on the first page of search results for likely queries.
The navigational scheme is easy to find, intuitive and consistent
Users should be able to very easily locate and use the navigational scheme (e.g. left hand menu, top menu, tabbed menu), and it
should not be significantly different across the site or application (unless a decision has been made to specifically differentiate a
given section or area).
The navigation has sufficient flexibility to allow users to navigate by their desired means
For example a user might want to be able to search for an item or browse by size, name or type. Although not all user
preferences can or indeed should be addressed, the most useful and common navigational means should be supported.
24 Very low
Forms
25 Medium
26 Low
27 Low
28 Medium
29 Medium
Errors
High
Medium
Medium
33 Medium
Content & text
Users can easily give feedback
For example, via email or an online feedback / contact us form. There should be an indication of how long users can expect to
wait for a response if a query has been made.
Complex forms and processes are broken up into readily understood steps and sections
For example, a checkout process might be broken up in to 'address', 'delivery options', 'payment' and 'confirmation'. Where a
process is used a progress indicator is present with clear numbers or named stages.
A minimal amount of information is requested and where necessary justification is given for asking for information
For example a site might outline that a telephone number is required in case there is an issue with a transaction. Users shouldn't
be asked for extraneous information and where possible information should be auto populated (e.g. postcode lookup, code
lookup) to keep input to a minimum.
Required and optional form fields are clearly indicated (e.g. using text or '')*
Where most fields are required the optional fields should be identified and when most fields are optional the required fields
should be identified.
Appropriate input fields are used and required formats are indicated
Appropriate input fields might include calendar for date selection, drop downs for selection and radio button for small selections.
Text might be used to indicate the required format or an example might be provided. Field lengths should correspond to the
expected input so for example an email input field should be long, where as an initials input field should be very short.
Help and instructions (e.g. examples, information required) are provided where necessary
Where input is non trivial or is likely to require some explanation this should be provided. Where a-lot of explanation is necessary
a link to a page outlining what is required should be provided.
Errors are clear, easily identified and appear in appropriate locations
Errors should be immediately apparent to users and ideally be located close to the offending input or function (e.g. adjacent to an
input entry field). Inputs causing an error should be highlighted, together with an explanation for the error.
Error messages are concise, written in easy to understand language and describe what's occurred and what action is
necessary
Errors should avoid using very technical terms or jargon and should be written from the user's perspective.
Common user errors have been taken into consideration and where possible prevented
Common user errors might be missing fields, invalid formats and invalid selections. For example, fields might limit input to
particular a format (e.g. numbers only) or only become available once certain criteria have been met. JavaScript might also be
utilised to provide immediate feedback for common formatting errors or errors caused by missing fields.
Users are able to easily recover (i.e. not have to start again) from errors
For example, users might be able to re-edit and resubmit a form or enter a different value.
34 Very high
35 Low
36 High
37 Medium
38 Medium
Help
39 High
40 Medium
41 Medium
42 Low
Performance
High
Medium
Medium
Content available (e.g. text, images, video, audio) is appropriate and sufficiently relevant, and detailed to meet user
goals
Content should also be appropriately formatted, so for example videos and audio should be directly playable (i.e. shouldn't need
to be downloaded to be played) and images should be of a sufficient quality. Links to other useful and relevant content (e.g. related pages, external websites or documents) are available and shown
in context
For example there might be links from an article to related articles, related content or related external websites.
Language, terminology and tone used is appropriate and readily understood by the target audience
Jargon should be kept to a minimum and plain language should be used where ever possible.
Terms, language and tone used are consistent (e.g. the same term is used throughout)
Capitalisation (e.g. 'Main title'; 'Main Title'; 'MAIN TITLE') and grammar should be consistent, together with the use of formal or
informal terms (e.g. could not vs couldn't; what's vs what is etc...).
Text and content is legible and scanable, with good typography and visual contrast
Users should be able to quickly scan headers and body text, in order to get an overview of what's available.
Online help is provided and is suitable for the user base
Help should be written in easy to understand language and only uses recognised terms. Users should be able to easily find and
access help and where appropriate contextual help should be available, such as help for a specific page, feature or process.
Online help is concise, easy to read and written in easy to understand language
Help should cover the essentials without providing excessive detail and shouldn't use jargon or technical terminology that isn't
likely to be understood by users.
Accessing online help does not impede users
Users should be able to resume work where they left off after accessing help. Ideally help should be available directly on a page
or using a new window. If help is provided in the form of a document, it should be formatted for the web (e.g. PDF, rather than a
Word document). Users can easily get further help (e.g. telephone or email address)
If a telephone help number is provided the hours of operation should be shown. If an email address or online form is provided, an
indication should be given of how long a response is likely to take (e.g. within the next 24 hrs).
Site or application performance doesn't inhibit the user experience (e.g. slow page downloads, long delays)
Web page downloads shouldn't take longer than 5 seconds and on page interactions (e.g. using an application or AJAX
functionality) shouldn't take any longer than 1 second to respond. Interactions taking longer than 1 second to respond should
provide suitable feedback to show that something is taking place (e.g. an hour glass or swirling graphic).
Errors and reliability issues don't inhibit the user experience
Sites and applications should be free of bugs and shouldn't have any broken links.
Possible user configurations (e.g. browsers, resolutions, computer specs) are supported
Websites should be usable at a 800x600 screen resolution and should work with the most common browsers (IE, Firefox, Opera,
Chrome etc…). Applications should be usable with common computer specifications (operation system, memory, available disk
space) and screen resolutions (e.g. 800x600, 1025x768).
