|
In a typical project we gather information through:
 |
 |
|
| |
 |
One or more walkthroughs of the system, usually held at your offices. |
| |
 |
Access to an appointed member of your staff who understands how your system should be used by your end users. We would communicate with them regularly, usually by email and phone and by visiting them at either your offices or ours as necessary. We typically require 10 to 15 minutes per day of their time. |
| |
 |
A working copy of the system that we can load onto our computers or access through the Internet. |
| |
 |
Existing documentation such as system specifications and marketing/promotional literature. |
Prior to commencing the actual writing of a user guide, we will determine the intended target audience. We will discuss with you the level of computing experience your typical users have and the roles they carry out. Armed with this information we can then adopt a language style and assume a level of knowledge to suit.
The result of this research is end user documentation that meets your user's needs exactly. Our aim is to provide readers with the information they need without them having to read through text they don't!
|
 |
|