1. ECE445: The Design Review Raj Vinjamuri February 3, 2014

2. Pro Tip: Be Organized!  Always look ahead in the calendar  Organize a central repository for your team (Box/OneDrive/DropBox/Drive/Blue Waters/etc.)  Version control documents and code  Hope for the best, plan for the worst –Price, lead time, design margins, etc.  Document your progress throughout –Video and pictures are great for a portfolio!

3. What the Design Review is  Structured discussion of your entire project  Defense of the complete electrical design  Design Review should be a stand alone document  ‘Requirements and Verification’ section is thought through and thorough

4. What the Design Review is NOT  Do not prepare a PowerPoint  Do not dress up  Do not bring in or demonstrate any hardware  Do not bring datasheets for all the parts you use

5. Administrative  Mock DR 2/18 - 2/19 (sign-ups open 2/11)  DR week of 2/23 (sign-ups open 2/16) –Don’t forget to sign up to peer-review another project  Grading rubric on the website  Description on the website  Look at design reviews from past award- winning projects

6. Structure/Sections of the Document  Modular Block Diagrams  Written descriptions of each block –Similar to proposal, but now includes the detailed design –Circuit diagrams, design calculations, circuit simulations –Flow charts for software and algorithms  Requirements and Verifications  Tolerance Analysis  Cost analysis (parts and labor)  Schedule  Ethics and Safety  Citations and References

7. Block Diagrams  High level overview of components  Break into sub-blocks if necessary  Clarity is important  Not a flowchart

8. Block Diagrams Examples and Considerations Growing Degree Day Monitor, Spring 2014

9. Block Diagrams Examples and Considerations cont. Ski Computer, Spring 2014

10. Block Descriptions  Similar to proposal, but includes detailed design  Justify your design  Reference your schematics (see schematics lecture)  Flowcharts for software and control  Calculations and simulations –Equations and their application –Design feasibility

11. Flowcharts Goo d Bad  Clearly labeled  All decision paths shown  No unnecessary information

12. Calculations and Simulations  Power budget  Link budget  Calculations for component values  Simulations of circuit designs

13. Calculations and Simulations cont.

14. Requirements and Verification  Requirements –Quantitative operational requirements –Break down into sub-requirements if necessary

15. Requirements and Verification cont.  Verification –Method to confirm each requirement –Checklist of acceptable results, quantitative –Debugging plan –“Make sure it works” is not a verification

16. Requirements and Verification cont.  Assign 100 points across all requirements. –This will be used as a rubric for your team.  Break down functionality into requirements and what is needed to fulfill the separate requirements

17. Tolerance Analysis  A part of the design process, not just a test procedure  R/V Table is a guide to goals of tolerance analysis  Actual test procedure in a separate section outside the R&V table

18. Cost Analysis  Bill of Materials (BOM) –Specific part numbers & component values –Module that uses it –Price and quantity  Labor costs

19. Schedule  Week-by-Week  Break down tasks  Assign responsibility  Stick to it

20. Ethics  IEEE code of ethics –Do not just copy/paste this into your paper –Know and understand it –http://www.ieee.org/about/corporate/governance/p7-8.htmlhttp://www.ieee.org/about/corporate/governance/p7-8.html  Discuss ethical concerns as they apply to your project  If no ethical concerns, justify yourself

21. Safety  Discuss safety concerns –Electrical safety –Mechanical safety –Lab safety –Consider safety of both yourselves and end users –Make a safety plan if necessary –If few safety concerns, justify yourself  If you have hazardous, or volatile elements of your project, you must create a “Lab Safety Manual”

22. Citations and References  List of references formatted using the IEEE standard –http://www.ieee.org/documents/ieeecitationref. pdfhttp://www.ieee.org/documents/ieeecitationref. pdf  Should include things like… –Textbooks or datasheets where you got design equations –Informative articles or tutorials used –IEEE code of ethics

23. Questions?  Mock DR 2/18 - 2/19 (sign-ups open 2/11)  DR week of 2/23 (sign-ups open 2/16) –Don’t forget to sign up to peer-review another project  Grading rubric on the website  Description on the website  Look at design reviews from past projects