More about Software Requirements: Thorny Issues and Practical Advice

Paperback (Print)
Rent from
(Save 59%)
Est. Return Date: 07/22/2015
Buy Used
Buy Used from
(Save 41%)
Item is in good condition but packaging may have signs of shelf wear/aging or torn packaging.
Condition: Used – Good details
Used and New from Other Sellers
Used and New from Other Sellers
from $1.99
Usually ships in 1-2 business days
(Save 93%)
Other sellers (Paperback)
  • All (34) from $1.99   
  • New (14) from $5.54   
  • Used (20) from $0.00   


No matter how much instruction you’ve had on managing software requirements, there’s no substitute for experience. Too often, lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book, Software Requirements, Second Edition, requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book.

With straightforward, professional advice and practical solutions based on actual project experiences, this book answers many of the tough questions raised by industry professionals. From strategies for estimating and working with customers to the nuts and bolts of documenting requirements, this essential companion gives developers, analysts, and managers the cosmic truths that apply to virtually every software development project.

Discover how to:

  • Make the business case for investing in better requirements practices
  • Generate estimates using three specific techniques
  • Conduct inquiries to elicit meaningful business and user requirements
  • Clearly document project scope
  • Implement use cases, scenarios, and user stories effectively
  • Improve inspections and peer reviews
  • Write requirements that avoid ambiguity

Read More Show Less

Editorial Reviews

From Barnes & Noble
The Barnes & Noble Review
For years, developers who are serious about building the right software have treasured Karl Wiegers’s classic Software Requirements. Since then, they’ve asked the “guru” plenty of questions. In More About Software Requirements, Wiegers identifies the most important of those questions, and offers realistic, highly workable answers.

For instance: How do you keep too much design from being embedded in your requirements? What questions work best in requirements interviews? How do you get your customers to actually review the spec? What metrics will help you determine how well you’re doing in writing requirements? What’s the best way to define project scope? How do you get your money’s worth from requirements tools? What best practices exist for managing requirements across multiple releases?

Wiegers’s advice is relentlessly practical. Something in here will save your bacon -- likely, more than once! Bill Camarda, from the February 2006 Read Only

Read More Show Less

Product Details

  • ISBN-13: 9780735622678
  • Publisher: Microsoft Press
  • Publication date: 1/17/2006
  • Edition description: REV
  • Pages: 224
  • Sales rank: 989,140
  • Product dimensions: 7.40 (w) x 8.80 (h) x 0.70 (d)

Meet the Author

Karl E. Wiegers is a leading speaker, author, and consultant on requirements engineering, project management, and process improvement. As Principal Consultant with Process Impact, he conducts training seminars for corporate and government clients worldwide. Karl has twice won the Software Development Productivity Award, which honors excellence in productivity-enhancing products and books.

Read More Show Less

Table of Contents

Praise for More About Software Requirements: Thorny Issues and Practical Advice



Part I: On Essential Requirements Concepts

Chapter 1: Requirements Engineering Overview

Chapter 2: Cosmic Truths About Software Requirements

Part II: On the Management View of Requirements

Chapter 3: The Business Value of Better Requirements

Chapter 4: How Long Do Requirements Take?

Chapter 5: Estimating Based on Requirements

Part III: On Customer Interactions

Chapter 6: The Myth of the On-Site Customer

Chapter 7: An Inquiry, Not an Inquisition

Chapter 8: Two Eyes Aren’t Enough

Part IV: On Use Cases

Chapter 9: Use Cases and Scenarios and Stories, Oh My!

Chapter 10: Actors and Users

Chapter 11: When Use Cases Aren’t Enough

Part V: On Writing Requirements

Chapter 12: Bridging Documents

Chapter 13: How Much Detail Do You Need?

Chapter 14: To Duplicate or Not to Duplicate

Chapter 15: Elements of Requirements Style

Chapter 16: The Fuzzy Line Between Requirements and Design

Part VI: On the Requirements Process

Chapter 17: Defining Project Scope

Chapter 18: The Line in the Sand

Chapter 19: The Six Blind Men and the Requirements

Part VII: On Managing Requirements

Chapter 20: Handling Requirements for Multiple Releases

Chapter 21: Business Requirements and Business Rules

Chapter 22: Measuring Requirements

Chapter 23: Exploiting Requirements Management Tools


Appendix : About the Author

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star


4 Star


3 Star


2 Star


1 Star


Your Rating:

Your Name: Create a Pen Name or

Barnes & Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation


  • - By submitting a review, you grant to Barnes & and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Terms of Use.
  • - Barnes & reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Reviews
  • Posted April 7, 2011

    Highly Recommended

    What an easy read this was! Lots of information packed in this book in easy to understand terms. I was able to read this book in one afternoon and feel like I have a better understanding of how to gather software requirements effectively.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)