Tip

Mastering the Requirements Process, 2nd Edition: Chapter 2, The Requirements Process

Suzanne Robertson and James Robertson

As a registered member of SearchSoftwareQuality.com, you're entitled to a complimentary copy of Chapter 2 of Mastering the Requirements Process, 2nd Edition written by Suzanne Robertson and James Robertson and published by Addison Wesley Professional. "The Requirements Process"

    Requires Free Membership to View

outlines the basic requirements process, from blastoff to reuse. This chapter breaks down project types so readers can find customize the information to their specific needs. A detailed chart and graphics guide the reader.



Book description:

It is widely recognized that incorrect requirements account for up to 60% of errors in software products, and yet the majority of software development organizations do not have a formal requirements process. Many organizations appear willing to spend huge amounts on fixing and altering poorly specified software, but seem unwilling to invest a much smaller amount to get the requirements right in the first place.

Mastering the Requirements Process, Second Edition, sets out an industry-proven process for gathering and verifying requirements with an eye toward today's agile development environments. In this total update of the bestselling guide, the authors show how to discover precisely what the customer wants and needs while doing the minimum requirements work according to the project's level of agility.

Features include

  • The Volere requirements process -- completely specified, and revised for compatibility with agile environments.
  • A specification template that can be used as the basis for your own requirements specifications.
  • New agility ratings that help you funnel your efforts into only the requirements work needed for your particular development environment and project.
  • How to make requirements testable using fit criteria.
  • Iterative requirements gathering leading to faster delivery to the client.
  • Checklists to help identify stakeholders, users, nonfunctional requirements, and more.
  • Details on gathering and implementing requirements for iterative releases.
  • An expanded project sociology section for help with identifying and communicating with stakeholders.
  • Strategies for exploiting use cases to determine the best product to build.
  • Methods for reusing requirements and requirements patterns.
  • Examples showing how the techniques and templates are applied in real-world situations.
  • >> Read Chapter 2: The Requirements Process.

    >> Buy the book




    This chapter is excerpted from the book, Mastering the Requirements Process, 2nd Edition, authored by Suzanne Robertson and James Robertson, published by Addison-Wesley Professional, March, 2006, Copyright Pearson Education, Inc. ISBN 0321419499. For more information please visit: www.awprofessional.com

    This was first published in December 2007

    There are Comments. Add yours.

     
    TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

    REGISTER or login:

    Forgot Password?
    By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
    Sort by: OldestNewest

    Forgot Password?

    No problem! Submit your e-mail address below. We'll send you an email containing your password.

    Your password has been sent to:

    Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.