| "Consciousness raising for systems analysts." —Tom
Demarco
Principal, Atlantic Systems Guild
"It's likely
that this book will not only give you concrete ways to improve our requirements
gathering process, but will also change the way that you look at requirements." —Elisabeth
Hendrickson,
Quality Tree Consulting
"Twelve years after it first appeared, this book is completely
relevant to today's development projects.
". . . most companies would benefit greatly
from improving the way they define requirements.
This book will help you do that, and I recommend
it to anyone who has anything to do with software
development."
—Richard Mateosian,
IEEE Micro
"Anyone who wants to build a product
should understand this book." —Watts S.
Humphrey,
Software Engineering Institute Carnegie Mellon
University
". . . a superb new book on systems analysis.
. . . you simply must read and absorb this gem.
It complements every brand-name systems analysis
methodology currently being practiced."
—Ed
Yourdon,
American Programmer
". . . provides an excellent set of principles
amply illustrated by relevant and thought-provoking
examples."
—Barry
Boehm, UCLA
"This extraordinary book grabbed me
from the Preface through to its end. Well written, readable, and paced comfortably.
. . . Highly recommended. . . . sure to change how you develop requirements for
your projects." —John L. Berg,
Computer Standards & Interfaces
". . . makes a very important, serious subject
fun and easy to read."
—Bill
Loveless,
PC News & Reviews
"The
Freedman and Weinberg book is full of tricks for eliciting from users what they
cannot express without your help and for testing to see if your understanding
of user needs is correct. "It is impossible to overemphasize the value
of this. Errors that you make in eliciting user requirements can be very expensive
to fix. Any software engineering book will tell you this. What the software engineering
books don't tell you is that it also can be expensive to give users what they
say they want instead of what they need." —J.
Adrian Zimmer,
Editor, Journal of Software Maintenance
"There are not very many technical
books on specification from over a decade ago that
people still keenly read, enjoy, and recommend to
their colleagues, but this is such a one . . . it
takes a clear head to reflect on what is really
happening, and then to look ahead to what ought
to be done about it. It is even better if the book
is not only visionary and sharp on the essential
principles of a domain, but also delightfully funny
and spicy. This book is."
—Ian
Alexander,
http://i.f.alexander.users.btopenworld.com
"There is no book in the software
industry before or since Exploring Requirements
that has as much to say about the integration of
creativity with the software design process. I have
been in the systems industry, in a variety of positions
since 1974, and this book is my all time number
one reference."
—Jim Adamski,
jim.adamski@entellic.com
| 
