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 solutions based on actual project experiences, this book answers many of the tough questions raised by industry professionals. From strategies for estimating and working with customers to the nuts and bolts of documenting requirements, this essential companion gives developers, analysts, and managers the cosmic truths that apply to virtually every software development project.
Karl Wiegers is Principal Consultant with Process Impact, a software development consulting and training company in Portland, Oregon. He has a PhD in organic chemistry. Karl is the author of 14 books, including Software Requirements Essentials (with Candase Hokanson), Software Development Pearls, The Thoughtless Design of Everyday Things, Software Requirements (with Joy Beatty), More About Software Requirements, Successful Business Analysis Consulting, and a forensic mystery novel titled The Reconstruction.
Karl has also written many articles on software development, design, project management, chemistry, military history, consulting, and self-help, as well as 18 songs. He has delivered hundreds of training courses, webinars, and conference presentations worldwide. When he's not at the keyboard, Karl enjoys wine tasting, volunteering (library and Meals on Wheels), playing guitar, recording songs (hear them at https://www.karlwiegers.com/songs.html), military history, and traveling.
Some years ago, I did the computer based training "Exploring User Requirements with Use Cases" (copyright 2004), also by Karl Wiegers. As he did with the CBT, I'm finding the author is covering the key topics concisely. He is providing references to the supporting materials and/or directing you to his other book, "Software Requirements 2", for details.
I feel this book is best for someone who has had some exposure to the requirements gathering process. Without some experience trying to gather information and compose a specification, I don't believe you can appreciate this book. The context of some experience will give you a lauching point into more in depth study of how to develop system specifications. This book will shows the issues facing you when creating a system specification and guides you to useful resources.