|
 |
 |
CHAPTER 11 user support
|
 |
 |
 |
- Users have different requirements for support at different times.
- User support should be:
- available but unobtrusive
- accurate and robust
- consistent and flexible.
- User support comes in a number of styles:
- command-based methods
- context-sensitive help
- tutorial help
- online documentation
- wizards and assistants
- adaptive help.
- Design of user support must take account of:
- presentation issues
- implementation issues.
|
|