 |
GetTextbooks.com
Compare Prices & Save up to 90% |
|
|
|
| Login | Sign up | My Wish List |
 | | Mastering the Requirements Process by Suzanne Robertson, James Robertson ISBN-10: 9780201360462 ISBN-10: 0-201-36046-2 ISBN-13: 9780201360462 ISBN-13: 978-0-201-36046-2 Hardcover 1999-08-12 Addison-Wesley Professional Find Lowest Price |
Editorials | ||
Product Description Written by two internationally acclaimed experts on requirements, Mastering the Requirements Process provides software engineers with the practical insights, techniques and templates to discover exactly what their customers desire for their systems. It also explains how to implement an easily learned, ongoing forma requirements process which allows the requirements to evolve over the life time of the project. Using this book you will learn how to ask the right questions, how to determine whether or not the final solution will satisfy the requirements, how to fit the solution to the requirements to provide high quality products and even how to reuse requirements. The result is, systems that the user loves to use! | ||
Amazon.com Review Written in an engaging style and relevant for any software analyst or designer, Mastering the Requirements Process provides a powerful and useful guide to defining more complete software requirements that lead to better software overall. It's also filled with innovative advice. The heart of this book is the authors' Volere Requirements Process Model, a step-by-step guide to gathering your requisites. Throughout this book, the authors use this process to explicate a single case study--a system for a municipality that will optimize the de-icing of roadways during snowy weather. Along the way, the book provides a solid guide to identifying and refining requirements, both functional and nonfunctional (such as performance and ease of use). There are many excellent ideas in the book, including the notion of fitness for your requirements, which can be later used to track whether the software is successful. The book also wisely separates technology from requirements so that analysts can concentrate on understanding and modeling business problems instead of moving right away to the nuts and bolts of implementation. Even if you don't adopt the Volere model in toto, you can benefit from the concepts of "trawling" (a metaphor for the requirements-gathering process), quality gateways (in which tentative requirements are evaluated for inclusion in a project), and the wise use of patterns to help simplify the process. Anchored by numerous examples (including many samples of successful requirements), the book provides an appealing mix of new ideas along with a remarkably clear presentation. In short, Mastering the Requirements Process provides useful advice that can make the project specification building phase of the software process easier and more robust. It provides the first steps for improving overall software quality for your organization. --Richard Dragan Topics covered: Volere Requirements Process Model; project blastoff; determining requirements; user and stakeholders; project constraints; requirements constraints; use cases; business events; adjacent systems; innovation; trawling for requirements: apprenticing, interviews, and videotape; functional and nonfunctional requirements; fit criteria; quality gateways; traceability; prototyping and scenarios; low and high fidelity prototypes; patterns and requirements reuse; improving the requirements gathering process. | ||
Reviews | ||
A book to study I recommend this book to anyone interested in discovering and documenting requirements whether the target is automation or not. It is comprehensive and very readable, but it is not dogmatic. The ideas it expresses can be used effectively with a wide range of methodologies. I've been doing requirements for more than 20 years and I learned things from this book. The notion of the "Blast Off" (hate that term, love the concept) as a key political event reinforced and expanded ideas I had before. The extensive checklist for the "Blast Off" is much more thorough than anything I've ever put together myself. The idea of "Trolling for Requirements" also expanded my horizons. The Volare snow card is an excellent starting point for collecting requirements that emphasizes the point that understanding the rational behind a requirement is as important as understanding the requirement itself. Over the years I've used this book as the basis for a series of brown bag lunches to help junior analysts better appreciate the nature of the requirements process. It has been generally well received. I've probably purchases over a dozen copies of this book to give to others, some of them with my own money. Along with Exploring Requirements: Quality Before Design this is one of the first two books every business or system analyst should read. | ||
Excellent book. The first chapter should be read and re-read by every engineer out there. The bood provides a near turn-key requirements elicitation / engineering process. | ||
Fatal Fundamental Flaws (cont) this book has not only the flaws identified below by F.C.Passavant - in addition it has inconsistencies in terminology, lots of ambiguity. it was difficult to map described precesses to those regarded in the field (i.e. IATF Release 3.1) I found "Requirements Engineering" by Elizabeth Hull, Kenneth Jackson, and Jeremy Dick a much better choice. | ||
Practical and good to keep it as a reference I found this book very practical, it's an excellent source of examples and cases. Even I would recommend it as a text book for university students. | ||
Have solid requirements in place before you begin The cost of undetected errors in software requirements can be extremely high. To start with, it could happen to build the wrong product. So, any care must be taken to have strong foundations in place; this is still the case if you plan to go Agile. If you like Steve McConnell's 'Rapid Development' and 'Code Complete', this book is a perfect complement covering the early phases of the software process. In a sentence, this book is a must for anyone dealing with software engineering, from the developer to the manager. | ||