Changes between Version 49 and Version 50 of CoreLibrary/UsabilityAnalysis


Ignore:
Timestamp:
10/25/12 14:29:51 (12 years ago)
Author:
pharms
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CoreLibrary/UsabilityAnalysis

    v49 v50  
    1414The input for generating task trees in AutoQUEST are sequences of elementary actions. Those can be manually defined or recorded using the monitors provided by AutoQUEST. AutoQUEST then combines actions that logically belong together into tasks. For example, it creates a task for all actions that took place in the same panel of a GUI. In a next step, AutoQUEST identifies iterations of tasks. Finally, AutoQUEST identifies selections between different tasks that a user can choose from at a specific point of using a software. The result is a condensed task tree, that shows all possible action combinations. 
    1515 
    16 The task tree model is not fully correct, as the analysed sequences do not contain all possible interactions. However, it provides sufficient information to perform a usability analysis for the concrete interaction sequence that was analysed. 
     16The task tree model is not fully correct, as the analysed sequences do not contain all possible actions. However, it provides sufficient information to perform a usability analysis for the concrete action sequence that was analysed. 
    1717 
    1818== Generating Interface Models ==