Embedded-software applications are complex and often difficult to debug. By including peer review as part of the product development process companies can make sure they catch defects early, minimize the impact of delays, maximize team productivity and improve overall product quality.
In their recent article "Embedded Software: Facts, Figures, and Future" 1 Christof Ebert and Capers Jones, quantified the most effective practices to improve Embedded Software quality (see list below). Many of the techniques identified in the article involve inspecting and reviewing technical documents and code, something that PeerReview Complete is designed to accomplish.
We’ve highlighted in BOLD the areas where companies can use PeerReview Complete for reviews.
Ranked by defect removal effectiveness in percent 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 exceptionally productive technique (more than 750+ function points/month)
1Christof Ebert, Capers Jones, "Embedded Software: Facts, Figures, and Future," Computer, vol. 42, no. 4, pp. 42-52, Apr. 2009, doi:10.1109/MC.2009.118