| 1 | <?xml version="1.0" encoding="UTF-8"?> |
---|
| 2 | <smellDescriptions |
---|
| 3 | xmlns="http://autoquest.informatik.uni-goettingen.de" |
---|
| 4 | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
---|
| 5 | xsi:schemaLocation="http://autoquest.informatik.uni-goettingen.de smellDescriptions.xsd"> |
---|
| 6 | |
---|
| 7 | <smellDescription smellId="TEXT_FIELD_INPUT_RATIO" briefText="many text inputs"> |
---|
| 8 | <textFragment> |
---|
| 9 | The ratio of interactions that enter text into text fields is relatively high in comparison |
---|
| 10 | with the other user interactions ( |
---|
| 11 | </textFragment> |
---|
| 12 | <parameterFragment parameterName="textInputRatio" /> |
---|
| 13 | <textFragment> |
---|
| 14 | %). This should be reduced. As an example, entering data can also be done using check boxes |
---|
| 15 | or combo boxes in the case predefined values must be entered. |
---|
| 16 | </textFragment> |
---|
| 17 | </smellDescription> |
---|
| 18 | |
---|
| 19 | <smellDescription smellId="TEXT_FIELD_INPUT_REPETITIONS" briefText="many text repetitions"> |
---|
| 20 | <textFragment> |
---|
| 21 | In |
---|
| 22 | </textFragment> |
---|
| 23 | <parameterFragment parameterName="textRepetitionRatio" /> |
---|
| 24 | <textFragment> |
---|
| 25 | % of entering text into text field |
---|
| 26 | </textFragment> |
---|
| 27 | <parameterFragment parameterName="textField1" /> |
---|
| 28 | <textFragment> |
---|
| 29 | , the same text was also entered into text field |
---|
| 30 | </textFragment> |
---|
| 31 | <parameterFragment parameterName="textField2" /> |
---|
| 32 | <textFragment> |
---|
| 33 | during the same session. Perhaps this can be automated, so that the user does not have to |
---|
| 34 | reenter the same text several times into different text fields. |
---|
| 35 | </textFragment> |
---|
| 36 | </smellDescription> |
---|
| 37 | |
---|
| 38 | <smellDescription smellId="TEXT_FIELD_NO_LETTER_OR_DIGIT_RATIO" briefText="many special signs"> |
---|
| 39 | <parameterFragment parameterName="noLetterOrDigitRatio" /> |
---|
| 40 | <textFragment> |
---|
| 41 | % of the text entered into text field |
---|
| 42 | </textFragment> |
---|
| 43 | <parameterFragment parameterName="textField" /> |
---|
| 44 | <textFragment> |
---|
| 45 | was no letter or digit. This is an indicator that the entered data has to follow a specific |
---|
| 46 | syntax. This should be supported by syntax checking, auto completion or even providing the |
---|
| 47 | text fields in a way that does not require the entering of special signs as they are already |
---|
| 48 | included at the right positions. |
---|
| 49 | </textFragment> |
---|
| 50 | </smellDescription> |
---|
| 51 | |
---|
| 52 | <smellDescription smellId="HIGH_EVENT_COVERAGE" briefText="often executed"> |
---|
| 53 | <textFragment> |
---|
| 54 | The task |
---|
| 55 | </textFragment> |
---|
| 56 | <parameterFragment parameterName="task" /> |
---|
| 57 | <textFragment> |
---|
| 58 | covers |
---|
| 59 | </textFragment> |
---|
| 60 | <parameterFragment parameterName="ratio" /> |
---|
| 61 | <textFragment> |
---|
| 62 | % of all recorded user actions. Therefore, it should be executed with a high efficiency. |
---|
| 63 | You should consider making the task more efficient, by minimizing the number of actions to |
---|
| 64 | be executed by users for fulfilling this task. |
---|
| 65 | </textFragment> |
---|
| 66 | </smellDescription> |
---|
| 67 | |
---|
| 68 | <smellDescription smellId="INEFFICIENT_ACTIONS" briefText="inefficient actions"> |
---|
| 69 | <textFragment> |
---|
| 70 | For executing task |
---|
| 71 | </textFragment> |
---|
| 72 | <parameterFragment parameterName="task" /> |
---|
| 73 | <textFragment> |
---|
| 74 | , the user has to execute a high number of inefficient actions ( |
---|
| 75 | </textFragment> |
---|
| 76 | <parameterFragment parameterName="ratio" /> |
---|
| 77 | <textFragment> |
---|
| 78 | % in average). Such actions are, e.g., scrolls. The number of inefficient actions should |
---|
| 79 | be as minimal as possible to increase the users efficiency in executing a task. Please |
---|
| 80 | check the task structure for occurrences of the following event tasks and consider to prevent |
---|
| 81 | them: scrolling. |
---|
| 82 | </textFragment> |
---|
| 83 | </smellDescription> |
---|
| 84 | |
---|
| 85 | <smellDescription smellId="COOCCURENCE_SUCCEED" briefText="usual cooccurrence"> |
---|
| 86 | <textFragment> |
---|
| 87 | In |
---|
| 88 | </textFragment> |
---|
| 89 | <parameterFragment parameterName="ratio" /> |
---|
| 90 | <textFragment> |
---|
| 91 | % of all occurrences, the task |
---|
| 92 | </textFragment> |
---|
| 93 | <parameterFragment parameterName="task1" /> |
---|
| 94 | <textFragment> |
---|
| 95 | is succeeded by |
---|
| 96 | </textFragment> |
---|
| 97 | <parameterFragment parameterName="task2" /> |
---|
| 98 | <textFragment> |
---|
| 99 | . This shows, that both tasks are likely used in combination. Please consider to support the |
---|
| 100 | execution of both tasks in one user action, e.g., by providing an appropriate button, to |
---|
| 101 | reduce the number of actions to be performed by the user. |
---|
| 102 | </textFragment> |
---|
| 103 | </smellDescription> |
---|
| 104 | |
---|
| 105 | <smellDescription smellId="COOCCURENCE_PRECED" briefText="usual cooccurrence"> |
---|
| 106 | <textFragment> |
---|
| 107 | In |
---|
| 108 | </textFragment> |
---|
| 109 | <parameterFragment parameterName="ratio" /> |
---|
| 110 | <textFragment> |
---|
| 111 | % of all occurrences, the task |
---|
| 112 | </textFragment> |
---|
| 113 | <parameterFragment parameterName="task2" /> |
---|
| 114 | <textFragment> |
---|
| 115 | is preceded by |
---|
| 116 | </textFragment> |
---|
| 117 | <parameterFragment parameterName="task1" /> |
---|
| 118 | <textFragment> |
---|
| 119 | . This shows, that both tasks are likely used in combination. Please consider to support the |
---|
| 120 | execution of both tasks in one user action, e.g., by providing an appropriate button, to |
---|
| 121 | reduce the number of actions to be performed by the user. |
---|
| 122 | </textFragment> |
---|
| 123 | </smellDescription> |
---|
| 124 | |
---|
| 125 | <smellDescription smellId="HIGH_TARGET_DISTANCE" briefText="long way to go"> |
---|
| 126 | <textFragment> |
---|
| 127 | For executing the task |
---|
| 128 | </textFragment> |
---|
| 129 | <parameterFragment parameterName="task" /> |
---|
| 130 | <textFragment> |
---|
| 131 | , the user utilizes |
---|
| 132 | </textFragment> |
---|
| 133 | <parameterFragment parameterName="noOfGUIElements" /> |
---|
| 134 | <textFragment> |
---|
| 135 | GUI elements on average. As these GUI elements have a high distance to each other ( |
---|
| 136 | </textFragment> |
---|
| 137 | <parameterFragment parameterName="distance" /> |
---|
| 138 | <textFragment> |
---|
| 139 | on average ), they should be more colocated to ease the execution of the task for the user. |
---|
| 140 | </textFragment> |
---|
| 141 | </smellDescription> |
---|
| 142 | |
---|
| 143 | <smellDescription smellId="MISSING_FEEDBACK" briefText="missing feedback"> |
---|
| 144 | <textFragment> |
---|
| 145 | A click on the button |
---|
| 146 | </textFragment> |
---|
| 147 | <parameterFragment parameterName="button" /> |
---|
| 148 | <textFragment> |
---|
| 149 | seems to be missing user feedback. In |
---|
| 150 | </textFragment> |
---|
| 151 | <parameterFragment parameterName="multipleClickCount" /> |
---|
| 152 | <textFragment> |
---|
| 153 | of |
---|
| 154 | </textFragment> |
---|
| 155 | <parameterFragment parameterName="allClickCount" /> |
---|
| 156 | <textFragment> |
---|
| 157 | uses, the button was clicked several times. The average waiting time between two subsequent |
---|
| 158 | clicks is |
---|
| 159 | </textFragment> |
---|
| 160 | <parameterFragment parameterName="averageWaitingTime" /> |
---|
| 161 | <textFragment> |
---|
| 162 | seconds. This is typical user behavior if the user does not see progress following his |
---|
| 163 | actions. Please consider showing the user some progress after he performed the |
---|
| 164 | first click. This is especially important if the operation triggered with the click usually |
---|
| 165 | takes longer than one second. This smell was observed based on task |
---|
| 166 | </textFragment> |
---|
| 167 | <parameterFragment parameterName="task" /> |
---|
| 168 | <textFragment> |
---|
| 169 | . |
---|
| 170 | </textFragment> |
---|
| 171 | </smellDescription> |
---|
| 172 | |
---|
| 173 | <smellDescription smellId="UNUSED_GUI_ELEMENTS" briefText="unused GUI elements"> |
---|
| 174 | <parameterFragment parameterName="ratio" /> |
---|
| 175 | <textFragment> |
---|
| 176 | % of the GUI elements ( |
---|
| 177 | </textFragment> |
---|
| 178 | <parameterFragment parameterName="noOfUnused" /> |
---|
| 179 | <textFragment> |
---|
| 180 | of |
---|
| 181 | </textFragment> |
---|
| 182 | <parameterFragment parameterName="noOfAll" /> |
---|
| 183 | <textFragment> |
---|
| 184 | ) are not used. This can have several reasons. Either they are not |
---|
| 185 | visible to the user or they are not required. If they are important, they may not be |
---|
| 186 | recognized by the user. This can be caused by visual design or because they are too hidden. |
---|
| 187 | If they are less important, they can either be removed from the GUI or relocated to a less |
---|
| 188 | prominent position. The unused GUI elements are: |
---|
| 189 | </textFragment> |
---|
| 190 | <parameterFragment parameterName="unusedGuiElements" /> |
---|
| 191 | </smellDescription> |
---|
| 192 | |
---|
| 193 | <smellDescription smellId="DATA_ENTRY_METHOD_CHANGE" briefText="data entry method change"> |
---|
| 194 | <textFragment> |
---|
| 195 | When executing task |
---|
| 196 | </textFragment> |
---|
| 197 | <parameterFragment parameterName="task" /> |
---|
| 198 | <textFragment> |
---|
| 199 | , the users have to switch between keyboard and mouse in |
---|
| 200 | </textFragment> |
---|
| 201 | <parameterFragment parameterName="ratio" /> |
---|
| 202 | <textFragment> |
---|
| 203 | % on average between two subsequently executed actions. Frequently changing between mouse and |
---|
| 204 | keyboard causes users to become slow when utilizing a GUI. Hence, these should be minimized to |
---|
| 205 | optimize the users performance. |
---|
| 206 | </textFragment> |
---|
| 207 | </smellDescription> |
---|
| 208 | |
---|
| 209 | <smellDescription smellId="GOOD_DEFAULTS" briefText="good defaults"> |
---|
| 210 | <textFragment> |
---|
| 211 | When using GUI element |
---|
| 212 | </textFragment> |
---|
| 213 | <parameterFragment parameterName="guiElement" /> |
---|
| 214 | <textFragment> |
---|
| 215 | in view |
---|
| 216 | </textFragment> |
---|
| 217 | <parameterFragment parameterName="view" /> |
---|
| 218 | <textFragment> |
---|
| 219 | , the values selected by the users are not equally distributed. Hence, it may be useful to |
---|
| 220 | have a good default value. The users entered the following values with their respective |
---|
| 221 | frequency in brackets most often (only the five most important entries listed): |
---|
| 222 | </textFragment> |
---|
| 223 | <parameterFragment parameterName="selectedValues" /> |
---|
| 224 | </smellDescription> |
---|
| 225 | |
---|
| 226 | <smellDescription smellId="CHECK_BOX_SINGLE_SELECTION" briefText="check box single selection"> |
---|
| 227 | <textFragment> |
---|
| 228 | Found a group of check boxes of which only one is usually selected. In this case, radio |
---|
| 229 | buttons should be used instead, if the alternatives are mutually exclusive. The check boxes |
---|
| 230 | belonging to the group are: |
---|
| 231 | </textFragment> |
---|
| 232 | <parameterFragment parameterName="radioButtons" /> |
---|
| 233 | </smellDescription> |
---|
| 234 | |
---|
| 235 | <smellDescription smellId="COMMON_TASK_RATE" briefText="common task rate"> |
---|
| 236 | <textFragment> |
---|
| 237 | The user sessions show only a few commonalities. On average, ten subsequently executed |
---|
| 238 | actions need to be described by |
---|
| 239 | </textFragment> |
---|
| 240 | <parameterFragment parameterName="ratio" /> |
---|
| 241 | <textFragment> |
---|
| 242 | different determined tasks. In the worst case, each action is its own task. In the best case, |
---|
| 243 | all actions are described by the same tasks. This indicates, that the users act relatively |
---|
| 244 | different as otherwise, all their actions would be described by only a few tasks. Hence, |
---|
| 245 | users seem to be missing guidance, as otherwise, they would behave similar resulting in less |
---|
| 246 | generated task which still cover many recorded actions. |
---|
| 247 | </textFragment> |
---|
| 248 | </smellDescription> |
---|
| 249 | |
---|
| 250 | <smellDescription smellId="MISLEADING_CLICK_CUE" briefText="misleading cue to click"> |
---|
| 251 | <textFragment> |
---|
| 252 | In the |
---|
| 253 | </textFragment> |
---|
| 254 | <parameterFragment parameterName="noOfViewDisplays" /> |
---|
| 255 | <textFragment> |
---|
| 256 | times the view |
---|
| 257 | </textFragment> |
---|
| 258 | <parameterFragment parameterName="view" /> |
---|
| 259 | <textFragment> |
---|
| 260 | has been displayed, the element |
---|
| 261 | </textFragment> |
---|
| 262 | <parameterFragment parameterName="element" /> |
---|
| 263 | <textFragment> |
---|
| 264 | has been clicked |
---|
| 265 | </textFragment> |
---|
| 266 | <parameterFragment parameterName="uselessClicks" /> |
---|
| 267 | <textFragment> |
---|
| 268 | times although it may not be clickable (it is no, e.g., button). If the element is not |
---|
| 269 | clickable, then the element seems to give a cue that it was clickable although it is not. |
---|
| 270 | Hence, it should be considered to change the appearance of the element to prevent it from |
---|
| 271 | looking clickable. |
---|
| 272 | </textFragment> |
---|
| 273 | </smellDescription> |
---|
| 274 | |
---|
| 275 | <smellDescription smellId="MOST_OFTEN_DONE_FIRST" briefText="most often done first in view"> |
---|
| 276 | <textFragment> |
---|
| 277 | When opening the view |
---|
| 278 | </textFragment> |
---|
| 279 | <parameterFragment parameterName="view" /> |
---|
| 280 | <textFragment> |
---|
| 281 | , users most often position the cursor into the text field |
---|
| 282 | </textFragment> |
---|
| 283 | <parameterFragment parameterName="textfield" /> |
---|
| 284 | <textFragment> |
---|
| 285 | (in |
---|
| 286 | </textFragment> |
---|
| 287 | <parameterFragment parameterName="ratio" /> |
---|
| 288 | <textFragment> |
---|
| 289 | % of cases when the view is opened). This should be automated to remove one action required |
---|
| 290 | for users. |
---|
| 291 | </textFragment> |
---|
| 292 | </smellDescription> |
---|
| 293 | </smellDescriptions> |
---|