Title: Telling stories
Subtitle: a short path to writing better software requirements
First published: 2009
Description: From System Designers to Top Management, Everyone loves a good story   Once upon a time, it was well understood that stories teach better than plain facts. Why then are most software requirements documents a baffling hodge-podge of diagrams, data dictionaries, and bullet points, held together by little more than a name and a staple? Telling Stories teaches you to combine proven standards of requirements analysis with the most ancient and effective tool for sharing information, the narrative. Telling Stories simplifies and refines the classic methods of Structured Analysis, providing organization, design, and old-fashioned writing advice. Whether you?re just getting started or an experienced requirements writer, Telling Stories can help you turn dull, detailed material into an engaging, logical, and readable story, a story that can make the difference for your project and your career.    Learn why readers believe and remember what they learn from stories  Work with team members to gather content, tell their stories, and win their support  Use stories to find every requirement  Create diagrams that almost tell the story on their own (while looking clear and professional)  Explain everything important about a process  Use precise language to remove the ambiguity from requirements  Write a forceful executive summary that stands on its own and sells a project to senior management  Summarize often to keep the reader focused on key issues  Structure the document so every part has a clear place and purpose
Subjects: Development, Technical writing, Computer software, Computer Technology, Nonfiction
LC classification: QA76.76.D47 R57 2009