Abstract

The documentation describing a technical project or product frequently takes one of two forms: too little documentation to present the necessary information properly, or too much documentation poorly organized and poorly written. To help overcome this problem, a four-level approach to project documentation is described, with documents assigned to each level according to their intended use. The technical writer can then judge how to construct a given document because the audience for each documentation level is clearly defined.