Ignore:
Timestamp:
04/11/14 11:21:45 (11 years ago)
Author:
pharms
Message:
  • state of the HCSE 2014 Paper. An appropriate tag will follow.
File:
1 edited

Legend:

Unmodified
Added
Removed

  • trunk/autoquest-core-usability/src/main/resources/defectDescriptions_en.xml

    r1335 r1493  
    11<?xml version="1.0" encoding="UTF-8"?> 
    22<defectDescriptions 
    3   xmlns="http://quest" 
     3  xmlns="http://autoquest.informatik.uni-goettingen.de" 
    44  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    5   xsi:schemaLocation="http://quest defectDescriptions.xsd"> 
     5  xsi:schemaLocation="http://autoquest.informatik.uni-goettingen.de defectDescriptions.xsd"> 
    66   
    7   <defectDescription defectId="TEXT_FIELD_INPUT_RATIO"> 
     7  <defectDescription defectId="TEXT_FIELD_INPUT_RATIO" briefText="many text inputs"> 
    88    <textFragment> 
    99      The ratio of interactions that enter text into text fields is relatively high in comparison 
    … …  
    1717  </defectDescription> 
    1818   
    19   <defectDescription defectId="TEXT_FIELD_INPUT_REPETITIONS"> 
     19  <defectDescription defectId="TEXT_FIELD_INPUT_REPETITIONS" briefText="many text repetitions"> 
    2020    <textFragment> 
    2121      In 
    … …  
    3636  </defectDescription> 
    3737   
    38   <defectDescription defectId="TEXT_FIELD_NO_LETTER_OR_DIGIT_RATIO"> 
     38  <defectDescription defectId="TEXT_FIELD_NO_LETTER_OR_DIGIT_RATIO" briefText="many special signs"> 
    3939    <parameterFragment parameterName="noLetterOrDigitRatio" /> 
    4040    <textFragment> 
    … …  
    5050  </defectDescription> 
    5151   
    52   <defectDescription defectId="SCROLL_REQUIRED"> 
     52  <defectDescription defectId="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  </defectDescription> 
     67   
     68  <defectDescription defectId="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  </defectDescription> 
     84   
     85  <defectDescription defectId="COOCCURENCE_SUCCEED" briefText="usual cooccurrence"> 
    5386    <textFragment> 
    5487      In 
    5588    </textFragment> 
    56     <parameterFragment parameterName="scrollRatio" /> 
     89    <parameterFragment parameterName="ratio" /> 
    5790    <textFragment> 
    5891      % of all occurrences, the task 
    5992    </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  </defectDescription> 
     104   
     105  <defectDescription defectId="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  </defectDescription> 
     124   
     125  <defectDescription defectId="HIGH_TARGET_DISTANCE" briefText="long way to go"> 
     126    <textFragment> 
     127      For executing the task 
     128    </textFragment> 
    60129    <parameterFragment parameterName="task" /> 
    61130    <textFragment> 
    62       is started with a scroll. This should be prevented as scrolling decreases the efficiency of 
    63       the user and indicates, that not all required information is visible at once in the 
    64       respective view. However, scrolling for reading of texts is no problem. 
     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. 
    65140    </textFragment> 
    66141  </defectDescription> 
     142   
     143  <defectDescription defectId="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 defect was observed based on task 
     166    </textFragment> 
     167    <parameterFragment parameterName="task" /> 
     168    <textFragment> 
     169      . 
     170    </textFragment> 
     171  </defectDescription> 
     172   
     173  <defectDescription defectId="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  </defectDescription> 
    67192</defectDescriptions> 
Note: See TracChangeset for help on using the changeset viewer.