<< 1 >>
Rating: 
Summary: Valuable advices, but not for beginners
Review: I found this book very insightfull, but it needs to have a first idea about what is the requirements engineering and how it's processed. Once you have this idea, this book helps you. You'll find here, essentially pieces of advices which looks like process patterns (in my opinion it should even improve the book to show these advices through a pattern form) to tackle specific problems whith requirements engineering. Moreover, these advices can be read separately. For the beginners, it mises a strong frame along the book to know what is exactly requirements management and so on. But I think the authors are right to do not try to satisfy everybody. As a weakness, I don't know why, but this book seems to be a bit old, where the edition date is only 1997, through a lot of details I feel to read a book written in the early 1980s. But this book is not about technology, so it's not a big weakness.
Rating: 
Summary: Some decent suggestions, but fluff to content ratio is 5:1.
Review: I've been in this part of the business for a while and I haven't seen anything quite like this book for requirements. A nice blend of theory and VERY practical advice, you can easily use the book in at several ways: 1. Better understanding of a particular techniques' effectiveness and context, for example use cases (called viewpoints here) or state-transition diagrams. 2. Flip through the book and see which guidelines you can most effectively apply to your current project, e.g. building a database or putting in a table of contents. 3. Evaluate your "maturity level" & determine how to improve your current requirements process.I can't tell if would be helpful to someone who had never wrestled with serious requirements, but even then, it has a good bibliography & website. Belongs on the analyst's working bookshelf.
Rating: 
Summary: Great for use at different levels
Review: I've been in this part of the business for a while and I haven't seen anything quite like this book for requirements. A nice blend of theory and VERY practical advice, you can easily use the book in at several ways: 1. Better understanding of a particular techniques' effectiveness and context, for example use cases (called viewpoints here) or state-transition diagrams. 2. Flip through the book and see which guidelines you can most effectively apply to your current project, e.g. building a database or putting in a table of contents. 3. Evaluate your "maturity level" & determine how to improve your current requirements process. I can't tell if would be helpful to someone who had never wrestled with serious requirements, but even then, it has a good bibliography & website. Belongs on the analyst's working bookshelf.
Rating: 
Summary: Sci Tech News, Sept 1997
Review: Presents guidelines which reflect good practice in requirements engineering, based on the authors' experience in research and in software and systems development. The guidelines range from common sense tips to complex new methods, and can be used in any order which suits the reader's problems, goals and budget. Guidlelines are consistent with ISO 9000 and CMM, are ranked with cost and benefit analysis, include implementation advice, and can be combined and applied to suit an organization's needs.
Rating:
Summary: Section on Safety-Critical Systems a plus
Review: The inclusion of a section dedicated to Requirements Engineering of Safety-Critical applications was a big plus and a differentiator when compared to other books on Requirements Engineering ..
Rating:
Summary: Some decent suggestions, but fluff to content ratio is 5:1.
Review: There are some usable guidelines for requirements gathering, though I feel common sense would give you many of them. I think this book is watered down heavily to fill 350 pages; the content could have fit in 50 pages. The book was not thought out.
<< 1 >>
| 
