Join Amazon Prime and ship Two-Day for free and Overnight for $3.99. Already a member? Sign in.

Discovering Real Business Requirements for Software Proje... and over 300,000 other books are available for Amazon Kindle � Amazon�s new wireless reading device. Learn more

Quantity:

More Buying Choices

20 used & new from $50.00

Have one to sell? Sell yours here

Share with Friends

Share your own customer images

Search inside this book

Start reading Discovering Real Business Requirements for Software Proje... on your Kindle in under a minute. Don�t have a Kindle? Get yours here.

Discovering Real Business Requirements for Software Project Success (Computing Library) (Hardcover)

by Robin F. Goldsmith (Author) "Defining business requirements is the most important and poorest performed part of system development..." (more)
Key Phrases: requirements definers, strawman requirements, itemized deliverables, Ann Analyst, Proactive Testing, Engineered Deliverable Quality (more...)

4.7 out of 5 stars See all reviews (7 customer reviews)

List Price:	$89.00
Price:	$74.68 & this item ships for FREE with Super Saver Shipping. Details
You Save:	$14.32 (16%)

In Stock.
Ships from and sold by Amazon.com. Gift-wrap available.

Only 1 left in stock--order soon (more on the way).

Want it delivered Tuesday, July 7? Choose One-Day Shipping at checkout. Details

13 new from $50.00 7 used from $83.95

Also Available in:	List Price:	Our Price:	Other Offers:
Kindle Edition (Kindle Book)		$67.21

Frequently Bought Together

Price For All Three: $127.54

Show availability and shipping details

This item: Discovering Real Business Requirements for Software Project Success (Computing Library) by Robin F. Goldsmith
In Stock.
Ships from and sold by Amazon.com.
This item ships for FREE with Super Saver Shipping. Details
The Software Requirements Memory Jogger: A Pocket Guide to Help Software And Business Teams Develop And Manage Requirements (Memory Jogger) by Ellen Gottesdiener
In Stock.
Ships from and sold by Amazon.com.
Eligible for FREE Super Saver Shipping on orders over $25. Details
Writing Effective Use Cases (Agile Software Development Series) by Alistair Cockburn
In Stock.
Ships from and sold by Amazon.com.
This item ships for FREE with Super Saver Shipping. Details

Customers Who Bought This Item Also Bought

Writing Effective Use Cases (Agile Software Development Series)

by Alistair Cockburn

4.6 out of 5 stars (46) $40.65

UML for the IT Business Analyst: A Practical Guide to Object-Oriented Requirements Gathering

by Howard Podeswa

4.3 out of 5 stars (19) $31.49

Software Requirements, Second Edition (Pro-Best Practices)

by Karl E. Wiegers

4.6 out of 5 stars (46) $26.39

More About Software Requirements: Thorny Issues and Practical Advice

by Karl E. Wiegers

4.6 out of 5 stars (12) $19.79

Requirements by Collaboration: Workshops for Defining Needs

by Ellen Gottesdiener

5.0 out of 5 stars (15) $45.51

› Explore similar items

Editorial Reviews

Product Description
While a number of books on the market deal with software requirements, this is the first resource to offer you a methodology for discovering and testing the real business requirements that software products must meet in order to provide value. The book provides you with practical techniques that help prevent the main causes of requirements creep, which in turn enhances software development success and satisfaction among the organizations that apply these approaches. Complementing discovery methods, you also learn more than 21 ways to test business requirements from the perspectives of assessing suitability of form, identifying overlooked requirements, and evaluating substance and content.

The powerful techniques and methods presented are applied to a real business case from a company recognized for world-class excellence. You are introduced to the innovative Problem Pyramidtm technique which helps you more reliably identify the real problem and requirements content. From an examination of key methods for gathering and understanding information about requirements, to seven guidelines for documenting and communicating requirements, while avoiding analysis paralysis, this book is a comprehensive, single source for uncovering the real business requirements for your software development projects.

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.

Product Details

Hardcover: 241 pages
Publisher: Artech House Publishers (March 2004)
Language: English
ISBN-10: 1580537707
ISBN-13: 978-1580537704
Product Dimensions: 10.3 x 7.2 x 0.7 inches
Shipping Weight: 1.3 pounds (View shipping rates and policies)

Average Customer Review: 4.7 out of 5 stars See all reviews (7 customer reviews)

Amazon.com Sales Rank: #640,338 in Books (See Bestsellers in Books)

Would you like to update product info or give feedback on images?

Front Cover | Table of Contents | First Pages | Index | Surprise Me!

Inside This Book (learn more)

First Sentence:
Defining business requirements is the most important and poorest performed part of system development. Read the first page

Key Phrases - Statistically Improbable Phrases (SIPs): (learn more)
requirements definers, strawman requirements, itemized deliverables, overlooked deliverables, problem pyramid, order processing manager, full end result, real business requirements, mini definition, documenting business requirements, product system requirements, defining business requirements, presumed process, requirements creep, overlooked requirements, manufacturing planners, formal technical review, requirements discovery, deliverable whats, customer specialist, real requirements, documenting requirements, reviewing requirements, technical folks, user stories

Key Phrases - Capitalized Phrases (CAPs): (learn more)
Ann Analyst, Proactive Testing, Engineered Deliverable Quality, Track Changes, New York, Receives Order Want Date, Software Engineering Body of Knowledge, United States, Accept Changes, Mastering the Requirements Process, Problem Cause

New!
Books on Related Topics | Concordance | Text Stats

Browse Sample Pages:
Front Cover | Table of Contents | First Pages | Index | Surprise Me!

Citations (learn more)

This book cites 36 books:

Mastering the Requirements Process (2nd Edition) by Suzanne Robertson on page 48, page 65, and page 123
Handbook of Walkthroughs by Gerald M. Weinberg on page 29, and page 30
Software Inspection by Tom Gilb on page 29, and page 30
Rapid Development: Taming Wild Software Schedules by Steve McConnell on page 48, and page 49
Software Requirements, Second Edition (Pro-Best Practices) by Karl E. Wiegers on page 38, and page 48

See all 36 books this book cites

9 books cite this book:

Practical Insight into Cmmi (Artech House Computing Library) by Tim Kasse in Back Matter
Text Mining for Biology And Biomedicine by Sophia Ananiadou in Back Matter
Information Systems Development: Methodologies, Techniques and Tools by David Avison on page 108
Facilitating the Project Lifecycle: The Skills & Tools to Accelerate Progress for Project Managers, Facilitators, and Six Sigma Project Teams (Jossey Bass Business and Management Series) by Janet A. Means on page 370
Agile Systems With Reusable Patterns of Business Knowledge: A Component-Based Approach (Artech House Computing Library) by Amit Mitra in Back Matter

See all 9 books citing this book

Books on Related Topics (learn more)

New Directions in Project Management by Paul C. Tinnirello

Discusses:

Team Design by Peter H. Jones

Discusses:

Troubled IT Projects by John Smith

Discusses:

Successful Software Reengineering by Salvatore Valenti

Discusses:

What Do Customers Ultimately Buy After Viewing This Item?

	64% buy the item featured on this page: Discovering Real Business Requirements for Software Project Success (Computing Library) 4.7 out of 5 stars (7) $74.68
	10% buy The Software Requirements Memory Jogger: A Pocket Guide to Help Software And Business Teams Develop And Manage Requirements (Memory Jogger) 4.5 out of 5 stars (22) $12.21
	10% buy Software Requirements, Second Edition (Pro-Best Practices) 4.6 out of 5 stars (46) $26.39
	8% buy Seven Steps to Mastering Business Analysis 4.8 out of 5 stars (4) $62.95

Explore similar items

Tags Customers Associate with This Product

(What's this?)

Click on a tag to find related items, discussions, and people.

business requirements(3)

requirements(2)

See all 3 tags...

Help others find this product — tag it for Amazon search

No one has tagged this product for Amazon search yet. Why not be the first to suggest a search for which it should appear?

Customer Reviews

7 Reviews

5 star:		(5)
4 star:		(2)
3 star:		(0)
2 star:		(0)
1 star:		(0)

Average Customer Review

4.7 out of 5 stars (7 customer reviews)

Share your thoughts with other customers:

Create your own review

Most Helpful Customer Reviews

7 of 7 people found the following review helpful:

5.0 out of 5 stars This book will improve the quality of your products !, May 17, 2004

By	Joe Fisher - See all my reviews

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.

Comment Comment | Permalink | Was this review helpful to you? Yes No (Report this)

6 of 6 people found the following review helpful:

5.0 out of 5 stars Testing Requirements is Part of Discovering Requirements, September 2, 2004

By	Johanna Rothman (Arlington, MA USA) - See all my reviews (REAL NAME)

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.

Comment Comment | Permalink | Was this review helpful to you? Yes No (Report this)

1 of 1 people found the following review helpful:

4.0 out of 5 stars Differentiates Identification of Business Problems from the Solution Alternatives, December 19, 2007

By	Paul L. (Portland, OR) - See all my reviews

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.

Comment Comment | Permalink | Was this review helpful to you? Yes No (Report this)

Share your thoughts with other customers: Create your own review

› See all 7 customer reviews...

Most Recent Customer Reviews

5.0 out of 5 stars Excellent Practical Application
Concise, addressing the essentials of discovering the 'real' business requirements of an organization. Read more

Published 4 months ago by Kevin R. Winegardner

5.0 out of 5 stars "Real" information for Business Users to Communicate
This book will be a great aid for me in helping Business Users to make better requests by outlining the business problems in such a way that technicians can meet their needs with... Read more

Published on February 16, 2007 by Carole E. Sandman

4.0 out of 5 stars Excellent book by an experienced practicioner
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. Read more

Published on November 5, 2006 by Alf

5.0 out of 5 stars Defining requirements for software gurus and the rest of us
This book is eminently readable for all practitioners who have to deal with the challenge of identifying and adequately defining requirements. Read more

Published on January 3, 2005 by Denise Robitaille

› See all 7 customer reviews...

.jsOffDisplayBlock { display: block; } .jsOffDisplayInline { display: inline; } .jsOffVisibility { visibility: visible; } .jsOnDisplayBlock { display: none; } .jsOnDisplayNoneBlock { display: block; } .jsOnDisplayNoneInline { display: inline; } .jsOnDisplayInline { display: none; } .jsOnVisibility { visibility: hidden; } .jsOnDisplayBlock { display: none; } .jsOnDisplayInline { display: none; } .jsOnVisibility { visibility: hidden; }