10 of 10 people found the following review helpful
Most comprehensive book on the topic,
This review is from: Mastering the Requirements Process: Getting Requirements Right (Hardcover)
(And at 500 pages, so it should be!)
This book covers everything you wanted to know about requirements and a fair bit of stuff you didn't know--yet--that you needed. Whether you're building a large "documentation heavy" project or a lean agile one, you still need requirements. The template outlined in this book covers all aspects of requirements that you may need, but you don't need to fill them all out. If all you need are a few functional requirements and a few statements about look-and-feel, great! This book will tell you how best to establish what they are, identify people who have an interest in them, refine the requirements and state them clearly so you can test them. What's this weird little section down here on Security? Hmm. Maybe, we _do_ have security requirements....
Similarly, the "snow card" is a complete set of attributes you may need to consider for a single requirement. If you're used to writing "stories" on an index card, the snow card is a way to ensure you captured everything of interest. Do you always need all the attributes? I can't tell you. But I can tell it's worth asking if, for example, there are reasons why a stakeholder might be seriously unhappy if you don't supply that feature.
In short, if it's useful in requirements engineering, you'll find it here. Do you need to read every word? No. There are helpful pointers to other sections in the book. And you'll always find a few nuggets there. All-in-all, well worth the time.
-- stephen mellor
Full disclosure notice: I have worked on-and-off with the Robertsons over 25 years. We worked together recently on modifying requirements coursework for a system-engineering audience. And I was a reviewer on this third edition of the book. That's how come I know it's worth the candle.