Technical Document Review for the Enterprise - PeerReview Complete
We are excited to bring our peer review tool to a much wider audience. It isn’t just for code anymore!
With PeerReview Complete, enterprise users can bridge the gap between software and hardware engineering teams. We’ve made this a single solution to effectively conduct reviews of all artifacts during an entire product development lifecycle.
Over and over again, peer reviews have been proven to improve the overall quality of the final product, a key factor in customer satisfaction. Our PeerReview Complete solution can enable widely distributed cross-functional teams to review design documents, software source code, images, schematics, and hardware description languages – among other artifacts. Pretty much: If you can create a document, we can help you work with your colleagues to review it.
Based on our research and what our customers tell us, the embedded development community has traditionally been underserved in regard to having an effective tool for embedded systems review. Reviews are either not done, or they are done grudgingly due to the nature of formal inspections which consist of long, laborious meetings marking up printed documents or schematics. With PeerReview Complete, our years of experience in making software code reviews easy and fun can now be applied to the hardware world. We all know that the tasks that are easy and fun make people more likely to participate, and that generates real value for the company.
As Christof Ebert and Capers Jones’ noted in their recent article, “Embedded Software: Facts, Figures, and Future,” published by the IEEE Computer Society, there are numerous technical document and code review techniques each with their own level of effectiveness. I highlighted in bold the areas where companies can use PeerReview Complete to achieve those terrific results.
The list below is ranked by defect removal effectiveness based on percent of defects removed.
- 87% static code analysis (“lint” tools, removing compiler warnings)*
- 85% design inspection
- 85% code inspection
- 82% quality function deployment (requirements analysis used by auto makers)
- 80% test plan inspection
- 78% test script inspection
- 77% document review (documents that aren’t code, design, test plans)*
- 75% pair programming (review aspect)
- 70% bug repair inspection
- 65% usability testing*
- 50% subroutine testing
- 45% SQA (Software Quality Assurance) review*
- 40% acceptance testing*
* means this is an exceptionally productive technique (more than 750+ function points/month)
Take a look: You might find that peer reviews can also be fun!
Join us on Tuesday, August 16, 2011 at 1 p.m. ET for a special Webinar introduction to PeerReview Complete in, Reducing Technical Document Review Times and Improving Quality.