Movies Books Music Food Tv Shows Technology Politics Video Games Parenting Fashion Green Living more >


Peer review works: it leads to better software. But implementing peer review can be challenging -- for technical, political, social, cultural, and psychological reasons. In this book, best-selling software engineering author Karl Wiegers presents succinct, easy-to-use techniques for formal and informal software peer review, helping project managers and developers choose the right approach and implement it successfully. Wiegers begins by discussing the cultural and social aspects of peer review, and reviewing several formal and informal approaches: their implications, their challenges, and the opportunities they present for quality improvement. The heart of the book is an in-depth look at the "nuts and bolts" of inspection, including the roles of inspectors, planning, examining work products, conducting code review meetings; improving the inspection process, and achieving closure. Wiegers presents a full chapter on metrics, and then addresses the process and political challenges associated with implementing successful software review programs. The book concludes with solutions to special review challenges, including large work products and software created by distributed development teams. For all developers, project managers, business analysts, quality engineers, testers, process improvement leaders, and documentation specialists.
edit this info


ISBN-10:  0201734850
ISBN-13:  978-0201734850
Author:  Karl E. Wiegers
Publisher:  Addison-Wesley Professional
What's your opinion on Peer Reviews in Software: A Practical Gu...?
1 rating: +5.0
You have exceeded the maximum length.
More Peer Reviews in Software: A Pr... reviews
review by . March 22, 2002
Every developer I have known has experienced the phenomena of spending an inordinate amount of time searching for a bug only to have a colleague look at the code and find it almost immediately. Study after study has indicated that the worst review process for software is self-criticism and the best is to have other coders take a good look at it. Therefore, it is logical that a formal process for developers reviewing each others code be implemented. The problem is that the former is informal, making …
Peer Reviews in Software: A Practical Guide
Related Topics
Dear John

A book by Nicholas Sparks

Little Women

A book by Louisa May Alcott and Susan Straight

Fight Club: A Novel

A 1996 book by Chuck Palahniuk.

First to Review
© 2014 Lunch.com, LLC All Rights Reserved
Lunch.com - Relevant reviews by real people.
This is you!
Ranked #
Last login
Member since