Go to start of metadata
- Created by Robert Reiner, last modified on 09. Oct 2019
A monograph of at least 49 pages (according to the UNESCO definition). A book may have different forms, but in this definition is required to be readable.
Description
A book is a written monograph of at least 49 pages. This is according to the UNESCO definition.
A book may have different forms, but in this definition is required to be readable. It is a hint for potential readers which equipment and environment is required to access the information contained in the book. Therefore audio books are not considered as books. Without a playing device and earphones it cannot be consumed at a working place without annoying team members.
There is no distinction between hard- or soft covered books or e-books. Nowadays most libraries have access to non-electronical and electronical versions. Some books may be readable online with a browser. Add a reference to each accessible form to the location property of the resource type.
Resources of this Type
| Name | Short Description |
|---|---|
| APIs: A Strategy Guide | While targeting on building a strategy for an API from a management point of view, this book also provides a chapter on documentation issues in the context of creating and selling an API. |
| Conversation and Community | Experiment with social media, social networking, and social relevance. |
| Developing Quality Technical Information | A Handbook for Writers and Editors - Direct from IBM's own documentation experts, this is the definitive guide to developing outstanding technical documentation--for the Web and for print. Using extensive before-and-after examples, illustrations, and checklists, the authors show exactly how to create documentation that's easy to find, understand, and use. This edition includes extensive new coverage of topic-based information, simplifying search and retrievability, internationalization, visual effectiveness, and much more. |
| DITA Best Practices | A Roadmap for Writing, Editing, and Architecting in DITA. |
| Information Architecture for the World Wide Web | The post-Ajaxian Web 2.0 world of wikis, folksonomies, and mashups makes well-planned information architecture even more essential. How do you present large volumes of information to people who need to find what they're looking for quickly? This classic primer shows information architects, designers, and web site developers how to build large-scale and maintainable web sites that are appealing and easy to navigate. |
| Information Architecture for the World Wide Web | The post-Ajaxian Web 2.0 world of wikis, folksonomies, and mashups makes well-planned information architecture even more essential. How do you present large volumes of information to people who need to find what they're looking for quickly? This classic primer shows information architects, designers, and web site developers how to build large-scale and maintainable web sites that are appealing and easy to navigate. |
| Object Design: Roles, Responsibilities, and Collaborations | Working within this conceptual framework, Rebecca Wirfs-Brock and Alan McKean present how user requirements, system architecture, and design patterns all contribute to the design of an effective object model. They introduce a rich vocabulary that designers can use to discuss aspects of their designs, discuss design trade-offs, and offer practical guidelines for enhancing the reliability and flexibility of applications. In addition, case studies and real-world examples demonstrate how the principles and techniques of Responsibility-Driven Design apply to real-world software designs. |
| Read Me First! A Style Guide for the Computer Industry | The definitive reference for technical writers, editors, and documentation managers, Read Me First! A Style Guide for the Computer Industry, Third Edition,has been revised and updated to cover everything from creating screencasts and referencing web sites to writing for wikis. |
| Reality is Broken | A book about Gamification: Why Games Make Us Better and How They Can Change the World. |
| Single Sourcing - Building Modular Documentation | Introduction to modular documentation. |
| Software Architekturen dokumentieren und kommunizieren | Great information on actually document software systems in an agile way. Currently only available in German. |
| The Insider's Guide to Technical Writing | Every complex product needs to be explained to its users, and technical writers, also known as technical communicators, are the ones who do that job. A growing field, technical writing requires multiple skills, including an understanding of technology, writing ability, and great people skills. |
| The Passionate Programmer | This book is about creating a remarkable career in software development. In most cases, remarkable careers don’t come by chance. They require thought, intention, action, and a willingness to change course when you’ve made mistakes. Most of us have been stumbling around letting our careers take us where they may. It’s time to take control. |
| Use Cases: Requirements in Context | The book shows how to create and evolve use cases. |
