Features
- Cover Type: Paperback with 384 pages
- Published by: Microsoft Press June 13, 2007
- Written in: English
- ISBN 10 Number: 0735623988
- ISBN 13 Number: 978-0735623989
-
Book Dimensions:
8.8 x 7.2 x 1.3 inches
- Weighs: 1.7 pounds
Product Description
Learn proven, real-world techniques for specifying
software requirements with this practical reference. It details thirty requirement "patterns" offering realistic examples for situation-specific guidance for building effective
software requirements. Each pattern explains what a requirement requirements to convey, offers potential questions to ask, points out potential pitfalls, suggests extra requirements, and other advice. This book also provides guidance on how to write other kinds of information that belong in a requirements specification, such as assumptions, a glossary, and document history and references, and how to structure a requirements specification.
A disturbing proportion of computer systems are judged to be inadequate; many are not even delivered; more are late or over budget. Studies consistently show one of the single biggest causes is poorly defined requirements: not properly defining what a system is for and what it's supposed to do. Even a modest contribution to improving requirements offers the prospect of saving businesses part of a large sum of wasted investment. This guide emphasizes this important requirement need--determining what a
software system requirements to do before spending time on development. Expertly written, this book details solutions that have worked in the past, with guidance for modifying patterns to fit individual needs--giving developers the valuable advice they need for building effective
software requirements
Publisher Description
Key Book Benefits:
-Provides a reference to solutions that have worked in the past, with guidance about how to modify patterns to fit individual needs
-Features an emphasis on determining what a
software system requirements to do--the necessary precursor to development
Reader ReviewsStephen Withall's "Software Requirement Patterns" can help any analyst write better requirements. The patterns Steve presents can help analysts ask the right questions to properly understand and specify requirements of many types at an appropriate level of detail. This book communicates a wealth of wisdom and insight for writing stellar requirements. The patterns point out the value of using a consistent style when exploring and documenting requirements. Even if you don't apply the patterns rigorously, Steve provides hundreds of practical tips for specifying better requirements. This book does not address the entire requirements development and management life cycle. You aren't going to sit down and read through the whole book, either. Instead, it's a valuable reference when you have questions about how best to explore and specify certain types of requirements. It will help you discover essential information that you wouldn't otherwise think to ask about. I used the "Report Requirement Pattern" this morning (literally) to get some new ideas about effectively specifying requirements for reports. This is the most comprehensive resource I've seen on thinking carefully through the information associated with effective functional, data, and quality requirements of many different kinds. I highly recommend it.