1. Common mistakes III and exemplary work samples Please don’t take offense if examples are taken from your report.

2. Importance of a quality report One of the main deliverables of an engineer is their report. The report must be technically correct as others (engineers, technicians, managers, accountants, etc.) will rely on this information. Schematics and bills of material must reflect the circuit that was built. Equations, test results, test setups, etc. must be correct and complete. Errors (technical and other) degrade the value of the report and its underlying work.

3. Common mistakes Report should not document chronology of process (like a diary) Instead the report should cover the various elements of the design, providing background detail where needed (e.g., when a new device or technology is introduced) Do not describe design process Create new project in Pspice Place a V sin voltage in Pspice Connect voltage regulator … Simulate under range of load resistors Such instructions would go into a design guide but not a project report

4. Common mistakes Missing, incorrect, or incomplete schematics

5. Common mistakes Missing, incorrect, or incomplete schematics

6. Common mistakes Missing, incorrect, or incomplete schematics

7. Common mistakes Errors in plotting data

8. Common mistakes Equation errors Use the equation editor Use superscripts and subscripts Should be ( )

9. Commendable examples

10. Quality photographs document the well-organized circuit assembly.

11. Commendable examples Inclusion of a Bill of materials is a good practice voltage

12. Commendable examples But double check your work

13. Commendable examples Diagram illustrating test setup instead of long wordy description.

14. Commendable examples Clear and readable figure

15. Commendable examples

16. Example of very good abstracts Provides concise project overview and states key performance features.