Requirements Engineering: A Good Practice Guide

by Pete Sawyer and Ian Sommerville

Book Overview

Zwei beliebte Autoren des Software-Engineerings stellen diese Seite des Gebietes in einer praxisnahen FAQ-Form (Fragen und Antworten) vor. Sie legen dar, wie die Anforderungen an eine Software (Pflichtenheft) den Vorstellungen der Nutzer entsprechen sollte.

• Format: Paperback
• Language: English
• ISBN: 0471974447
• ISBN13: 9780471974444
• Release Date: April 1997
• Publisher: Wiley
• Length: 416 Pages
• Weight: 1.70 lbs.
• Dimensions: 0.9" x 7.5" x 9.3"

Customer Reviews

Section on Safety-Critical Systems a plus

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 ..

Valuable advices, but not for beginners

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.

Great for use at different levels

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.