Discovering Real Business Requirements for Software Proje... and over one million other books are available for Amazon Kindle. Learn more
CDN$ 100.20
  • List Price: CDN$ 106.95
  • You Save: CDN$ 6.75 (6%)
Usually ships within 1 to 2 months.
Ships from and sold by Amazon.ca.
Gift-wrap available.
Quantity:1
Have one to sell?
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Discovering Real Business Requirements for Software Project Success Hardcover – Mar 10 2004


See all 2 formats and editions Hide other formats and editions
Amazon Price New from Used from
Kindle Edition
"Please retry"
Hardcover
"Please retry"
CDN$ 100.20
CDN$ 99.93 CDN$ 75.00

Best Books of 2014
Unruly Places, Alastair Bonnett’s tour of the world’s most unlikely micro-nations, moving villages, secret cities, and no man’s lands, is our #1 pick for 2014. See all

Special Offers and Product Promotions

  • Join Amazon Student in Canada


Customers Who Bought This Item Also Bought



Product Details

  • Hardcover: 241 pages
  • Publisher: Artech House Publishers; 1 edition (March 10 2004)
  • Language: English
  • ISBN-10: 1580537707
  • ISBN-13: 978-1580537704
  • Product Dimensions: 26.2 x 18.3 x 1.9 cm
  • Shipping Weight: 585 g
  • Average Customer Review: 5.0 out of 5 stars  See all reviews (2 customer reviews)
  • Amazon Bestsellers Rank: #414,663 in Books (See Top 100 in Books)
  • See Complete Table of Contents

Product Description

About the Author

Robin F. Goldsmith is President of Go Pro Management, Inc., a consultancy in Needham, MA. He has extensive information systems experience, having worked in this capacity for the City of Cleveland, large financial institutions, and a “Big Four” management consulting firm. Mr. Goldsmith presents public and in-house seminars and is a frequent speaker at leading leading software development and quality/testing conferences. He earned his LL.M. in taxation law at Boston University, J.D. at Suffolk University, M.S. in psychology from Pennsylvania State University, and A.B. in psychology from Kenyon College.

Customer Reviews

5.0 out of 5 stars
5 star
2
4 star
0
3 star
0
2 star
0
1 star
0
See both customer reviews
Share your thoughts with other customers

Most helpful customer reviews

Format: 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.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.
Format: Hardcover
This book changed how we approach development projects. It is easy and fun to read and provides deep insights.
Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again.

Most Helpful Customer Reviews on Amazon.com (beta)

Amazon.com: 6 reviews
10 of 10 people found the following review helpful
Testing Requirements is Part of Discovering Requirements Sept. 2 2004
By Johanna Rothman - Published on Amazon.com
Format: 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
This book will improve the quality of your products ! May 17 2004
By Joe Fisher - Published on Amazon.com
Format: 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
Differentiates Identification of Business Problems from the Solution Alternatives Dec 19 2007
By Paul L. - Published on Amazon.com
Format: 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.
2 of 2 people found the following review helpful
Excellent Practical Application Feb. 13 2009
By Amazon Customer - Published on Amazon.com
Format: Hardcover Verified Purchase
Concise, addressing the essentials of discovering the 'real' business requirements of an organization. Effective and efficient testing methodologies that are readily applicable to requirements analysis. I found the "Problem Pyramid" tool to be particularly useful. Differentiation between the 'business requirements' vs 'system design requirements' was enlightening. Every technologist should be reading this book to ensure that the real business requirements are discovered before any coding begins. Excellent knowledge for account managers and business analysts as well. Strongly recommended.
4 of 5 people found the following review helpful
Excellent book by an experienced practicioner Nov. 4 2006
By Alf - Published on Amazon.com
Format: Hardcover Verified Purchase
I wanted to find a book that I could recommend to my requirements-challenged clients. This was the first I bought and the last I'll need. The author has a solid command of the subject and obvious real-world experience. Nestled among the chapters are over 60 "tests" to tell if you have real requirements.

I only gave it four stars because I was put off by the author's tilting at windmills in the first few chapters as he tries to stave off imagined criticism.


Feedback