Software Requirements

* Introduction * Acknowledgments * Software requirements: What, why, and who * Chapter 1: The essential software requirement * Chapter 2: Requirements from the customer's perspective * Chapter 3: Good practices for requirements engineering * Chapter 4: The business analyst * Requirements development * Chapter 5: Establishing the business requirements * Chapter 6: Finding the voice of the user * Chapter 7: Requirements elicitation * Chapter 8: Understanding user requirements * Chapter 9: Playing by the rules * Chapter 10: Documenting the requirements * Chapter 11: Writing excellent requirements * Chapter 12: A picture is worth 1024 words * Chapter 13: Specifying data requirements * Chapter 14: Beyond functionality * Chapter 15: Risk reduction through prototyping * Chapter 16: First things first: Setting requirement priorities * Chapter 17: Validating the requirements * Chapter 18: Requirements reuse * Chapter 19: Beyond requirements development * Requirements for specific project classes * Chapter 20: Agile projects * Chapter 21: Enhancement and replacement projects * Chapter 22: Packaged solution projects * Chapter 23: Outsourced projects * Chapter 24: Business process automation projects * Chapter 25: Business analytics projects * Chapter 26: Embedded and other real-time systems projects * Requirements management * Chapter 27: Requirements management practices * Chapter 28: Change happens * Chapter 29: Links in the requirements chain * Chapter 30: Tools for requirements engineering * Implementing requirements engineering * Chapter 31: Improving your requirements processes * Chapter 32: Software requirements and risk management * Epilogue * Current requirements practice self-assessment * Requirements troubleshooting guide * Sample requirements documents * Glossary * * About the authors

Karl Wiegers, PhD, is a principal consultant with a software process consulting and education company. An expert in requirements engineering, process improvement, software quality, and project management, Karl has written several books, including the two previous editions of Software Requirements.Joy Beatty, a leader in the software requirements community, has trained thousands of business analysts and helped major organizations build business-analysis centers of excellence. She is coauthor of Visual Models for Software Requirements.