HomeGroupsTalkZeitgeist
Hide this

Results from Google Books

Click on a thumbnail to go to Google Books.

More About Software Requirements: Thorny…
Loading...

More About Software Requirements: Thorny Issues and Practical Advice

by Karl E. Wiegers

MembersReviewsPopularityAverage ratingConversations
117None103,116 (3.94)None

None.

None
Loading...

Sign up for LibraryThing to find out whether you'll like this book.

No current Talk conversations about this book.

No reviews
no reviews | add a review
You must log in to edit Common Knowledge data.
For more help see the Common Knowledge help page.
Series (with order)
Canonical title
Original title
Alternative titles
Original publication date
People/Characters
Important places
Important events
Related movies
Awards and honors
Epigraph
Dedication
First words
Quotations
Last words
Disambiguation notice
Publisher's editors
Blurbers
Publisher series
Original language

References to this work on external resources.

Wikipedia in English (1)

Book description
Haiku summary

Amazon.com Product Description (ISBN 0735622671, Paperback)

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

(retrieved from Amazon Thu, 12 Mar 2015 18:16:00 -0400)

No library descriptions found.

Quick Links

Swap Ebooks Audio
10 wanted

Popular covers

Rating

Average: (3.94)
0.5
1
1.5
2
2.5
3 2
3.5 1
4 4
4.5
5 2

Is this you?

Become a LibraryThing Author.

 

About | Contact | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 119,425,010 books! | Top bar: Always visible