1. Please rate the following features based on your evaluation:
1.a) Option Menu
2Poor 2 Weak 2 Medium 2 Good 2 Strong
1.b) Sharing Audio/Video/Text about museum to your social networks 2Poor 2 Weak 2 Medium 2 Good 2 Strong
1.c) Audio and video transcript about interesting museum artifacts 2Poor 2 Weak 2 Medium 2 Good 2 Strong
1.d) More information on Wikipedia
2Poor 2 Weak 2 Medium 2 Good 2 Strong
1.e) Delete recent activities
2Poor 2 Weak 2 Medium 2 Good 2 Strong
2. Which kind of information about museums do you find more accessible? 2Audio transcript 2 Video media 2 Text transcript
3. What features of the augmented-reality museum application are vague or confusing to you; add comments if any?
4. Does the menu operation seem easy to operation or difficult? What makes it that way?
5. What other features do you think should be included in the augmented- reality museum Application?
6. What do you like best about the augmented-reality museum application?
7. What part or feature do you like the least?
8. Scale the rating as per usefulness of Augmented Reality Museum Appli- cation (1 being lowest and 5 being highest rating):
21 2 2 2 3 24 2 5
9.Would you like to use the augmented-reality museum application for your next trip to any museum?
2Yes 2 No
10. Any suggestions to improve the augmented-reality museum application?
11. Would you like to make any other comments about the augmented- reality museum application?
Appendix C
Appendices to Chapter 3
C.1 Adapted heuristics
# Original heuristic Modified version
1 Visibility of system status The system should always keep users informed about what is going on, through appropri- ate feedback within reasonable time.
The application should always keep user informed about what is going on. The information about the used database or a category of points of interest should be always visible as well as location tracking status and orientation. All information should be given through appro- priate feedback within reason- able time.
2 Match between system and the real world The system should speak the
users’ language, with words, phrases and concepts familiar to the user, rather than system- oriented terms. Follow real- world conventions, making in- formation appear in a natural and logical order.
The application should show correct user’s location and ori- entation and also correct lo- cation and distance to visible points of interest. The distance units should respect user’s lo- cale.
# Original heuristic Modified version Users often choose system func-
tions by mistake and will need a clearly marked “emergency exit” to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
Allow user to switch freely be- tween different databases and categories of points of interest. Allow also to choose between the map navigation and the live video overlay. Return to the same state after switching be- tween applications. Consider returning into a default state af- ter a long interruption.
4 Consistency and standards Users should not have to won- der whether different words, sit- uations, or actions mean the same thing. Follow platform conventions.
The user interface controls should respect conventions used for mobile devices. All used graphic symbols should be clear and intuitive.
5 Error prevention
Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Ei- ther eliminate error-prone con- ditions or check for them and present users with a confirma- tion option before they commit to the action.
The application should be de- signed in such way, that it pre- vents errors from happening. If it is not possible, the applica- tion should be able to recover.
6 Recognition rather than recall Minimize the user’s memory load by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. In- structions for use of the system should be visible or easily re- trievable whenever appropriate.
Show user “where” he is in the application and make nav- igation throughout the applica- tion simple. The most impor- tant functions (like search and switching between the map nav- igation and the live video over- lay) should be always easily ac- cessible.
# Original heuristic Modified version Accelerators – unseen by the
novice user – may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
Make user’s favorite func- tions/databases easily acces- sible. Allow user to configure shortcuts for these options.
8 Aesthetic and minimalist design Dialogues should not contain information which is irrelevant or rarely needed. Every ex- tra unit of information in a di- alogue competes with the rel- evant units of information and diminishes their relative visibil- ity.
Screens should not contain in- formation which is irrelevant or unneeded.
9 Help users recognize, diagnose, and recover from errors Error messages should be ex-
pressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
All errors should be in a clear, user-readable form and they should suggest a reasonable so- lution. If an error happens, user should be notified. There should be no “silent” errors. 10 Help and documentation
Even though it is better if the system can be used without documentation, it may be nec- essary to provide help and doc- umentation. Any such informa- tion should be easy to search, focused on the user’s task, list concrete steps to be carried out, and not be too large.
Provide some help and/or doc- umentation. Both a quick start help and a detailed documenta- tion should be available.