Re: Best Practices for Hardware Engineers


John Larkin wrote:
On 31 May 2006 07:47:26 -0700, "Luhan" <luhanis@xxxxxxxxx> wrote:


jjlindula@xxxxxxxxxxx wrote:

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 don't get much out of your list, here is mine...

1. Make sure your client knows what he's getting into - time, money,
problems, etc.
2. Dont use any parts that the sales reps say are replacing the current
ones.
3. Document only as much as you need for yourself, offer extensive
documentationt to the client after the project is done. Let them pay
for as much as they want.
4. Check out the convetional solutions, use only as they apply.
5. Dont take on any project unless you have it mostly designed already.



6. Write the manual first.

Hey, thats a good one. I wrestled back and forth with one client for
weeks as they gave me vague and conflicting functions for the product.
Maybe, let *them* write the manual first!

Luhan

.

Relevant Pages

  • Re: Finding records with a form
    ... The search functions start with a label with a yellow background (I could ... Both combo boxes would show both Client and LoanNo in them. ... it's been fun transmitting some of my forms design paradigm. ...
    (microsoft.public.access.formscoding)
  • Re: A Design Problem
    ... to improve my OO design skills (should be easy to ... I want to provide a set of C++ classes which will enable client (of ... -> In each toolbar there will be some tools. ... a Tool does not have so the exception is unnecessary. ...
    (comp.object)
  • Re: TDD and Refactoring
    ... Given a design with more than one poor qualities, ... > refactor that gives a small but leading benefit. ... Been doing that on the GUI, where it makes a real difference. ... and divert that single client to use the new model. ...
    (comp.object)
  • Re: TDD and Refactoring
    ... Given a design with more than one poor qualities, ... refactor that gives a small but leading benefit. ... somethingand somethingElse() are candidates for the "Introduce ... and divert that single client to use the new model. ...
    (comp.object)
  • Re: Joes AsyncSocket Example
    ... data across the thread boundary and pushesit on the socket. ... the point of Joe's example was how to use CAsyncSocket ... According to this design, the winsock stack converts network events ... there's nothing in the code that limits a client in any way. ...
    (microsoft.public.vc.mfc)