Blog Post Grading

GENERAL OVERVIEW

Do the posts capture the progress and development of your project?

GENERAL OVERVIEW

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

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?

GENERAL OVERVIEWYour Critical Design Review (CDR) contains the following:• System designs Block

diagrams• Experiments Trade-off studies,

simulations• Project status Resource

reports (mass), costs, project status

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.

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

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.

• 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 videoNon-copyrighted musicMaximum length of approximately two

minutesAcknowledge CSULB/ EE Dept / COE in the video

OTHER CONSIDERATIONS

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 postTitle Page/Executive Summary

• Project Work Breakdown Structure (Who is doing what?) • Project Objectives• Preferred Design with Illustrations

• Alternative DesignsSystem Design

• System Block Diagram(s), with Summary of Major Project Features (Specifications)

• Design Solutions

FINAL POST

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.)

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.)