Customer Reviews for

Mastering the Requirements Process

Average Rating 4
( 5 )
Rating Distribution

5 Star

(2)

4 Star

(2)

3 Star

(0)

2 Star

(1)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com 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 & Noble.com 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 & Noble.com 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 BN.com 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

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com 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 BN.com. 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 – 4 of 5 Customer Reviews
Page 1 of 1
  • Anonymous

    Posted May 24, 2006

    a sociological text

    [A review of the SECOND EDITION, 2006.] The main context of this book is for software projects. If you are reading these words, you probably hail from that environment. But the authors do explain that the processes they describe are applicable to almost any project. This is not a software book, per se. Not a line of code appears here, as far as I can tell. Most programmers know that design is important, and should usually precede any coding. The book's contribution is about that design and its prelude. Namely the gathering and determination of what the requirements might be. The authors point out that this makes the book in no small part a sociological text. About how to get a group of people together, and to solicit their contributions and perceptions into the project's requirements. Managing the dynamics of this is the purview of sociology [and psychology]. Without a solid performance here, subsequent design and coding may rest on quicksand. The book does acknowledge that recent technological innovations like blogs and wikis can lead to quicker feedback. And hence contribute to a more interactive and iterative scenario of updating requirements as the project proceeds. All in the Agile spirit that many teams are now using. Just remember that the blogs and wikis are not a substitute for physically getting the team together. Much of the dynamics and feedback in the processes given by the book do really require that physical presence, to enhance the members' contributions.

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

    Posted March 17, 2010

    No text was provided for this review.

  • Anonymous

    Posted February 19, 2010

    No text was provided for this review.

  • Anonymous

    Posted October 18, 2011

    No text was provided for this review.

Sort by: Showing 1 – 4 of 5 Customer Reviews
Page 1 of 1