More About Software Requirements: Thorny Issues and Practical Advice

Karl Wiegers

View sample pages

More About Software Requirements: Thorny Issues and Practical Advice

By Karl Wiegers
Available on demand
We'll put in a special order, which can take 2-3 weeks to reach you. This item cannot be returned unless it is defective, or there's been a mistake in fulfilling the order.
Don't wait. Order the eBook version instead.
Add to cart
Karl Wiegers
Published Date
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, 2nd 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

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.

Table of contents
  • 1 Requirements Engineering Overview
  • 2 Cosmic Truths About Software Requirements
  • 3 The Business Value of Better Requirements
  • 4 How Long Do Requirements Take?
  • 5 Estimating Based on Requirements
  • 6 The Myth of the On-Site Customer
  • 7 An Inquiry, Not an Inquisition
  • 8 Two Eyes Aren’t Enough
  • 9 Use Cases and Scenarios and Stories, Oh My!
  • 10 Actors and Users
  • 11 When Use Cases Aren’t Enough
  • 12 Bridging Documents
  • 13 How Much Detail Do You Need?
  • 14 To Duplicate or Not to Duplicate
  • 15 Elements of Requirements Style
  • 16 The Fuzzy Line Between Requirements and Design
  • 17 Defining Project Scope
  • 18 The Line in the Sand
  • 19 The Six Blind Men and the Requirements
  • 20 Handling Requirements for Multiple Releases
  • 21 Business Requirements and Business Rules
  • 22 Measuring Requirements
  • 23 Exploiting Requirements Management Tools