Daily-Use Scenarios: Unterschied zwischen den Versionen
K |
|||
| Zeile 2: | Zeile 2: | ||
In daily-use scenarios you can find out which features of the programme will be used most frequently. | In daily-use scenarios you can find out which features of the programme will be used most frequently. | ||
| − | If you work with [[ | + | If you work with [[Personas|personas]], you will start to imagine their every-day tasks. A secretary for example will enter her office every day at 8.30 am and turn on the computer first to check her e-Mail and the calendar. |
This feature should be presented foremost in the interface. | This feature should be presented foremost in the interface. | ||
Version vom 16. August 2005, 16:01 Uhr
A daily-use scenario is used in the pre-production phase of the production phases of a software.
In daily-use scenarios you can find out which features of the programme will be used most frequently. If you work with personas, you will start to imagine their every-day tasks. A secretary for example will enter her office every day at 8.30 am and turn on the computer first to check her e-Mail and the calendar. This feature should be presented foremost in the interface.
Other features that will not be used that frequently (see necessary-use scenarios) like reserving a room or an institute's car, can be a less obvious part of the programme. It is not necessary to provide all possible functions visible for the user.
The functions that are used sometimes can be hidden away, but the most used information and functions should be in a place that is easily accessible and visible for the user.
