IDEAS

DOCUMENT EXAMPLES

Now we're ready to look at some examples of documentation from the electrical hardware design and testing phases of a development project. Keep in mind that similar documents need to be considered for the other product development phases such as:

  • PRODUCTS REQUIREMENTS and VALIDATION TESTING

  • SYSTEM DESIGN and VERIFICATION TESTING

  • OTHER HARDWARE DESIGN and TESTING (e.g. cables/harnesses, RF & IR interfaces, mechanical components; and industrial design & human factors, etc…)

  • SOFTWARE & FIRMWARE DESIGN and TESTING

  • PRODUCTION & SUPPORT DESIGN and TESTING
The tables below show examples of documents that are prudent to develop and maintain during the various product development efforts. It's advisable is to be concise and limit documentation to that which is required by (1) the various Groups-of-Influence or (2) the Guidelines-Of-Business. By applying these gauges you will eliminate a document bureaucracy (or at least keep it to a manageable minimum).

It's important to determine the documents that are required at the start of the product development process as best you can, and then assign the responsibility, budget and timeline for generating them.


 
JUMP TO PAGE
1 2 3 4 5 6 7 8 9 10 11 12

©2002 Richard M. (Dick) Haney
BACK TO: RICHARD (DICK) HANEY   IDEAS