10 | | In software development processes, the users and their tasks should analysed to derive requirements for the software |
| 10 | Usability should be considered throughout the whole software development process. For this, a broad variety of methods exists that can be used at distinct stages of the process. Applying such methods in the development process is referred to as usability engineering. |
| 11 | |
| 12 | Most of the methods of usability engineering rely on a proper analysis of the application context. With an increasing size of the application context, such as a larger number of different users, the analysis becomes imprecise. This causes a decrease of the achievable usability for the individual user or a group of users. Furthermore, the users that are actually using the software as well as their way of using the software may differ from the expectations of an initial user analysis. This is because users very often use software also for tasks, for which is was not implemented. As an example, many posters nowadays are created using tools for screen presentations or writing documents as poster software is either rare or expensive. |
| 13 | |
| 14 | = AutoQUEST and Usability Analysis = |
| 15 | |
| 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. |
| 17 | |