Changes between Version 43 and Version 44 of CoreLibrary/UsabilityAnalysis


Ignore:
Timestamp:
10/22/12 17:05:36 (12 years ago)
Author:
pharms
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CoreLibrary/UsabilityAnalysis

    v43 v44  
    1414= AutoQUEST and Usability Analysis = 
    1515 
    16 AutoQUEST is capable of recording users while using a software for their tasks. Based on this recording, AutoQUEST provides tools for usability analysis. At the first step, these tools determine a model of the usage of a software. This model is a task tree that combines the individual user interactions to logical units. Furthermore, AutoQUEST is able to determine a model of the GUI of the software. Based on both models, AutoQUEST is capable of performing a usability analysis of the software. As an example, a task tree may contain a regularly repeated list of user interactions specific elements of the GUI. For most effective support for the user, these GUI elements should be colocated. If they are colocated can be checked using the GUI model. 
     16AutoQUEST analyses the usability of a software for the users that are using it. For this, it records users while using a software for their tasks. Based on this recording, AutoQUEST provides tools for usability analysis. At the first step, these tools determine a model of the usage of a software. This model is a task tree that combines the individual user interactions to logical units. Furthermore, AutoQUEST is able to determine a model of the GUI of the software. Based on both models, AutoQUEST is capable of performing a usability analysis of the software. As an example, a task tree may contain a regularly repeated list of user interactions on specific elements of the GUI. For most effective support for the user, these GUI elements should be colocated. If they are colocated can be checked using the GUI model. 
    1717