1. Blog Post Grading

2. GENERAL OVERVIEW Do the posts capture the progress and development of your project?

3. GENERAL OVERVIEW Are the posts part of a cohesive project rather than just thrown together to have something posted?

4. GENERAL OVERVIEW Is the work original to your project? Is the work too dependent upon the work of others? Are the photos / drawings / calculations / collected data yours?

5. GENERAL OVERVIEW Your Critical Design Review (CDR) contains the following: System designs Block diagrams Experiments Trade-off studies, simulations Project status Resource reports (mass), costs, project status

6. GENERAL OVERVIEW All posts should feature some technical aspect of your project. Non technical posts (For example, “Hey, the parts came in today!”) will be deleted.

7. EXAMPLES From Tesla Blog Post: “DC Power Supply,” Dec. 12, 2014 Post describes Power needs Steps on how the need is determined Actual calculation Simulated in Multisim

8. EXAMPLES “Pathfinder Final Software Implementation,” Dec. 11, 2014 FSM demonstrates the system in an easy to understand visual that will also act as a guide in the implementation.

9. PDR / CDR will need to be uploaded as a PDF Deadline for all blog posts and video TBD. Points will be deducted for missing the deadline. Extra Credit for promotional video Non-copyrighted music Maximum length of approximately two minutes Acknowledge CSULB/ EE Dept / COE in the video OTHER CONSIDERATIONS

10. Your final post is the project documentation, which includes a summary and links to previous posts on the individual subject. The CDR outline can be used as a template for the final post Title Page/Executive Summary Project Work Breakdown Structure (Who is doing what?) Project Objectives Preferred Design with Illustrations Alternative Designs System Design System Block Diagram(s), with Summary of Major Project Features (Specifications) Design Solutions FINAL POST

11. Experiments Trade-off Studies, Models, and Rapid Prototyping Design Solutions for System, Subsystem, and Components Computer Simulations including Solidworks, Simulink, Multisim, Matlab, LabVEIW, LTspice, etc Experimental results and observations Systems/Subsystem Design Electronics Interface Definations Breadboard(s), Fritzing, Schematics, PCB Layout Software – Specifications, Psedo-code, or flowchart, C++ Hardware – 3D Models and prototype prints Resource Reports (Project Models and Prototype Prints) FINAL POST (CONT.)

12. Verification Test Plans System and Subsystem, Hardware and Software Project Status Resource Reports (Mass, Power) Updated Cost Schedule Status – Fabrication Project Percent completion and/or Burn Down Diagram FINAL POST (CONT.)