Roger A. Grice

A discussion of modes and motives for usability evaluation

The evaluation purposes that can be served at various stages in the development of a document are analyzed. Three testing modes-exploring, verifying, and comparing-are discussed, and their use with various forms of evaluation and feedback modes is examined. The generalization of evaluation findings and the need to make evaluation an integral part of document development are discussed. >

Issues concerning the development and use of online information

Permission to copy without fee all or part of this material is granted provided that the copies are not made or distributed for direct commercial advantage, the ACM copyright notice and the title of the publication and its date appear, and notice is given that copying is by permission of the Association for Computing Machinery. To copy otherwise, or to republish, requires a fee and /o r specific permission.

From the guest editors the growing importance of computer documentation

Producing computer documentation today involves more than just writing. Todays computer documentation specialists must draw on a wide range of multidisciplinary skills to produce an effective documentation package. Beyond knowledge of the underlying computer technology and the necessary writing skills, they must also draw upon pertinent concepts from marketing, user psychology, graphic design, screen design, usability testing, and the product development cycle.

Use of format models and generic outlines to develop source material

This paper describes how format models and generic outlines were used to produce macro and system logic descriptions for the first release of IBMs Distributed Processing Programming Executive (DPPX) during the systems development. Because models and outlines were created and adopted early in the systems development cycle and because project control of both the information and information-developing process were enforced, initial documentation available to system developers was in the same format and of the same quality as the descriptions made available to users after the system was released. The process resulted in higher quality descriptions and less last-minute rework. Format models and generic outlines provide a standard description of how the system should be described. In the case of macros, the format model tells the developer how the macro will be described in customer publications and identifies the required information and information formats to be used in the macros initial description. Following the format ensures that all required information will be included in the initial descriptions of all system macros and that the descriptions of all the system macros will be in the form needed to produce the final descriptions. In the case of system logic descriptions, the generic outline helps ensure that all areas of the system are described in a complete, consistent manner and that there is as little overlap as possible in the systems descriptions. Generic outlines and format models help ensure that: • Source material will adhere to a specified format. • Developers can produce better source material with less effort. • Less rewriting is required to convert the source material to final copy. • Less review is required to ensure accuracy of the final copy. • Developers have final-quality information for their own use. • Drafts for review can be produced more quickly and more easily. When a new macro or system component is approved for inclusion in the system, its description is added to the projects internal information data base. The description is modified, if necessary, to fit the required format and is placed in the data base and an entry for it is placed in the data bases table of contents. The description is then available for review, use, and update by all members of the project.