Changes between Version 52 and Version 53 of CoreLibrary/UsabilityAnalysis

Timestamp:

10/21/14 17:57:08 (10 years ago)

Author:

pharms

Comment:

--

CoreLibrary/UsabilityAnalysis

@@ -12 +12 @@
 A task tree is a structure for a task that a user or another system performs with a software. It decomposes a task into subtasks, which can be further subdivided. Each task and its subtasks are represented as nodes in the task tree. The leaf nodes of a task tree represent the actions a user must perform to fulfill the overall task. The subtasks of a parent task are set into temporal relationship. This defines the order in which they must be executed to fulfill the parent task.
 
-The 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.
+The 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 are typically executed in the same combination. 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.
 
-The 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.
+The task tree model is not fully correct, as the analysed action 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.
 
 == Generating Interface Models ==