Building a Better ReadMe
Surveys and focus groups show that most software buyers use ReadMe files. Users primarily look to ReadMe files for information on software bugs. They identify the following ways that software manufacturers can improve their ReadMe files: 1) keep them short, 2) include a table of contents, 3) use hypertext, and 4) eliminate the need for ReadMe files. Along with these four improvements, this article discusses other ways to create quality ReadMe files that meet concrete user needs.
No Supplementary Data
No Article Media
Document Type: Research Article
Publication date: February 1, 1997
More about this publication?
- Technical Communication, the Society's journal, publishes articles about the practical application of technical communication theory and serves as a common arena for discussion by practitioners. Technical Communication includes both quantitative and qualitative research while showcasing the work of some of the field's most noteworthy writers. Among its most popular features are the helpful book reviews. Technical Communication is published quarterly and is free with membership.
- Information for Authors
- Subscribe to this Title
- Membership Information
- Ingenta Connect is not responsible for the content or availability of external websites