rent-now

Rent More, Save More! Use code: ECRENTAL

5% off 1 book, 7% off 2 books, 10% off 3+ books

9780131477490

Developing Quality Technical Information A Handbook for Writers and Editors

by ; ; ; ; ; ;
  • ISBN13:

    9780131477490

  • ISBN10:

    0131477498

  • Edition: 2nd
  • Format: Hardcover
  • Copyright: 2004-04-06
  • Publisher: IBM Press
  • View Upgraded Edition
  • Purchase Benefits
  • Free Shipping Icon Free Shipping On Orders Over $35!
    Your order must be $35 or more to qualify for free economy shipping. Bulk sales, PO's, Marketplace items, eBooks and apparel do not qualify for this offer.
  • eCampus.com Logo Get Rewarded for Ordering Your Textbooks! Enroll Now
List Price: $59.99

Summary

The book presents a much needed approach to quality technical communication and a working plan for achieving quality. The examples are excellent and are easy to use and adapt. The editorial advice is simple and clear enough for tech writers who did not major in English or journalism. It is most worthy of a text in university programs, but it is more valuable to experienced writers, editors and managers concerned with raising the quality of their publications. The main difference between this and other books is that in each of the first nine chapters, one quality characteristic is presented that you can apply to your writing project to make technical information easy to use, easy to understand and easy to find. There are checklists at the end of each chapter for review and a Quality checklist in the appendix covering all of the characteristics. The book shows original text and revision text so that you can actually browse the book and see the differences applied. This is another excellent feature that should catch a purchaser's eye.

Author Biography

The authors have served on the Editing Council at IBM Silicon Valley Laboratory in San Jose, California, an organization dedicated to excellence in technical information. Gretchen Hargis is a technical manager at IBM for a group that provides user assistance and user-centered design for application development tools. She was a technical editor and writer and a pioneer of IBM Darwin Information Typing Architecture (DITA). Michelle Carey is a technical writer at IBM and a technical writing instructor at University of California Santa Cruz Extension. She is an expert on topic-based information systems and on writing for international audiences. Ann Kilty Hernandez is a technical editor at IBM and has been a technical writer, manager, and marketing specialist. She was a co-author of An Introduction to DB2 for OS/390 and contributed to its next edition, The Official Guide to DB2 UDB for z/OS. Polly Hughes, now retired from IBM, worked as a visual designer for technical information and software interfaces and as a technical writer. Deirdre Longo is a technical editor and writer at IBM who edits product interfaces and writes customer information, mostly for content management products. Shannon Rouiller is a technical editor at IBM who has written and edited topicbased information systems, books, contextual help, wizards, and interfaces for products that are marketed worldwide. She co-authored Designing Effective Wizards. Elizabeth Wilde is a technical editor at IBM and a leader in developing quality metrics and quality assurance processes for technical documentation. She also educates writers and editors throughout IBM on developing user-centered information.

Table of Contents

Contentsp. iii
Welcomep. xi
Is this book for you?p. xi
How to use this bookp. xii
Conventions used in this bookp. xii
Changes in this editionp. xiii
Acknowledgmentsp. xv
Quality technical informationp. 1
What is quality technical information?p. 3
Relationships among the quality characteristicsp. 4
Order of the groupsp. 4
Quality characteristics compared with elements and guidelinesp. 5
Other possible quality characteristics of technical informationp. 6
Using the quality characteristics to develop quality technical informationp. 7
Preparing to write: understanding users, tasks, and the productp. 8
Writing and rewritingp. 9
Reviewing, testing, and evaluating technical informationp. 10
Writing task, concept, and reference topicsp. 10
Establishing a unit of reusep. 11
Restructuring technical informationp. 12
Easy to usep. 15
Task orientationp. 17
Write for the intended audiencep. 19
Present information from the user's point of viewp. 20
Indicate a practical reason for informationp. 23
Relate details to a task where appropriatep. 23
Provide only a necessary amount of conceptual information in task topicsp. 24
Focus on real tasks, not product functionsp. 27
Use headings that reveal the tasksp. 31
Divide tasks into discrete subtasksp. 33
Provide clear, step-by-step instructionsp. 36
Make each step a clear action for users to takep. 36
Group steps for usabilityp. 38
Clearly identify optional stepsp. 41
Identify criteria at the beginning of conditional stepsp. 43
In sump. 45
Accuracyp. 47
Write information only when you understand it, and then verify itp. 49
Keep up with technical changesp. 53
Maintain consistency of all information about a subjectp. 58
Reuse information when possiblep. 60
Avoid introducing inconsistencies and eliminate those that you findp. 60
Use tools that automate checking for accuracyp. 67
Check the accuracy of references to related informationp. 69
In sump. 72
Completenessp. 75
Cover all topics that support users' tasks, and only those topicsp. 77
Cover each topic in just as much detail as users needp. 79
Include enough informationp. 82
Include only necessary informationp. 84
Use patterns of information to ensure proper coveragep. 90
Repeat information only when users will benefit from itp. 96
In sump. 99
Easy to understandp. 101
Clarityp. 103
Focus on the meaningp. 105
Avoid ambiguityp. 110
Use words with a clear meaningp. 110
Avoid vague referentsp. 113
Place modifiers appropriatelyp. 114
Avoid long strings of nounsp. 116
Write positivelyp. 118
Make the syntax of sentences clearp. 120
Keep elements shortp. 124
Remove roundabout expressions and needless repetitionp. 124
Choose direct wordsp. 127
Keep lists shortp. 129
Write cohesivelyp. 132
Present similar information in a similar wayp. 136
Use lists appropriatelyp. 136
Segment information into tablesp. 139
Use technical terms only if they are necessary and appropriatep. 141
Decide whether to use a termp. 141
Use terms consistentlyp. 142
Define each term that is new to the intended audiencep. 144
In sump. 146
Concretenessp. 149
Choose examples that are appropriate for the audience and subjectp. 152
Consider the level and needs of usersp. 152
Use examples appropriately in conceptual, task, and reference informationp. 154
Use focused, realistic, accurate, up-to-date examplesp. 160
Make examples easy to findp. 162
Use visual cues to indicate where examples arep. 162
Make examples part of the user interfacep. 163
Make clear where examples start and stopp. 163
Make code examples easy to adaptp. 166
Use scenarios to illustrate tasks and to provide overviewsp. 169
Set the context for examples and scenariosp. 172
Relate unfamiliar information to familiar informationp. 174
Use general language appropriatelyp. 176
In sump. 178
Stylep. 181
Use correct grammarp. 183
Check for sentence fragmentsp. 184
Correct pronoun problemsp. 185
Correct dangling modifiersp. 187
Use correct and consistent spellingp. 189
Use consistent and appropriate punctuationp. 191
Write with the appropriate tonep. 193
Use an active stylep. 196
Use active voicep. 196
Use the present tensep. 198
Use the appropriate moodp. 199
Follow template designs and use boilerplate textp. 200
Create and reuse templatesp. 200
Use boilerplate text to ensure inclusion of necessary informationp. 201
Create and follow style guidelinesp. 203
Provide practical and consistent highlightingp. 205
Present list items consistentlyp. 207
Use unbiased languagep. 208
In sump. 211
Easy to findp. 213
Organizationp. 215
Organize information into discrete topics by typep. 218
Organize tasks by order of usep. 222
Organize topics for quick retrievalp. 225
Separate contextual information from other types of informationp. 228
Organize information consistentlyp. 232
Provide an appropriate number of subentries for each branchp. 234
Emphasize main points; subordinate secondary pointsp. 236
Reveal how the pieces fit togetherp. 239
In sump. 243
Retrievabilityp. 245
Facilitate navigation and searchp. 247
Provide a complete and consistent indexp. 249
Use an appropriate level of detail in the table of contentsp. 254
Provide helpful entry pointsp. 257
Link appropriatelyp. 260
Design helpful linksp. 264
Ensure that a link describes the information that it links top. 264
In similar links and cross-references, emphasize the text that is differentp. 265
Minimize the effort that is needed to reach related informationp. 265
Avoid redundant linksp. 266
Make linked-to information easy to find in the target topicp. 268
In sump. 273
Visual effectivenessp. 277
Use graphics that are meaningful and appropriatep. 279
Illustrate significant conceptsp. 279
Avoid illustrating what is already visiblep. 280
Choose graphics that complement the textp. 284
Use visual elements for emphasisp. 288
Emphasize the appropriate informationp. 288
Ensure that your visual elements are not distractingp. 292
Use visual elements logically and consistentlyp. 295
Use a visually simple but distinct heading hierarchyp. 295
Maintain consistent placement of document elementsp. 297
Ensure that the look and feel of multimedia presentations is consistentp. 301
Use icons and symbols consistentlyp. 303
Balance the number and placement of visual elementsp. 304
Use visual cues to help users find what they needp. 307
Visually identify recurring alternatives or contextsp. 307
Ensure that visual cues are usable in all environmentsp. 309
Ensure that textual elements are legiblep. 311
Use a legible typeface and sizep. 311
Ensure that the text fits in the available spacep. 315
Ensure that the contrast between text and background is adequatep. 316
Use color and shading discreetly and appropriatelyp. 318
Ensure that all users can access the informationp. 323
In sump. 325
Putting it all togetherp. 329
Applying more than one quality characteristicp. 331
Applying quality characteristics to task informationp. 332
Applying quality characteristics to conceptual informationp. 337
Applying quality characteristics to reference informationp. 340
Applying quality characteristics to information for an international audiencep. 344
Applying quality characteristics to information on the Webp. 351
Revising technical informationp. 355
Reviewing, testing, and evaluating technical informationp. 357
Inspecting technical informationp. 358
Reading and using the informationp. 358
Finding problemsp. 359
Reporting problemsp. 360
Testing information for usabilityp. 361
Prototypingp. 362
Testing outside a usability laboratoryp. 362
Testing in a usability laboratoryp. 363
Testing technical informationp. 367
Using test toolsp. 368
Using test casesp. 368
Testing the user interfacep. 369
Editing and evaluating technical informationp. 370
Preparing to editp. 371
Getting an overviewp. 371
Reading and editing the informationp. 373
Looking for specific informationp. 376
Summarizing your findingsp. 376
Conferring with the writerp. 378
Reviewing the visual elementsp. 379
Preparing to reviewp. 380
Getting an overviewp. 380
Reviewing individual visual elementsp. 382
Summarizing your findingsp. 383
Conferring with the editor or writer or bothp. 384
Appendixesp. 385
Quality checklistp. 387
Who checks which quality characteristics?p. 391
Quality characteristics and elementsp. 397
Looking at the quality characteristicsp. 398
Looking at the elementsp. 398
Resources and referencesp. 401
Easy to usep. 401
Easy to understandp. 404
Easy to findp. 407
Putting it all togetherp. 409
Glossaryp. 413
Indexp. 425
Table of Contents provided by Ingram. All Rights Reserved.

Supplemental Materials

What is included with this book?

The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.

The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.

Rewards Program