Changeset 1335 for trunk/autoquest-core-usability/src/main/resources/defectDescriptions_en.xml

Timestamp:

01/24/14 13:50:29 (11 years ago)

Author:

pharms

Message:

• corrected and extended usability evaluations
• checking now more text field specific for required input formats and word repetitions
• checking also for required scrolls

File:

• trunk/autoquest-core-usability/src/main/resources/defectDescriptions_en.xml (modified) (2 diffs)

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

@@ -12 +12 @@
     <parameterFragment parameterName="textInputRatio" />
     <textFragment>
-      ). This should be reduced. As an example, entering data can also be done using check boxes
+      %). This should be reduced. As an example, entering data can also be done using check boxes
       or combo boxes in the case predefined values must be entered.
     </textFragment>
@@ -19 +19 @@
   <defectDescription defectId="TEXT_FIELD_INPUT_REPETITIONS">
     <textFragment>
-      Several interactions that enter text into text fields repeat tokens such as words or
-      specific signs (
+      In
     </textFragment>
     <parameterFragment parameterName="textRepetitionRatio" />
     <textFragment>
-      ). This is an indicator that the same data must be entered several times. This could be
-      better supported by using e.g. automatic filling of input fields, provision of combo
-      boxes or lists prefilled with data that was already entered previously. 
+      % of entering text into text field 
+    </textFragment>
+    <parameterFragment parameterName="textField1" />
+    <textFragment>
+      , the same text was also entered into text field
+    </textFragment>
+    <parameterFragment parameterName="textField2" />
+    <textFragment>
+      during the same session. Perhaps this can be automated, so that the user does not have to
+      reenter the same text several times into different text fields.
     </textFragment>
   </defectDescription>
   
   <defectDescription defectId="TEXT_FIELD_NO_LETTER_OR_DIGIT_RATIO">
-    <textFragment>
-      Much of the text entered into text fields contains signs other than letters or digits (
-    </textFragment>
     <parameterFragment parameterName="noLetterOrDigitRatio" />
     <textFragment>
-      ). This is an indicator that the entered data has to follow a specific syntax. This should
-      be supported by syntax checking, auto completion or even providing the text fields in a way
-      that does not require the entering of special signs as they are already included at the right
-      positions.
+      % of the text entered into text field
+    </textFragment>
+    <parameterFragment parameterName="textField" />
+    <textFragment>
+      was no letter or digit. This is an indicator that the entered data has to follow a specific
+      syntax. This should be supported by syntax checking, auto completion or even providing the
+      text fields in a way that does not require the entering of special signs as they are already
+      included at the right positions.
+    </textFragment>
+  </defectDescription>
+  
+  <defectDescription defectId="SCROLL_REQUIRED">
+    <textFragment>
+      In
+    </textFragment>
+    <parameterFragment parameterName="scrollRatio" />
+    <textFragment>
+      % of all occurrences, the task
+    </textFragment>
+    <parameterFragment parameterName="task" />
+    <textFragment>
+      is started with a scroll. This should be prevented as scrolling decreases the efficiency of
+      the user and indicates, that not all required information is visible at once in the
+      respective view. However, scrolling for reading of texts is no problem.
     </textFragment>
   </defectDescription>