|
One of the critical activities in design verification is the design review, often with the aid of physical prototypes of the design. The value of reviewing a design seems obvious, but exactly how should I go about design reviews to get maximum value out of them? What constitutes a good review plan, and when should I do this planning? How should I conduct the actual reviews? What should I do before, during, and after the review? Our team seems to spend a lot of time in heated discussions during reviews -- how can I make review time more productive and less disruptive? Are there any special review techniques for software designs? For software code? It seems a lot cheaper to find design and code defects in a review than during testing -- how can I maximize the detection of defects during reviews?
|
©Copyright 2000-2008 Emprend, Inc. All Rights Reserved.
About us Site Map View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy