The product was added. Continue shopping or proceed to checkout. You can also view a cart summary above on the right.

Recommended Books

The following books are in alphabetical order by title and do not represent an order of preference. Each book title is underlined and includes a hyperlink so that you can view the book in more detail.

The Quest for Software Requirements is a handbook of probing questions for eliciting nonfunctional requirements, as well as, proven techniques and tips for engaging the right stakeholders. (Roxanne Miller, MavenMark Books, 2009).
Software Requirements Questions is a companion to The Quest for Software Requirements.  This CD contains the 2,000+ elicitation questions formatted in an editable Microsoft Excel file to help you customize requirements-gathering interviews. (Roxanne Miller, Requirements Quest, 2009).
Business Analysis Body of Knowledge (BABOK®) presents 32 business analysis tasks grouped into 6 knowledge areas, and describes 34 business analysis techniques that might be applied when performing the tasks.  Every business analysis professional should have a copy.  International Institute of Business Analysis (IIBA®), 2009, version 2.0.
No image available Business Rule Book contains very good descriptions of the types of business rules and how they are related.  Business Rules are a key starting point for gathering requirements.  (Ronald G. Ross, Business Rule Solutions, Incorporated; 2nd edition 1997).
Capability Maturity Model Integration, 2nd Edition provides an overview into the Software Engineering Institute’s (SEI) Capability Maturity Model Integration (CMMI), which was first developed by Watts Humphrey.  (Mary Beth Chrissis, Mike Konrad, and Sandy Shrum, 2007).
Competitive Engineering is a handbook for systems engineering, requirements engineering, and software engineering using Planguage. (Tom Gilb, Elsevier Butterworth-Heinemann, 2005).
Complete Systems Analysis provides a great tutorial about analyzing systems. (James & Suzanne Robertson, Dorset House, 1994).
Customer-Centered Products: Creating Successful Products Through Smart Requirements Management is a clearly written book on requirements targeted at managers. (Ivy F. Hooks and Kristin A. Farry, AMACOM, 2001).
No image available Data Modeling Made Easy is a book that does an excellent job of illustrating the way to breakdown data modeling into a simplified process.  (Gary Rush, MGR Consulting, Inc., 2007).
Discovering Requirements describes how to specify products and services. (Ian Alexander & Ljerka Beus-Dukic, John Wiley & Sons, 2009).
Exploring Requirements: Quality Before Design is the number one book—a classic—for anyone interested in understanding requirements. (Gerald Weinberg & Don Gause, Dorset House, 1989).
Managing Software Requirements, Second Edition – A Use Case Approach is a must read for every practitioner. (Dean Leffingwell and Don Widrig, Addison-Wesley, 2003).
Mastering the Requirements Process, 2nd Edition describes a detailed process for gathering and verifying requirements. (Suzanne Robertson and James Robertson, Addison-Wesley, 2006).
Patterns for Effective Use Cases presents many suggestions for how to effectively apply use cases for developing user requirements. (Steve Adolph and Paul Bramble, Addison-Wesley, 2003).
Project Requirements provides straightforward, practical, and commonsense advice for project managers. (Ralph Young, Mangement Concepts, 2006).
Requirements by Collaboration: Workshops for Defining Needs provides a comprehensive and practical approach to holding effective requirements-gathering workshops with users. (Ellen Gottesdiener, Addison-Wesley, 2002).
A Requirements Pattern: Succeeding in the Internet Economy provides clear role definitions, and numerous possible elicitation questions. (Patricia L. Ferdinandi, Addison-Wesley, 2002).
Software Requirement Patterns takes a fresh look at the use of patterns by applying the concept to requirements management.  (Stephen Withall, Microsoft, 2007).
Software Requirements, 2nd Edition is an excellent book for both the novice and the expert Requirements Engineer. (Karl Wiegers, Microsoft, 2003).
The Software Requirements Memory Jogger is a pocket guide to help software and business teams develop and manage requirements.  (Ellen Gottesdiener, Goal/QPC, 2007).
Use Cases: Requirements in Context provides the Requirements Engineer with an approach to documenting requirements using a process based on use cases. (Daryl Kulak and Eamonn Guiney, Addison-Wesley, 2000).
Writing Effective Use Cases is a good book for engineers who want to capture the behavioral requirements of software systems. (Alistair Cockburn, Addison-Wesley, 2001).