Daily-Use Scenarios: Unterschied zwischen den Versionen
| Zeile 1: | Zeile 1: | ||
[[category:Software]] | [[category:Software]] | ||
| − | A daily-use scenario is used in the [[The_Inmates_are_Running_the_Asylum#Pre-Production_Phase|pre-production phase]] of the software production. | + | A daily-use scenario is used in the [[The_Inmates_are_Running_the_Asylum (Buchbesprechung)#Pre-Production_Phase|pre-production phase]] of the software production. |
In daily-use scenarios you can find out which features of the program will be used most frequently. | In daily-use scenarios you can find out which features of the program will be used most frequently. | ||
Version vom 6. März 2006, 14:52 Uhr
A daily-use scenario is used in the pre-production phase of the software production.
In daily-use scenarios you can find out which features of the program 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. These features should be presented foremost in the program 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 program. It is not necessary to provide all possible functions visible for the user.
The functions that are used rarely can be hidden away, but the most frequently used information and functions should be in a place that is easily accessible and visible for the user.
