Single Sourcing: Building Modular Documentation [Englisch] [Taschenbuch]

"Single Sourcing: Building Modular Documentation" provides a clear and concise introduction to building modular documentation. The book is divided into five parts.

Chapter 1 "About single sourcing" introduces the concepts of single sourcing including the reasons, benefits, types, and what makes single sourcing successful.

Chapter 2 "Building documents" gets right into the heart of the subject by providing a 10 step process for building modular documentation including how to identify, label, organize, build, and edit modules then build documents from your modules. He also emphasizes the importance of developing guidelines for authors to follow.

Chapter 3 "Structuring content" provides guidelines on creating structured content. Guidelines are provided for such common content types as procedures, glossaries, examples, indexes, notes, troubleshooting scenarios, and many more.

Chapter 4, "Configuring Language" emphasizes that good modular content is more than just "chunks" of information; it is well written content. This chapter provides guidelines for developing consistent standards for writing content such as abbreviations, capitalization, punctuation, tense, and voice.

Chapter 5, "Leveraging technology" provides an introduction to how you can use technology to support your single sourcing effort.

What I like best about "Single Sourcing: Building Modular Documentation" is that Ament practices what he preaches; the content is highly modular, consistently structured, and full of examples. He provides examples of common content and how the content could be changed to reflect the concepts he presents. The book is an easy read and is chock full of tips and guidelines.

"Single Sourcing: Building Modular Documentation" provides an excellent resource for creators of single source technical documentation.

I was trained in Information Mapping® in 2000 and have used the principles to excellent advantage since then. More importantly, those techniques - called 'single sourcing' in this book - foster the ability to create coherent documentation using geographically distributed teams. This is because the single sourcing technique described in this book is concerned with document design, which is based on a process that identifies requirements and bases the initial draft on procedures and knowledge instead of the more common approach of writing an ad hoc outline.

At the heart of the author's single sourcing approach is a concept called 'chunking' - grouping information into manageable chunks - and factors such as relevance and consistency. When these are employed the cost-effectiveness of the method becomes apparent for two reasons:

(1) Documents written by teams are consistent and developed using a set process.
(2) Components within the documents - blocks - can be reused in other documents because they will address a specific, relevant topic (a chunk).

What I like about this book is the fact that it makes Information Mapping® available to anyone who will take the time to read this book and apply the principles. I also like way it offers an off-the-shelf solution to any company that wants to implement a cost-effective, highly efficient documentation standard that supports readable documentation that can be used instead of 'shelfware'.

The best way to learn about this book is to visit the official Information Mapping® site (ASIN B0000B01VZ) upon which many of the principles in this book are based. What you will discover there will give you a reasonable idea about what to expect from the approach in this book. If you are a technical writer who works with software architecture I also recommend that you read "Documenting Software Architectures: Views and Beyond" (ISBN 0201703726) because the approach in that book is consistent with both the "Single Sourcing" approach, as well as Information Mapping®.

Ament covers the issues -- step by step -- that many others only discuss. He lays out a simple roadmap, complete with real world examples that have worked -- or not worked -- for his clients.

In Chapter 1 (About Single Sourcing), he carefully defines "single sourcing" and explains related concepts (reusable content, modular writing, and assembled documents) in ways that are easy to understand and free of techno-jargon. And, he does us all a big favor by addressing the negatives associated with using technology to assemble documents by explaining that it actually takes more creativity to write content that can fit into multiple media, for multiple audiences, than it does to continually rewrite information over and over again each time it is needed.

Chapter 2 (Building Documents) and Chapter 3 (Structuring Content) are of particular value to those seeking to understand the shift in thinking required to master single sourcing. Writers, programmers and managers will all benefit from these chapters. Each chapter is packed full of tips and examples you can begin using today!

Chapter 4 (Configuring Language) explains how to "configure" your writing to support and increase usability while Chapter 5 (Leveraging Technology) touches on issues including conditional text, conventions, localization, translation, variables and more. As are the previous chapters, Chapter 5 is written in clear, concise language and is not a chapter business types should skip. In fact, it's just the opposite. Managers and decision makers need to understand the concepts explained in this chapter because many of the benefits a single source strategy can deliver are made possible by combining good planning with the right technology. And, while this chapter is certainly not about selecting software tools, the author helps his readers understand some of the issues they will need to understand as they begin thinking about their strategy and the types of functionality they'll need to support with the tools they select.

What I like most about "Single Sourcing" is that Ament went straight for the meat of the issues. He doesn't belabor points or confuse the reader by jumping back and forth from subject to subject (as so many poorly written IT-related books do). Instead, he supplies us with a book you can read in an afternoon and use the information contained within the next day at work.

But, be forewarned. You're going to want your sticky notes and your highlighting markers nearby. Chances are you'll be using them a lot!