1. ECE 3331 Project Lab I Lab Projects and Presentations 1

2. Overview Budget Gantt Chart Documentation Presentations Written Reports Lab Notebook 2

3. What is the question most frequently asked of engineers? How much does it cost? –To build –To buy –To design 3

4. Budget Fee for the entire project. Weekly accumulated expenditure. Manufacturing cost for the system in quantity. 4

5. Fee for the Entire Project 5 Labor Cost: Direct Labor: Manhours x Hourly Rate ($20.00/Hr) Indirect Labor: (Overhead Cost = 1.5 x Direct Labor Cost) Materials Cost: Catalog Price for all materials used in the Prototype Equipment Cost: Cost of renting all test equipment used in constructing and testing the prototype. (1% of the replacement cost of the equipment per week)

6. Weekly Accumulated Expenditure 6 1 st Week: Direct Labor for 1 st Week Indirect Labor for 1 st Week Total Materials Anticipated for the Prototype Total Equipment Anticipated for the Prototype Each Successive Week: Accumulated Direct and Indirect Labor Additional Materials Additional Equipment

7. Manufacturing Cost 7 Estimate the Manufacturing Cost for 1000 Units Labor Cost: Direct Labor: Manhours x Hourly Rate ($15.00/Hr) Indirect Labor: (Overhead Cost = 1.5 x Direct Labor Cost) Materials Cost: Catalog Price for all materials in quantities for 1000

8. 8

9. Gantt Chart Plan all of the activities through the entire project. There are no group tasks! A task for every person, a person for every task. The third time is the charm! The last month should be programming. There is no group programming. Watching someone else code is not a proper task. 9

10. What do engineers produce? Engineers produce documents !!! –Design documents –Contract documents –Test documents –Operation Manuals 10

11. Project Flowchart 11 Design Construction Testing Demonstration Document the entire Project !!!

12. Design 12 System Requirements Design Documents Design Analysis Performance Criteria Specifications Block Diagrams Schematics Datasheets Calculations Predicted Performance Flowcharts Code

13. Construction 13 Design Documents Construction of Prototype Plans Drawings Photographs The success (or failure) of a project is often a matter of construction techniques! Document all changes!

14. Construction Techniques Breadboard Solder-able Breadboard Proper Connectors 14

15. 15 Perfect the circuit here Make a permanent copy here

16. 16 Use proper connectors

17. Testing 17 Performance Criteria Measurements Evaluation Expected Performance Experiment Design Instrumentation Diagram Recorded Data Tables Charts Graphs Oscilloscopes Traces Comparison with Expected Performance Statistical Analysis Back to Design

18. Demonstration 18 System Requirements Demonstration Evaluation Experiment Design Instrumentation Diagram Recorded Data Tables Charts Graphs Video Comparison with System Requirements Operational Instructions

19. Documentation The weekly presentations are to be design reviews. The status and progress of the project are to be demonstrated in the project documents. The project documents are to be updated as the project progresses. All of the technical information generated in the design, construction and testing of the system go into the project notebook. 19

20. PowerPoint Presentations No Backgrounds No Animations No Embedded Videos –Upload Videos as separate files Black on white Names on slides 20

21. Weekly Presentations Show the design documents every week –Block Diagrams –All Schematic Diagrams of what is being built –Flow Charts (State Diagrams) Discuss improvements in the plan Show measurements and videos Only present interesting snippets of code. 21

22. Weekly Presentations Have something to say! –It is easy to present when your laboratory work is producing results Do not look at the screen. Look at the audience. Do not simply read from the slide. Hands at your sides, not in your pockets. 22

23. Weekly Presentations Good posture, head up, shoulders back. Do not stand in front of the screen. 23

24. Weekly Deliverables From Wikipedia, the free encyclopedia Deliverable is a term used in project management to describe a tangible or intangible object produced as a result of the project that is intended to be delivered to a customer (either internal or external). A deliverable could be a report, a document, a work package, a server upgrade or any other building block of an overall project. 24

25. Weekly Deliverables Each week, include the Deliverable that will be presented next week. Be flexible. Often circumstances demand that anticipated Deliverables be abandoned in favor new priorities. Research is never a Deliverable! The plan, diagram or algorithm that comes from the research is a Deliverable. 25

26. Written Reports Each person shall write an individual report. Each report shall describe the entire system. The report shall be a technical description of the system. The project documents are the substance of the written report. Write a narrative that connects the elements of the system. 26

27. Lab Notebook All materials used and generated in the course of the project are to be recorded digitally. All the material is to be zipped into one folder and uploaded at the end of the semester. 27