Descriptor
Source
| Technical Communication | 5 |
Publication Type
| Journal Articles | 5 |
| Opinion Papers | 2 |
| Guides - Non-Classroom | 1 |
| Reference Materials -… | 1 |
| Reports - General | 1 |
| Reports - Research | 1 |
Education Level
Audience
Location
Laws, Policies, & Programs
Assessments and Surveys
What Works Clearinghouse Rating
Peer reviewedSides, Charles H. – Technical Communication, 1988
Offers a selective bibliography, covering the last 25 years, of articles on how to write instructions for using computers. Contains sections on planning computer documentation, computer manuals, and online documentation. (JAD)
Descriptors: Annotated Bibliographies, Computer Software, Technical Writing
Peer reviewedConklin, James – Technical Communication, 1993
Argues that the development of software documentation should be fully integrated with the overall development of new software products. Suggests that, when technical communicators become full members of the development team, they will not cease to communicate but will be able to add communications value to the product as well as to the…
Descriptors: Computer Software, Computer Software Development, Integrated Activities, Technical Writing
Peer reviewedHorton, William – Technical Communication, 1993
Presents a 10-step procedure for selecting the computer software needed to author and deliver online documentation. (SR)
Descriptors: Computer Software, Computer Software Selection, Decision Making, Models
Peer reviewedHorton, William – Technical Communication, 1993
Notes that many companies want to reduce paper documentation necessary to support their products. Maintains that, if technical communicators are to avoid being downsized out of a job, they must build on their existing communication skills and move toward product design, helping to produce products so obvious that they need no manuals. (SR)
Descriptors: Career Change, Computer Software, Computer Software Development, Organizational Change
Peer reviewedSkelton, T. M. – Technical Communication, 1992
Argues that traditional methods of testing software products leave too little time for major modifications and that in-cycle usability testing is required. Reports a study of environmental factors that constrain such testing. Concludes that it is not yet routine because of budget and staff limitations, lack of performance standards, and untrained…
Descriptors: Computer Software, Computer Software Development, Computer Software Evaluation, Computer Software Reviews


