Programming Books C Java PHP Python Learn more Browse Programming Books
Mastering the Requirements Process (2nd Edition) and over one million other books are available for Amazon Kindle. Learn more
Buy Used
FREE Shipping on orders over $35.
Condition: Used: Good
Comment: Shared Knowledge is a not for profit public charity! Check us out on facebook. We provide funding for educational programs in Richmond, Virginia. PLEASE READ FULL DESCRIPTION -USED GOOD- This book has been read and may show wear to the cover and or pages. There may be some dog-eared pages. In some cases the internal pages may contain highlighting/margin notes/underlining or any combination of these markings. The binding will be secure in all cases. This is a good reading and studying copy and has been verified that all pages are legible and intact. If the book contained a CD it is not guaranteed to still be included. Your purchase directly supports our scholarship program as well as our partner charities. All items are packed and shipped from the Amazon warehouse. Thanks so much for your purchase!
Access codes and supplements are not guaranteed with used items.
Add to Cart
Have one to sell? Sell on Amazon
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

Mastering the Requirements Process (2nd Edition) Hardcover – March 27, 2006

ISBN-13: 978-0321419491 ISBN-10: 0321419499 Edition: 2nd

Price: $15.09
13 New from $30.00 31 Used from $2.25
Amazon Price New from Used from
"Please retry"
Hardcover, March 27, 2006
$30.00 $2.25
"Please retry"

There is a newer edition of this item:



Shop the new
New! Introducing the, a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry. > Shop now

Product Details

  • Hardcover: 592 pages
  • Publisher: Addison-Wesley Professional; 2 edition (March 27, 2006)
  • Language: English
  • ISBN-10: 0321419499
  • ISBN-13: 978-0321419491
  • Product Dimensions: 7.6 x 1.5 x 9.6 inches
  • Shipping Weight: 2.4 pounds
  • Average Customer Review: 4.2 out of 5 stars  See all reviews (31 customer reviews)
  • Amazon Best Sellers Rank: #591,020 in Books (See Top 100 in Books)

Editorial Reviews 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. --This text refers to an alternate Hardcover edition.


Requirements are a make or break phase of the software development process. If the requirements are carefully chosen to represent what the customer wants, needs, and expects, then the project has a good chance of success. If not, the project may very well be doomed.

That said, it is easy to say that this book is about an important topic. But is it a good book about that important topic?

My vote is "yes." This is a nicely crafted, well-thought-through, complete, up-to-date view of the task of creating a requirements specification for a software project.

Nicely crafted? It is well written, readable, never pedantic. Well-thought-through? The authors base the book on seminars they have given and honed over the years. Complete and up-to-date? Not only are the basic topics covered, but the authors also mention such advanced topics as requirements reuse, requirements patterns, traceability, and an event + use case-driven approach.

The book is written for the requirements novice. There are plenty of detail-level discussions of steps and approaches, templates for framing the results, and an elaborated case study (how refreshing it is to see a case study based on de-icing roadways, rather than one of the traditional, overused topics like video rental or cruise control!) But the book can also be useful to the patient requirements expert - there is more verbiage than the expert will want, but by scanning carefully the essence of the book can be easily distilled out. Importantly, the essence of the book is conceptual rather than formula/methodology-driven - the authors say the book is intended "not as a set of canonical rules that must be obeyed, but as a reliable companion to intelligent work."

Given all of that, I found some things that were mildly annoying: Some of the terminology the authors use is cutesy, although often it is appropriate, but (a) "blastoff: as the term for project start? (The projects I've been involved with rarely start with a "blast"!); (b) "requirements leakage" for requirements that erroneously get accepted into a project? (I would have thought that things leak out of a project, not in!) The authors claim that their book can be used not just for customized software development projects, but also for software maintenance and even for projects that aggregate pre-built packages. But later they say that the requirements process should never consider the technology of the solution (all well and good for customization, but impossible for the latter two categories). The authors take the (debatable) position that "object-orientation has become the standard way of developing systems," but then mix the two terms "use cases" and "event-driven" as if they were the same, both related to the OO approaches. In my view, event-driven approaches are rather different from object-oriented ones (for example, Visual Basic allows the programmer to build an event-driven system, but the result may or may not (likely not!) be object-oriented). The authors speak of a "post-mortem review" (an excellent idea), but it is not until page 271 (near the end of the book) that it becomes clear that "post-mortem" means "after the requirements phase," not "after the project is complete." (Either could be correct, but the authors should make it clear which they mean when they first bring up the topic 250 pages earlier). There is an appropriate and thorough discussion of the topic of "fit," by which the authors mean that requirements should be expressed in a measurable way. But the authors fail to acknowledge that some things simply don't lend themselves to measurement, with the result that much mischief is done by those who attempt to measure the unmeasurable (e.g., the terrible tendency to state "the software product shall be modular" in terms of the length of program segments - "modules shall contain no more than 50 lines of code").

Things I particularly like about the book are Requirements representation is treated as a pragmatic topic, where requirements are to be readable by both application customers and software designers. There is none of the formal specification discussion that computer scientists love to advocate but that seldom fits the needs of real-world requirements. There is also a nice discussion of software tools, appropriately mentioning that they are a means to an end, not an end in themselves. (Interestingly, there is no mention of the now-in-disrepute term "CASE"!) The discussion of the "quality gateway," which covers the process of making a final decision as to which requirements to include in the final specification, is both important and nice. There are very well-done discussions of such topics as "requirements creep," "gold plating," "traceability," and "viability." (I was reminded of the wry comment by Jerry Weinberg at a conference many years ago that software may be the only discipline where the answer to the early-project question of feasibility is always "yes"!) The discussions of the avant-garde requirements topics like requirements reuse and requirements patterns are very nice. I was less pleased with the discussion of traceability - what the book contains is excellent material, but it fails to go far enough to note that tracing requirements into design and code, although extremely desirable, is so far an out-of-reach topic (due to the "explosion" of business requirements into design requirements as the life cycle proceeds, an explosion estimated by some to be measured in orders of magnitude).

There should be at least one book on requirements in the library of every enterprise, even every software professional. You could do a lot worse than choosing this one. -- Robert L. Glass --This text refers to an alternate Hardcover edition.

More About the Authors

Discover books, learn about writers, read author blogs, and more.

Customer Reviews

STYLE AND COMMUNICATION The writing style is fairly light and very readable, and the book clearly communicates to the reader.
Mick Addis
As a process it is also highly scalable, which means you can use it for a 3-day requirements gathering project just as well as for the 3-month project.
Michael Stringer
I recommend this book to anyone interested in discovering and documenting requirements whether the target is automation or not.
Richard C. Cohen

Most Helpful Customer Reviews

98 of 104 people found the following review helpful By Tony Stewart on August 28, 2000
Format: Hardcover
This is not only the best book on requirements gathering that I've found, it is one of the best books on *any* aspect of software development that I've ever read. It is clear, focussed, well-written, full of extremely powerful concepts, and illustrated with useful examples and formal models of all aspects of the requirements gathering process and requirements-related information. As a result, I not only gained tremendous insight into how to improve the requirements gathering process at our company, I also learned by clear example how to make best use of each of the modeling formalisms the authors recommend.
I've never written an on-line review before, but this book was so superior that I felt I had to take the time and share my enthusiasm. I hope you find it as valuable in your projects as we are finding at our company.
Comment 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
51 of 53 people found the following review helpful By A Customer on September 2, 1999
Format: Hardcover
This excellent treatment of the requirements process provides practical, step-by-step guidance. Given the impact of requirements specification on the success or failure of software products, the value of this timely book is tremendous. The generous examples supply the necessary concreteness for individuals and organizations to put the specific process into practice. Essential reading should also include a general requirements text, such as "Exploring Requirements" by Gause and Weinberg, before or in parallel with this book.
Comment 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
41 of 42 people found the following review helpful By Dean Waye on February 17, 2000
Format: Hardcover
This is the best book on requirements gathering I have ever read. When I finished it, I asked for and received the authors' permission to use the Volere template for a couple of test cases in my job (I specialize in requirements gathering) and have used it for one very large and another very famous client, with excellent results. While it doesn't especially lend itself to Internet projects, it significantly cuts down the time it takes me to gather requirements, and adds a level of consistency to the requirements documents my colleagues and I produce. Definitely worth the money.
Comment 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
37 of 39 people found the following review helpful By Christophe Addinquy on December 16, 1999
Format: Hardcover
For my own opinion, the best book on requirements! Even if it is based on Gause & Weinberg work on "exploring requirement", this book is about a very well formalized and described process for requirements. On each step, activities and artifacts are explained and true guidelines help you to achieve the work. Last but not least, you get two book in one: a user guide and a reference manual. If you had to build requirements (even with UML, like me), choose this book.
Comment 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
21 of 22 people found the following review helpful By Ken Quick on February 21, 2002
Format: Hardcover
I have been in the IT industry for 20 years and this is by FAR the best book on the Requirements Analysis process I've every seen. I've had it since it first came out, and have used the Volere process to successfully run several software development projects. They were all successful. Both the Design and Test teams LOVED the resultant Requirements Specification because they knew exactly what to code and exactly what to test to prove the requirements were met. My only complaint is that it takes a lot longer to document a Spec. to this degree of detail, but if you can convince "the powers that be" to take the time to do it, it will save a lot of time and expensive re-writes later.
Even if you don't use the Volere method to write your specs., it's worth the read for the knowledge gained on the analysis process itself.
Comment 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
20 of 21 people found the following review helpful By Mr. Rupert Ls Smith on December 17, 2004
Format: Hardcover
This is one of the best books on the subject of computer software development that I have ever read. The style is engaging and very creative; a pleasure to read. They explain something that I have tried to do many times myself but I was never quite able to hit the nail on the head until I encountered their ideas. I like this book because it has an abundance of ideas, most of them good. You can cut out what you don't want if their process is too elaborate for you, on a smaller project say. On larger projects it could well be a life saver. Read this book and you could well become the respected 'requirements genius' of your organisation, bringing direction where there was chaos.

Every software project I have ever worked on has had fundamentally the same problem; poor requirements. After reading this book my requirements documents were rated 9 or 10 out of 10 by a software development team. We had a traceable, understandable and very thorough process which enabled us to write the correct software straight off. Of course only an oracle can predict how requirements will change as your organisations business needs change so your requirements can still become wrong over time. The subject of changing requirements has been the focus of eXtreme Programming and other Agile methods; perhaps the authors might consider adding a chapter on how to integrate their process and template with Agile?

The chapter on 'Event Driven Use Cases' explains how to arrive at more innovative products by considering the product boundary. I really enjoyed this. Its very creative. Don't believe that having a fixed requirements process means that you will have a dull product. Quite the opposite, the authors show how the process can really support your own creativity and invention.
Read more ›
Comment 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
20 of 23 people found the following review helpful By R. Jones on March 9, 2002
Format: Hardcover
Wary of "star inflation?" Me too, yet this book gets five stars from me.
A very readable book, <i>Mastering...</i> gave me concrete guidelines for a topic that seems too nebulus at times. I read this book at the same time I was doing requirements gathering for a relatively simple project. This book caused me to make *specific* changes to our requirments document template and ask our customers questions I wouldn't have otherwise.
I think this book has just right amount of depth and detail to be read "in isolation" (of other books or prior experience) and help one do a competent job of requirements gathering. However, you the reader must do your part.
You'll have to cogitate just a little! Requirements gathering is thoughful process, not a science with rigid algorithms. There is no pretentious scientification in this book. And yes, "use case" is not given much more than a simple definition (although the concept is fundamental to the authors' process); but how many books do I need to read on <i>Use Case</i> to understand that a customer's business process can be divided into logical or physical modules, each of which in turn can be divided...
This book will give the novice what (s)he needs to actually do requirements gathering; and it definitely gave me points to ponder when doing my project. You won't be an expert after reading this book any more than you'll be a pro golfer after reading a book by Tiger Woods. Practice makes perfect! Reading this book is an <i>excellent</i> way to learn <i>what</i> to practice.
Comment 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

Customer Images

Most Recent Customer Reviews