Re: Best Practices for Hardware Engineers
- From: nico@xxxxxxxxxxx (Nico Coesel)
- Date: Wed, 31 May 2006 16:10:28 GMT
jjlindula@xxxxxxxxxxx wrote:
Hello, I have a list of Best Practices for Hardware Engineers that I
would like anyone to look over and tell me what you think or what
should be added to the list.
Here is my list in no particular order
1. Always have a top block diagram, in your schematics and in your FPGA
code
2. Follow the System Engineering Design Process Model
3. Document, Document, Document your work
4. Modularize your work
5. Try a Top Down design approach instead of Bottom Up
6. Ask for Peer Reviews and code walk throughs
7. If a standard exits then follow it.
8. Manage time, don't let time manage you.
I'm missing an important one:
Test whether each module you make works as expected with any input
combination. Design modules to deal with faulty input properly
--
Reply to nico@nctdevpuntnl (punt=.)
Bedrijven en winkels vindt U op www.adresboekje.nl
.
- References:
- Best Practices for Hardware Engineers
- From: jjlindula
- Best Practices for Hardware Engineers
- Prev by Date: Re: Making piezo louder
- Next by Date: Re: Best Practices for Hardware Engineers
- Previous by thread: Re: Best Practices for Hardware Engineers
- Next by thread: Re: Best Practices for Hardware Engineers
- Index(es):