- Hardcover: 241 pages
- Publisher: Artech House (28 Feb 2004)
- Language English
- ISBN-10: 1580537707
- ISBN-13: 978-1580537704
- Product Dimensions: 26.2 x 18.3 x 1.9 cm
- Amazon Bestsellers Rank: 1,376,465 in Books (See Top 100 in Books)
- See Complete Table of Contents
Discovering Real Business Requirements for Software Proje...
and over 900,000 other books are available for Amazon Kindle .
Learn more
| |||||||||||||||
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Visit the Amazon.co.uk Trade-In Store for more details. |
Product details |
More About the Author
Product Description
Product Description
Book InformationFinding customer requirements is an essential activity for software developers. While a number of books on the market deal with software requirements, this is the first resource to offer a methodology for discovering and testing the real business requirements that software products must meet in order to provide value. The book provides practical techniques that help ensure successful software development and greater satisfaction among the organizations that put these software systems to use. The powerful techniques and methods presented in this hands-on reference are applied to a real business case from a company recognized for world-class excellence. From an examination of key methods for gathering and understanding information about requirements, to seven guidelines for documenting and communicating requirements, this book is a comprehensive, single source for uncovering the real business requirements that lead to software project success.Content HighlightsValue of Testing Up-Front. The Regular Way. Are They Requirements? Evaluating Requirements' Form. Discovering Real Requirements. Problem Pyramid. Applying the Techniques. Data Gathering. Formats for Analyzing Requirements. Key to Completeness. Formats for Documenting Requirements. Finding Overlooked Requirements.
Tag this product(What's this?)Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organise and find favourite items. |
Customer Reviews
|
There are no customer reviews yet on Amazon U.K.
|
||||||||||||||||||||
|
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com:
4.7 out of 5 stars (6 customer reviews)
10 of 10 people found the following review helpful:
5.0 out of 5 stars
Testing Requirements is Part of Discovering Requirements, 2 Sep 2004
By Johanna Rothman - Published on Amazon.com
This review is from: Discovering Real Business Requirements for Software Project Success (Computing Library) (Hardcover)
If you ever wanted to know if your requirements were accurate and complete, this book will help. As Robin says on p. 13, "...we're going to intermix discovery methods with techniques for testing the adequacy of requirements." Using his problem pyramid - which includes a way to measure the problem and the solution - Robin discusses several techniques to elicit and define requirements.
Robin defines 64 techniques to test requirements - throughout a project. For example, test method #17, "identify assumptions" is common sense that too few people remember. Test method #53 is "Defining acceptance criteria," a technique useful for any project if you want to know you've built what the customer wanted.
Between the problem pyramid emphasis on measurement and the various tests, the book can help you meet its promise of preventing too much requirements change throughout a project.
10 of 10 people found the following review helpful:
5.0 out of 5 stars
This book will improve the quality of your products !, 17 May 2004
By Joe Fisher - Published on Amazon.com
This review is from: Discovering Real Business Requirements for Software Project Success (Computing Library) (Hardcover)
As a Software Developer and Consultant, I found this book to be a clear and practical guide that will be a valuable asset to all system development professionals.I strongly recommend it to all systems professionals, and believe it is a MUST HAVE for systems analysts !
The book presents a step-by-step methodology that contrasts how things are "normally" done with how they should be done to achieve optimum results and satisfied customers.
In addition to analyzing why and how traditional approaches fail, the text provides a comprehensive checklist that can be followed to avoid common mistakes and improve the quality of the most significant aspect of develop: gathering and documenting requirements !
Presented in a easy-to-read format sprinkled with wry humor, you are likely to find it a more enjoyable read than most technical texts.
4 of 4 people found the following review helpful:
4.0 out of 5 stars
Differentiates Identification of Business Problems from the Solution Alternatives, 19 Dec 2007
By Paul L. - Published on Amazon.com
This review is from: Discovering Real Business Requirements for Software Project Success (Computing Library) (Hardcover)
The 64 ways to test requirements are good and helpful, and you'll need to determine how many of these techniques (and with what rigor) could/should be applied to your project in your organizational context. The greatest benefit for me from reading this book was understanding the distinction Goldsmith makes between business problems and the solution design alternatives that might address them. I've witnessed problems on projects where this distinction was not understood, and I'm convinced that identifying the business problem(s) and business requirements first is critical before undertaking software requirements and solution alternatives.
Listmania!
Look for similar items by category
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
