Title: Very Comprehensive
Product review: If you are a beginner to requirements management, I can't think of a better place to start. It contains a chapter on just about every aspect of requirements and even touches on Project Management (the 2 areas are closely related).Why did it lose 1*:- the book is a little dated .. it reads like Karl started by promoting the SRS type document to capture requirements, but as the book progressed he started to promote use cases, (which have become more widely accepted in the last 10 years).- some of the examples are flawed. This is perhaps an unfair criticism, because I may be finding flaws that few other people will spot, and they do not detract from the value gained from reading the book.- too many words and not enough examples. This is a criticism that I level at almost all technical books of this nature. Karl's is no different in this respect.One of the better books for anyone needing to learn about requirements management.
Would you say this review depicts the product in a flattering or unflattering light?
