In 1951, when a school of information science was first established, Briet was the founding Director of Studies. She became Vice President of the International Federation for Documentation (FID) and acquired the nickname 'Madame Documentation.' This book relates her fascinating story and includes the first English translation of Briet's manifesto on the nature of documentation, a 48-page pamphlet, which sought to push the boundaries of the field beyond texts to include any material form of evidence. It also argued that a new and distinct profession was emerging and urged the societal need for new and active documentary services. Due to its continuing relevance towards understanding the nature, scope, and societal impacts of documents and documentation, Briet's modernist perspective, combined with semiotics, still deserves attention because it offers a sturdy and insightful alternative to the scientific, positivist view that has so dominated information science and which is increasingly being questioned.
Looking for a way to invigorate your technical writing team and grow that expertise to include developers, designers, and writers of all backgrounds? When you treat docs like code, you multiply everyone's efforts and streamline processes through collaboration, automation, and innovation. Second edition now available with updates and more information about version control for documents and continuous publishing.
Documentation has always been crucial in human society. Today almost all communication are being stored digitally. In order to deal systematically and coherently with old and new media in the world today, you have to deal with the physical as well as the social and cultural context. Alongside this, there is now increasing interest in documentation theory and science, and documentation studies has become a distinctly lively field of research as well as a basis for professional practice in libraries, archives and museums. This groundbreaking new book introduces and demonstrates the value and relevance of a new approach to the documentation, communication and information field, complementary to the traditional library, information and archival sciences. It offers an introduction to documentation studies - a new discipline within the overall information studies umbrella - and gives a broad and general theory for documentation. It outlines the historical background and the theoretical foundation for the discipline by giving insight into documentation issues and processes from early modern society to today's digital age: not only in the context of academic study, but also in the practice of documentation, both in everyday life and in professional life. Key topics covered include: Human life in a documentation perspective Documentation in theory Documentation: a conceptual history A complementary theory of documentation A model for documentation analysis Documentation in practice: 6 case studies Documentation in society The science and profession of documentation. This unique text outlines the main scientific purpose and objective of the science of documentation; to study documentation in society. It also describes the main skills for a documentalist in the 21st century; to be able to select, collect and make accessible all documentation of possible interest for the general public as well as research. This book will be pivotal reading for students (advanced undergraduate and graduate), researchers, and faculty in library science, information science, records management, publishing, media studies, cultural studies, archival studies, and information systems. It will also be of interest to thoughtful professionals in libraries, archives, records and media. 010
Use an Approach Inspired by Domain-Driven Design to Build Documentation That Evolves to Maximize Value Throughout Your Development Lifecycle Software documentation can come to life, stay dynamic, and actually help you build better software. Writing for developers, coding architects, and other software professionals, Living Documentation shows how to create documentation that evolves throughout your entire design and development lifecycle. Through patterns, clarifying illustrations, and concrete examples, Cyrille Martraire demonstrates how to use well-crafted artifacts and automation to dramatically improve the value of documentation at minimal extra cost. Whatever your domain, language, or technologies, you don't have to choose between working software and comprehensive, high-quality documentation: you can have both. · Extract and augment available knowledge, and make it useful through living curation · Automate the creation of documentation and diagrams that evolve as knowledge changes · Use development tools to refactor documentation · Leverage documentation to improve software designs · Introduce living documentation to new and legacy environments
Software documentation forms the basis for all communication relating to a software project. To be truly effective and usable, it should be based on what needs to be known. Agile Documentation provides sound advice on how to produce lean and lightweight software documentation. It will be welcomed by all project team members who want to cut out the fat from this time consuming task. Guidance given in pattern form, easily digested and cross-referenced, provides solutions to common problems. Straightforward advice will help you to judge: What details should be left in and what left out When communication face-to-face would be better than paper or online How to adapt the documentation process to the requirements of individual projects and build in change How to organise documents and make them easily accessible When to use diagrams rather than text How to choose the right tools and techniques How documentation impacts the customer Better than offering pat answers or prescriptions, this book will help you to understand the elements and processes that can be found repeatedly in good project documentation and which can be shaped and designed to address your individual circumstance. The author uses real-world examples and utilises agile principles to provide an accessible, practical pattern-based guide which shows how to produce necessary and high quality documentation.
This book provides a broad perspective about the essential aspects of creating technical documentation in today's product development world. It is a book of opinions and guidance, collected as short essays. You can read selectively about subjects that interest you, or you can read the entire collection in any order you like. Information development is a multidimensional discipline, and it is easy to theorize. We have written this book from our direct experience, using the concrete insights and practices we apply to our work every day. If you work as an information developer, a manager in a documentation team, or in another part of product development that collaborates with a doc team, there is information in this book for you. Perhaps you are a technical writer in a small, high-growth company that is figuring out its processes. Perhaps you are an information-development manager in a large enterprise company with an expanding product line and an ever more complex matrix of cross-functional dependencies. You might work at a medium-sized company where your management is asking you to do more with fewer people, and you want some additional perspective that will help you find a leaner and more effective way to deliver what your business demands. Or you might work outside the technical documentation world, in another part of product development, and are wondering how to collaborate most effectively with the documentation team. The purpose of The Product is Docs is to provoke discussion, shine light on some murky areas, and--we hope--inspire our colleagues to consider their processes and assumptions with new eyes. -- Amazon.
The Art of Technical Documentation presents concepts, techniques, and practices in order to produce effective technical documentation. The book provides the definition of technical documentation; qualities of a good technical documentation; career paths and documentation management styles; precepts of technical documentation; practices for gathering information, understanding what you have gathered, and methods for testing documentation; and considerations of information representation, to provide insights on how different representations affect reader perception of your documents. Technical writers and scientists will find the book a good reference material.
Develop the skills you need to effectively and efficiently document patient care for children and adults in clinical and hospital settings. This handy guide uses sample notes, writing exercises, and EMR activities to make each concept crystal clear, including how to document history and physical exams and write SOAP notes and prescriptions.
This is a practical guide for software developers, and different than other software architecture books. Here's why: It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face. It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties. It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts. It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail. It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.
