Rating: 
Summary: Great treatment of traditional, rigorous requirements mgmt
Review: When it comes to the development life cycle, there are generally two broad schools of thought: rigorous, waterfall approach; and the agile, iterative approach. This text sits in the heart of the rigorous, waterfall approach.Iterative approaches are proven to be more effective at eliciting requirements, a fact which is somewhat embraced in the author's discussion of use cases; however, Jacobson originally envisioned use cases to replace other requirements documents as a central element in elicitation, rather than just being a quick diversion. In reality, most of us strike a middle ground. Projects can't be run in most organizations without rigor, and Software Requirements is a thorough treatment or requirements development and management. The well-organized book is a quick read, and is filled with prescriptive advice, risks, sample forms, and checklists that can be applied to your requirements effort. No wonder the author won a Software Productivity Award for the effort!
Rating: 
Summary: If you can't read them all, read this one!
Review: Whether you are a customer, project manager or member of a project team, you can't go wrong with this book on software requirements. If you are only going to read one book on software requirements this is about as good as it gets. Wiegers writes in an eminently readable style. He doesn't claim that any one way is right for everyone. Instead he provides a variety of tips and techniques you can choose from at will to help you communicate with your customer (or vendor), document your requirements, and track and manage them. Most of his ideas are quick and simple to implement and should show distinct benefits almost immediately. This book is one I go back to time and again when working on process development and improvement for my organization. Read it!
| 
