Software Requirements 3

( 2 )


Now in its third edition, this classic guide to software requirements engineering has been fully updated with new topics, examples, and guidance. Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development and management activities on software projects.
• Describes practical, effective, field-tested techniques for managing the requirements engineering ...

See more details below
Paperback (Third Edition)
$32.68 price
(Save 27%)$44.99 List Price

Pick Up In Store

Reserve and pick up in 60 minutes at your local store

Other sellers (Paperback)
  • All (17) from $25.19   
  • New (13) from $26.08   
  • Used (4) from $25.19   
Software Requirements

Available on NOOK devices and apps  
  • NOOK Devices
  • Samsung Galaxy Tab 4 NOOK 7.0
  • Samsung Galaxy Tab 4 NOOK 10.1
  • NOOK HD Tablet
  • NOOK HD+ Tablet
  • NOOK eReaders
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac
  • NOOK for Web

Want a NOOK? Explore Now

NOOK Book (eBook)
$19.99 price
(Save 44%)$35.99 List Price


Now in its third edition, this classic guide to software requirements engineering has been fully updated with new topics, examples, and guidance. Two leaders in the requirements community have teamed up to deliver a contemporary set of practices covering the full range of requirements development and management activities on software projects.
• Describes practical, effective, field-tested techniques for managing the requirements engineering process from end to end.
• Provides examples demonstrating how requirements "good practices" can lead to fewer change requests, higher customer satisfaction, and lower development costs.
• Fully updated with contemporary examples and many new practices and techniques.
• Describes how to apply effective requirements practices to agile projects and numerous other special project situations.
• Targeted to business analysts, developers, project managers, and other software project stakeholders who have a general understanding of the software development process.
• Shares the insights gleaned from the authors' extensive experience delivering hundreds of software-requirements training courses, presentations, and webinars. New chapters are included on specifying data requirements, writing high-quality functional requirements, and requirements reuse. Considerable depth has been added on business requirements, elicitation techniques, and nonfunctional requirements. In addition, new chapters recommend effective requirements practices for various special project situations, including enhancement and replacement, packaged solutions, outsourced, business process automation, analytics and reporting, and embedded and other real- time systems projects.

Read More Show Less

Product Details

  • ISBN-13: 9780735679665
  • Publisher: Microsoft Press
  • Publication date: 8/23/2013
  • Series: Developer Best Practices Series
  • Edition description: Third Edition
  • Edition number: 3
  • Pages: 672
  • Sales rank: 248,340
  • Product dimensions: 8.80 (w) x 7.30 (h) x 1.40 (d)

Meet the Author

Joy Beatty, a leader in the software requirements community, has trained thousands of business analysts and helped major organizations build business-analysis centers of excellence. She is coauthor of Visual Models for Software Requirements.

Read More Show Less

Table of Contents



Software requirements: What, why, and who

Chapter 1: The essential software requirement

Chapter 2: Requirements from the customer’s perspective

Chapter 3: Good practices for requirements engineering

Chapter 4: The business analyst

Requirements development

Chapter 5: Establishing the business requirements

Chapter 6: Finding the voice of the user

Chapter 7: Requirements elicitation

Chapter 8: Understanding user requirements

Chapter 9: Playing by the rules

Chapter 10: Documenting the requirements

Chapter 11: Writing excellent requirements

Chapter 12: A picture is worth 1024 words

Chapter 13: Specifying data requirements

Chapter 14: Beyond functionality

Chapter 15: Risk reduction through prototyping

Chapter 16: First things first: Setting requirement priorities

Chapter 17: Validating the requirements

Chapter 18: Requirements reuse

Chapter 19: Beyond requirements development

Requirements for specific project classes

Chapter 20: Agile projects

Chapter 21: Enhancement and replacement projects

Chapter 22: Packaged solution projects

Chapter 23: Outsourced projects

Chapter 24: Business process automation projects

Chapter 25: Business analytics projects

Chapter 26: Embedded and other real-time systems projects

Requirements management

Chapter 27: Requirements management practices

Chapter 28: Change happens

Chapter 29: Links in the requirements chain

Chapter 30: Tools for requirements engineering

Implementing requirements engineering

Chapter 31: Improving your requirements processes

Chapter 32: Software requirements and risk management


Current requirements practice self-assessment

Requirements troubleshooting guide

Sample requirements documents


About the authors

Read More Show Less

Customer Reviews

Average Rating 5
( 2 )
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 all of 2 Customer Reviews
  • Anonymous

    Posted February 14, 2014

    What I love about this book is that it is so easy to pick this u

    What I love about this book is that it is so easy to pick this up, get several great ideas on how to fix whatever kind of problem you are facing in software development, and then use those ideas to implement something today that is really going to make a difference in what you can deliver to your customers. Wiegers and Beatty give pragmatic examples and “oops” stories on everything from Agile and analytics through real-time embedded systems that demonstrate the key points you need to know to make your project successful. The book also includes templates, tips, and project-specific details to help you use what you learn.
    I have used the second edition of this book to help me work with software teams on problems ranging from reducing defects and increasing consulting revenue through implementing industry-standard requirements such as PCI. The third edition of the book builds on the second by increasing its coverage on topics such as dashboard reporting, data requirements, and data modeling. The book is meant to be read cover-to-cover but you can still get a lot out of it by reading what you need, as you need it.
    My favorite section in this third edition is the expanded discussion on quality attributes. This is an area that is so often overlooked in software development because we tend to assume the best and forget to plan for the worst. This section explains the different types of quality controls and how to know which ones to use based on the type of project you are working on. The authors do a great job throughout the book in explaining how to gracefully handle software errors to keep your data, users, and possibly your customers safe from harm.

    Was this review helpful? Yes  No   Report this review
  • Anonymous

    Posted October 16, 2013

    I highly recommend buying, reading and adopting the many require

    I highly recommend buying, reading and adopting the many requirements engineering best practices found in this 3rd edition of Software Requirements. Karl Wiegers and Joy Beatty have written an excellent guide for all stakeholders of software application development. This includes business analysts, QA/testers, software developers, infrastructure developers, program/project managers, project sponsors and very importantly the business stakeholders who possess the requirements that will be elicited and then managed. Everyone will read this book from their role’s point of view and will learn how to work synergistically in the pursuit of eliciting and leveraging excellent requirements.

    I am pleased that the structure and content of the book remains similar to that of the second edition. The emphasis is on readability and practicality, giving readers the tools and techniques needed to deal successfully with requirements on a wide variety of projects. Karl and Joy have incorporated their collective knowledge gained and lessons learned from years of delivering many training courses, conference presentations, and webinars on requirements to thousands of students. Many of us that read the 1st edition of Software Requirements have collaborated with Karl through the years and offered our thoughts on contemporary requirements engineering best practices. Many of those thoughts are also present in this 3rd edition.

    Those associated with the International Institute for Business Analysis (IIBA) will be pleased that this edition aligns with terminology from the BABOK where appropriate and sensible.

    Agile, incremental and iterative development methods are addressed effectively and more guidance is given to how to handle requirements on agile projects. There is an entire chapter on this now and the other relevant chapters have guidance on how to adopt the practices described in the chapter to agile projects. Use cases and user stories are addressed as well.

    Another improvement from the 2nd edition is more emphasis on defining data and reporting requirements.

    I have been associated with software development for over 40 years now. I have been preaching and teaching requirements engineering for many of those years. The book Software Requirements remains central to my thoughts on requirements engineering processes, deliverables and techniques. The reason I am aligned to this book lies in what I believe is the core focus of its content: To promise and deliver to the business, on time and within budget, innovative software that meets end user needs and expectations requiring minimal rework and maintenance.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing all of 2 Customer Reviews

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