References to interesting publications on documentation, team collaboration, and software development.
Name | Short Description | Authors | Publication Date |
---|---|---|---|
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. | Daniel Jacobson, Greg Brail, Dan Woods | 2011 |
DITA Best Practices | A Roadmap for Writing, Editing, and Architecting in DITA. | Laura Bellamy, Michelle Carey, Jenifer Schlotfeldt | 2012 |
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. | Rebecca Wirfs-Brock, Alan McKean | 2003 |
Reality is Broken | A book about Gamification: Why Games Make Us Better and How They Can Change the World. | Jane McGonigal | 2011 |
Single Sourcing - Building Modular Documentation | Introduction to modular documentation. | Kurt Ament | 2003 |
Software Architekturen dokumentieren und kommunizieren | Great information on actually document software systems in an agile way. Currently only available in German. | Stefan Zörner | 2012 |
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. | Chad Fowler | 2009 |
Use Cases: Requirements in Context | The book shows how to create and evolve use cases. | Daryl Kulak, Eamonn Guiney | 2000 |
Wer hat Angst vor dem Betrieb? | An introduction into using roles and stakeholders in documentation (in German). | Uwe Friedrichsen | 2010 |