Advertisement
Guest User

Untitled

a guest
Mar 28th, 2017
58
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.49 KB | None | 0 0
  1. Part One: Evaluating the app
  2.  
  3. Swipe left – allows the user to choose from two options edit or delete
  4. Edit – lets the user tick and untick any available bus codes suited for their travel
  5. Delete – removes the bus stop from the users list of stops
  6. Stop no. – displays the bus code, buses destination and the time of arrival/ bus status
  7. Save – saves the user selected route for selected bus stop
  8. Plus, icon – displays a map or the area with bus icons indicating bus stops
  9. Search bar – allow user to find closest bus stop when address or bus stop no. entered
  10. Zoom – allows user to zoom in and out, to view different bus stop locations
  11. Drag – allows user to move map
  12. Bus icon – reveals bus stop number and address
  13. Back arrow icon – navigate back to previous window
  14. Forward arrow icon – reveals bus codes that pass the current bus stop
  15.  
  16.  
  17.  
  18.  
  19.  
  20.  
  21.  
  22.  
  23.  
  24.  
  25.  
  26.  
  27.  
  28.  
  29.  
  30.  
  31.  
  32.  
  33.  
  34.  
  35.  
  36.  
  37.  
  38.  
  39.  
  40.  
  41.  
  42.  
  43.  
  44.  
  45.  
  46.  
  47.  
  48.  
  49.  
  50.  
  51.  
  52.  
  53.  
  54.  
  55. Visibility of system status
  56. The system should always keep users informed about what is going on, through appropriate feedback within reasonable time.
  57.  
  58. When a user touches the screen the application respond by adjusting what is displayed instantly for example the track my bus application displays a rectangle box with texts to inform the user what bus stop it is and the location of the bus stop, this is a form of feedback for the user which is instantaneous. The user can also view the distance between their current position and intended bus stop through a bus icon and person icon. The system provides simple and easy to understand feedback to the user by changing windows when a button is pressed or by highlighting options in green this is a form of feedback that will be useful to the user. The feedback is vital to keep the user informed on how they are navigating through the system.
  59.  
  60. Match between system and the real world
  61. 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 information appear in a natural and logical order.
  62.  
  63. The system provides the user with simple, easy to use and understand navigation controls. When a user is viewing their list of saved buses stops they are easily able to add another by pressing the plus icon. The plus icon is a natural and intuitive icon which lets the user know if they would like to add, in this case they will add a new bus top to their current list. The system informs that there will be no service for the next two hours when the bus stop button is pressed, this is more suitable for a user rather than a system-oriented term such as “no service”. Providing an estimate time for next service will help provide more information to the user. A system that provides intuitive phrases or pictures will be easier to use by a new user as it will be naturally and logically intuitive.
  64.  
  65. User control and freedom
  66. Users often choose system functions 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.
  67.  
  68. The track my bus system provides a back-arrow icon for users to use if they have made a mistake or need to view the previous screen. The intuitive icon will give users a better experience using the system since it will be straightforward to figure out the process. A system that consist of few windows will be much easier to navigate rather than a system with a large quantity of windows.
  69.  
  70. Consistency and standards
  71. Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform conventions.
  72.  
  73. The system is consistent in using logical and intuitive icons so that the standard of understanding what the icons means is simple. The user will naturally know what icons to use when they continue using the system. The system is not consistent when you save a stop without ticking a bus route. If the user chosen the bus stop it will not load any results, the error message does not show the user that they have not chosen a stop. The system should consistently inform the user
  74.  
  75. Error prevention
  76. Even better than good error messages is a careful design which prevents a problem from occurring in the first place. Either eliminate error-prone conditions or check for them and present users with a confirmation option before they commit to the action.
  77. (Read full article on preventing user errors.)
  78.  
  79. The track my bus system provides a search bar that eliminates user error in spelling by providing suggestions to compared to what the user has entered. By providing suggestions the user is less prone to making errors, the system also helps speed the process up by making it easier to select the suggestions. A system that provides error prevention is a system that will operate more smoothly for the user.
  80.  
  81. Recognition rather than recall
  82. 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. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
  83. (Read full article on recognition vs. recall in UX.)
  84.  
  85. The AT metro track my bus consistently uses icons that stay the same, which users will recognise and naturally understand what each icon means. Being a system that is easy to use is easy for the user to remember what each icon does or how to navigate through the system. By minimising the amount of instructions required to add a bus stop the user will more likely remember it through photographic memory, which is a positive point in the users view.
  86.  
  87. Flexibility and efficiency of use
  88. 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.
  89.  
  90. Aesthetic and minimalist design
  91. Dialogues should not contain information which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
  92.  
  93. The system has been deigned to be easy and simple so that anyone can intuitively use it. By providing intuitive design aspects into the system such as the plus icon to add a bus stop, the user can easily figure out that the plus icon means add. Each window displayed in the system provides relevant and most minimal information for users. Providing relevant and minimal information to users through feedback ensures that the system is easy to use and understand.
  94.  
  95. Help users recognize, diagnose, and recover from errors
  96. Error messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
  97.  
  98. The system displays an error message when there is “no service for the next two hours”. This error message in informative because it also give the user an idea of when the next bus on route is due to arrive. Information is important for the user to recognize or diagnose in order to provide a partial solution when the expected solution is not what the user wants.
  99.  
  100. Help and documentation
  101. Even though it is better if the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120. Usability Test Plan Template
  121. Product under test
  122. Describe the app and its core functionality.
  123. The AT metro track my bus system is simple system that is designed so that new users will easily understand how the application works through logical intuition. The applications main goal is to provide users with essential information on their preferred bus stops.
  124. Test Objectives
  125. Describe the objectives of the usability test.
  126.  
  127. Participants Required
  128. Describe the number of participants to be recruited and the attributes of the participants you would like to recruit.
  129. Tasks to Undertake
  130. Describe the tasks you will ask participants to perform.
  131. Data Collection
  132. Describe specifically what data you want to collect about each participant and each task. If you choose to have a questionnaire, include it in this section.
  133. Test Procedure
  134. Provide the scripted step‐by‐step instructions for running the test (imagine someone else will be running the tests for you).
  135. Analysis
  136. Describe how the data collected will be analysed.
  137. Results
  138. Describe how the results will be reported.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement