RE: The Schematic Review: A Few Methods To The Madness

gervasi — Tue, 16 Aug 2011 03:05:13 GMT

I agree completely. It's so important to have a positive attitude. So when someone finds an error you can say jokingly, "I put that there to keep you 'vigilent when facing a sea of infomration'. I'm keeping you on your toes." I wouldn't really do that but it's so hard to have a bunch of people grill your design. The only thing harder is to find an error yourself on boad with several BGAs that cannot be easily fixed with cuts and jumpers, e.g. major footprint error, supplies shorted.

RE: The Schematic Review: A Few Methods To The Madness

DAB — Tue, 16 Aug 2011 00:03:02 GMT

Hi Dave,

You outlined a very good process. I might point out that the only difference from your process to a code review is the terminology. The key issues will always remain.

Does the circuit meet the products requirements?

Will the design be robust enough for later modifications?

Are there any threads through the control or data processing logic that do not make sense?

Are you using any hard to find or high demand components that could delay production? If so, what are the alternative parts?

Could you build the circuit with the data available? This one is key. If you do not understand the circuit well enough at the end of the review to say Yes to this question, then it is not ready to use.

Plus, I cannot overstress the need to get someone completely away from the project to do the review. You need those fresh eyes, always.

The only other thing I would add is that you should always hand out notebooks at the beginning of every project and stress that all of the design work be kept there. If nothing else, it gives you some insurance should one of your engineers be smashed up in a car wreck going to or from work. It happens, be proactive.

Thanks

DAB