Every software project eventually arrives at the same uncomfortable moment: the product is built, the deadline is looming, and someone looks up from their keyboard and says, "Oh — we'll need a manual." What follows is usually a disaster. A programmer's technical notes get processed through a word processor, repackaged with a title page, and handed to users who flip through it once, set it on a shelf, and never touch it again. The software fails not because it doesn't work, but because nobody can figure out how to use it.
Software User Documentation is the guide that prevents that outcome.
Written by Dr David Tuffley — senior lecturer in sociotechnical studies at Griffith University and a technical writer with decades of experience in both the Australian public service and the private sector — this compact, authoritative manual covers the entire documentation lifecycle from initial planning through to post-publication maintenance. It is grounded in IEEE Standard 1063, the internationally recognised benchmark for software user documentation, and it delivers that standard's wisdom in precisely the kind of clear, accessible prose it advocates.
The book opens with a bracing diagnosis: the computer industry has a documentation problem, and users are the ones who pay for it. The gap between a programmer's internal world and the everyday user's experience is not a technical problem — it is a communication problem. Bridging that gap requires a specific discipline, a specific method, and a specific set of skills. This book provides all three.
From the earliest chapters on preparation — how to gather source material, construct a documentation project plan, estimate time and resources, and profile your audience — to the nuanced craft of clear writing (active voice, present tense, short words over long ones, no tired clichés), the guide moves methodically through every stage of the process. Readers learn what makes first drafts work, how to structure a document so that users can find what they need without frustration, and how to handle error messages, appendixes, glossaries, and indexes in ways that serve rather than confuse.
There is practical wisdom here that textbooks rarely touch: how to survive writer's block, how to set up an ergonomic workspace, when to print a draft rather than edit on screen. The chapters on editing and proof-reading are meticulous without being pedantic, and the guidance on reviewing and field-testing manuals — who should do it, how to brief them, how to act on their feedback — reflects the hard-won experience of someone who has managed real documentation projects under real deadline pressure.
The final sections address online help systems, production and binding, version control, and the often-neglected art of document maintenance after publication. A comprehensive glossary of computer terms and a set of ready-to-use project forms round out the package.
What distinguishes this book from the narrow technical writing manuals that crowd the shelf is its insistence that good documentation is, at its heart, an act of translation — from the world of the machine into the world of the person sitting in front of it. Get that translation right, and users succeed. Get it wrong, and even brilliant software becomes shelfware.
If you write, commission, review, or manage software documentation — or if you simply want users to actually use what you build — this book belongs on your desk, not your shelf.
"synopsis" may belong to another edition of this title.
David Tuffley PhD is lecturer and researcher at Griffith University in Australia. David is a Software Engineer, though his interests range across Comparative Religion, Philosophy, Psychology, Anthropology, Literature, History, Design and Architecture. David has been an academic since 1999. For 15 years before academia David was a technical writer and later a consultant for public and private sector IT clients in Australia and the United Kingdom. He combines theory and practice in a focussed and disciplined way that has proved effective for solving problems for clients.
"About this title" may belong to another edition of this title.
Seller: GreatBookPrices, Columbia, MD, U.S.A.
Condition: As New. Unread book in perfect condition. Seller Inventory # 20947769
Seller: GreatBookPrices, Columbia, MD, U.S.A.
Condition: New. Seller Inventory # 20947769-n
Seller: PBShop.store US, Wood Dale, IL, U.S.A.
PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Seller Inventory # L0-9781461133377
Seller: California Books, Miami, FL, U.S.A.
Condition: New. Print on Demand. Seller Inventory # I-9781461133377
Seller: PBShop.store UK, Fairford, GLOS, United Kingdom
PAP. Condition: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Seller Inventory # L0-9781461133377
Quantity: Over 20 available
Seller: Ria Christie Collections, Uxbridge, United Kingdom
Condition: New. In. Seller Inventory # ria9781461133377_new
Quantity: Over 20 available
Seller: GreatBookPricesUK, Woodford Green, United Kingdom
Condition: New. Seller Inventory # 20947769-n
Quantity: Over 20 available
Seller: THE SAINT BOOKSTORE, Southport, United Kingdom
Paperback / softback. Condition: New. This item is printed on demand. New copy - Usually dispatched within 5-9 working days. Seller Inventory # C9781461133377
Quantity: Over 20 available
Seller: GreatBookPricesUK, Woodford Green, United Kingdom
Condition: As New. Unread book in perfect condition. Seller Inventory # 20947769
Quantity: Over 20 available
Seller: CitiRetail, Stevenage, United Kingdom
Paperback. Condition: new. Paperback. I N T R O D U C T I O NGood manuals are a scarce commodity - expensive to produce, difficult to maintain, the province of experts. Not any more. With this new step-by-step guide you can produce successful manuals at a fraction of the normal cost. Software user Documentation: A How To Guide for Project Staff is a detailed reference guide to the preparation of effective user documentation for computer software applica-tions. It is intended for people who wish to develop software user documentation. The format and arrangement of this manual re-flects the principles outlined within it - it 'practices what it preaches'.No prior knowledge or experience of user documentation writ-ing is assumed. The manual is designed to equip a person with at least average written expression skills with a blueprint of how to prepare a software user manual. Provided the person is prepared to follow the instructions through to completion, the result will be an effective piece of documentation. It can be used by practicing user documenters and technical writers as a checklist of what to include in a piece of documen-tation. The information given in this manual conforms with the interna-tionally recognised IEEE Standard 1063 which relates to the requirements for software user documentation. S O W H A T M A K E S A N E F F E C T I V E M A N U A L ?Organisation - Good manuals are well-structured with comprehensive table of contents and index.Content - The material focuses on user tasks, provides clear instructions and is concise.Appearance - The presentation is attractive with plenty of white space, and are packaged in booklets that are easy to use.Language - The text is easy to read and aimed specifically at the users.What to Avoid - Users dislike manuals that are: inaccurate, contain too much detail, talks down to people, is too formal, is poorly presented and/or organised. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability. Seller Inventory # 9781461133377
Quantity: 1 available