Index: trunk/autoquest-core-usability/src/main/resources/defectDescriptions.xsd
===================================================================
--- trunk/autoquest-core-usability/src/main/resources/defectDescriptions.xsd	(revision 1335)
+++ trunk/autoquest-core-usability/src/main/resources/defectDescriptions.xsd	(revision 1493)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <xsd:schema
-  targetNamespace="http://quest"
-  xmlns:tns="http://quest"
+  targetNamespace="http://autoquest.informatik.uni-goettingen.de"
+  xmlns:tns="http://autoquest.informatik.uni-goettingen.de"
   xmlns:xsd="http://www.w3.org/2001/XMLSchema"
   xmlns:jxb="http://java.sun.com/xml/ns/jaxb"
@@ -22,4 +22,5 @@
     </xsd:choice>
     <xsd:attribute name="defectId" type="xsd:string" use="required" />
+    <xsd:attribute name="briefText" type="xsd:string" use="required" />
   </xsd:complexType>
 
Index: trunk/autoquest-core-usability/src/main/resources/defectDescriptions_en.xml
===================================================================
--- trunk/autoquest-core-usability/src/main/resources/defectDescriptions_en.xml	(revision 1335)
+++ trunk/autoquest-core-usability/src/main/resources/defectDescriptions_en.xml	(revision 1493)
@@ -1,9 +1,9 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <defectDescriptions
-  xmlns="http://quest"
+  xmlns="http://autoquest.informatik.uni-goettingen.de"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
-  xsi:schemaLocation="http://quest defectDescriptions.xsd">
+  xsi:schemaLocation="http://autoquest.informatik.uni-goettingen.de defectDescriptions.xsd">
   
-  <defectDescription defectId="TEXT_FIELD_INPUT_RATIO">
+  <defectDescription defectId="TEXT_FIELD_INPUT_RATIO" briefText="many text inputs">
     <textFragment>
       The ratio of interactions that enter text into text fields is relatively high in comparison
@@ -17,5 +17,5 @@
   </defectDescription>
   
-  <defectDescription defectId="TEXT_FIELD_INPUT_REPETITIONS">
+  <defectDescription defectId="TEXT_FIELD_INPUT_REPETITIONS" briefText="many text repetitions">
     <textFragment>
       In
@@ -36,5 +36,5 @@
   </defectDescription>
   
-  <defectDescription defectId="TEXT_FIELD_NO_LETTER_OR_DIGIT_RATIO">
+  <defectDescription defectId="TEXT_FIELD_NO_LETTER_OR_DIGIT_RATIO" briefText="many special signs">
     <parameterFragment parameterName="noLetterOrDigitRatio" />
     <textFragment>
@@ -50,18 +50,143 @@
   </defectDescription>
   
-  <defectDescription defectId="SCROLL_REQUIRED">
+  <defectDescription defectId="HIGH_EVENT_COVERAGE" briefText="often executed">
+    <textFragment>
+      The task
+    </textFragment>
+    <parameterFragment parameterName="task" />
+    <textFragment>
+      covers
+    </textFragment>
+    <parameterFragment parameterName="ratio" />
+    <textFragment>
+      % of all recorded user actions. Therefore, it should be executed with a high efficiency.
+      You should consider making the task more efficient, by minimizing the number of actions to
+      be executed by users for fulfilling this task.
+    </textFragment>
+  </defectDescription>
+  
+  <defectDescription defectId="INEFFICIENT_ACTIONS" briefText="inefficient actions">
+    <textFragment>
+      For executing task
+    </textFragment>
+    <parameterFragment parameterName="task" />
+    <textFragment>
+      , the user has to execute a high number of inefficient actions (
+    </textFragment>
+    <parameterFragment parameterName="ratio" />
+    <textFragment>
+      % in average). Such actions are, e.g., scrolls. The number of inefficient actions should
+      be as minimal as possible to increase the users efficiency in executing a task. Please
+      check the task structure for occurrences of the following event tasks and consider to prevent
+      them: scrolling.
+    </textFragment>
+  </defectDescription>
+  
+  <defectDescription defectId="COOCCURENCE_SUCCEED" briefText="usual cooccurrence">
     <textFragment>
       In
     </textFragment>
-    <parameterFragment parameterName="scrollRatio" />
+    <parameterFragment parameterName="ratio" />
     <textFragment>
       % of all occurrences, the task
     </textFragment>
+    <parameterFragment parameterName="task1" />
+    <textFragment>
+      is succeeded by
+    </textFragment>
+    <parameterFragment parameterName="task2" />
+    <textFragment>
+      . This shows, that both tasks are likely used in combination. Please consider to support the
+      execution of both tasks in one user action, e.g., by providing an appropriate button, to
+      reduce the number of actions to be performed by the user.
+    </textFragment>
+  </defectDescription>
+  
+  <defectDescription defectId="COOCCURENCE_PRECED" briefText="usual cooccurrence">
+    <textFragment>
+      In
+    </textFragment>
+    <parameterFragment parameterName="ratio" />
+    <textFragment>
+      % of all occurrences, the task
+    </textFragment>
+    <parameterFragment parameterName="task2" />
+    <textFragment>
+      is preceded by
+    </textFragment>
+    <parameterFragment parameterName="task1" />
+    <textFragment>
+      . This shows, that both tasks are likely used in combination. Please consider to support the
+      execution of both tasks in one user action, e.g., by providing an appropriate button, to
+      reduce the number of actions to be performed by the user.
+    </textFragment>
+  </defectDescription>
+  
+  <defectDescription defectId="HIGH_TARGET_DISTANCE" briefText="long way to go">
+    <textFragment>
+      For executing 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.
+      , the user utilizes
+    </textFragment>
+    <parameterFragment parameterName="noOfGUIElements" />
+    <textFragment>
+      GUI elements on average. As these GUI elements have a high distance to each other (
+    </textFragment>
+    <parameterFragment parameterName="distance" />
+    <textFragment>
+      on average ), they should be more colocated to ease the execution of the task for the user.
     </textFragment>
   </defectDescription>
+  
+  <defectDescription defectId="MISSING_FEEDBACK" briefText="missing feedback">
+    <textFragment>
+      A click on the button
+    </textFragment>
+    <parameterFragment parameterName="button" />
+    <textFragment>
+      seems to be missing user feedback. In
+    </textFragment>
+    <parameterFragment parameterName="multipleClickCount" />
+    <textFragment>
+      of
+    </textFragment>
+    <parameterFragment parameterName="allClickCount" />
+    <textFragment>
+      uses, the button was clicked several times. The average waiting time between two subsequent
+      clicks is
+    </textFragment>
+    <parameterFragment parameterName="averageWaitingTime" />
+    <textFragment>
+      seconds. This is typical user behavior if the user does not see progress following his
+      actions. Please consider showing the user some progress after he performed the
+      first click. This is especially important if the operation triggered with the click usually
+      takes longer than one second. This defect was observed based on task
+    </textFragment>
+    <parameterFragment parameterName="task" />
+    <textFragment>
+      .
+    </textFragment>
+  </defectDescription>
+  
+  <defectDescription defectId="UNUSED_GUI_ELEMENTS" briefText="unused GUI elements">
+    <parameterFragment parameterName="ratio" />
+    <textFragment>
+      % of the GUI elements (
+    </textFragment>
+    <parameterFragment parameterName="noOfUnused" />
+    <textFragment>
+      of
+    </textFragment>
+    <parameterFragment parameterName="noOfAll" />
+    <textFragment>
+      ) are not used. This can have several reasons. Either they are not
+      visible to the user or they are not required. If they are important, they may not be
+      recognized by the user. This can be caused by visual design or because they are too hidden.
+      If they are less important, they can either be removed from the GUI or relocated to a less
+      prominent position. The unused GUI elements are:
+    </textFragment>
+    <parameterFragment parameterName="unusedGuiElements" />
+  </defectDescription>
 </defectDescriptions>
