This book i think which I most wanted to read about, yeah I love creating software requirements.
So what this books offer…
Karl Wiegers is known software analyst, he begins his book with very clear and concise message, that requirement engineering models must be adjusted and that requirements for software projects are different in type and variety and very depend on type and size of particular software company.
This book describe different types of categories which you need to think about, when your write your software requirements.
Interesting book author say it’s better to speak about user cases instead of working with catalogue of questions to check the box.
This book gives a lot of interesting advises, how to collect and analyze requirements.
Wiegers even discuss the topic of code review.
Very interesting the book author says it’s depends sometimes use case should not be detailed at all.
Sometimes business rules can and will be in violation with requirements, this book gives good advise about that.
Summary: Here and there these books consist gems, still it feels kind of dated, many times book author stated that no requirement is perfect and there a lot of additional work is needed, the author do not mention the framework which would help to solve such problem, still this book consist many interesting views and ideas. Can I recommend this book? Well I suppose , but only as reference for anyone who are switching into the role of req engineer or business analyst.