No matter how much instruction you've had on managing software requirements, there's no substitute for experience. Too often, lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book, Software Requirements, Second Edition, requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book.
With straightforward, professional advice and practical

Part Ⅰ On Essential Requirements Concepts
1 Requirements Engineering Overview
2 Cosmic Truths About Software Requirements
Part Ⅱ On the Management View of Requirements
3 The Business Value of Better Requirements
4 How Long Do Requirements Take?
5 Estimating Based on Requirements
Part Ⅲ On Customer Interactions
6 The Myth of the On-Site Customer
7 An Inquiry, Not an Inquisition
8 Two Eyes Aren't Enough
Part Ⅳ On Use Cases
9 Use Cases and Scenarios and Stories, Oh My!
10 Actors and Users
11 When Use Cases Aren't Enough
Part Ⅴ On Writing Requirements
12 Bridging Documents
13 How Much Detail Do You Need?
14 To Duplicate or Not to Duplicate
15 Elements of Requirements Style
16 The Fuzzy Line Between Requirements and Design
Part Ⅵ On the Requirements Process
17 Defining ProJect Scope
18 The Line in the Sand
19 The Six Blind Men and the Requirements
Part Ⅶ On Managing Requirements
20 Handling Requirements for Multiple Releases
21 Business Requirements and Business Rules
22 Measuring Requirements
23 Exploiting Requirements Management Tools