====== Presentation Guidelines ====== ===== General Guidelines ===== ==== Date and Time ==== Please refer to the date on the [[x96 syllabus:start#Meetings|x96 Syllabus]] for the presentation dates. Please respond to the google calendar invite that was sent out, and if you cannot make it, please also email the project manager. ==== Criteria ==== When presenting, please keep the criteria from the following rubric in mind: {{:x96_syllabus:presentationrubric.pdf|}}. We will give teams feedback based off of this criteria. ==== Submission Requirements ==== * Presentations should be saved or shared to the Google Drive (SCEL > Spring 2018 > General Documents > Presentations & Papers > x96 > Presentations) **at least 30 minutes before the meeting starts** * Files should be saved as < Your team name >_< Name of presentation >.pptx. For example, the Dragonfruit design team will name their proposal presentation as “Dragonfruit_Proposal_Presenation.pptx”. ---- ===== Proposal Presentation ===== Attire: [[.:attire#casual|Casual]] ==== 396/496 Students ==== Team presentations should include the following: * Introduction of the team, including roles of each member * Overview of the project and your goals for this semester * Your approach to completing these goals * Potential problems you foresee for the semester * Learning expectations for this semester * Your team’s progress so far Teams will have **8 minutes** to present with a couple minutes afterwards for questions. ==== 499 Students ==== Team presentation should include the following: * Quick introduction of the team * Goals for this semester * Schedule for this semester * Updates on your progress Teams will have **4 minutes** to present with a couple minutes afterwards for questions. ==== 196/296 Students ==== Team presentations should include the following: * Introduction of the team * Motivation * Overview of the project * Goals for this semester * Timeline/schedule for the semester Teams will have **4-8 minutes** to present with a couple minutes afterwards for questions. ---- ===== Preliminary Design Review (PDR) ===== Attire: [[.:attire#casual|Casual]] The PDR demonstrates that the preliminary design meets all system requirements with acceptable risk and within the cost and schedule constraints. It also establishes the basis for proceeding with a more detailed design. It will show that the correct design options have been selected and interfaces have been identified. For all x96 students engaged on a full design project, the PDR will be a review of the planned design for the semester. ==== 396/496 Students ==== Team presentations should include the following: * Overall block diagram of your system * Problems or issues you have experienced * Your team’s progress since the Proposal Presentation * What you have yet to finish Teams will have **4-8 minutes** to present with a couple minutes afterwards for questions. ---- ==== 499 Students ==== Team presentation should include the following: * Update on schedule * Please include a revised schedule if you have made changes. * Updates on your progress * Issues encountered Teams will have **4 minutes** to present with a couple minutes afterwards for questions. ==== 196/296 Students ==== Team presentations should include the following: * Overall block diagram of your system * How your teams have been splitting up the project * Problems or issues you have experienced * Your team’s progress since the Proposal Presentation * What you have yet to finish * Timeline/schedule for the semester Teams will have **4-8 minutes** to present with a couple minutes afterwards for questions. ---- ===== Critical Design Review (CDR) ===== Attire: [[.:attire#casual|Business Casual]] ==== 396/496 Students ==== Team presentations should include the following: * Overall block diagram of your system * Hardware teams: * Include more detailed block diagrams of the different parts of your system * Completed testing box in the lab and show full Power Budget * Software teams: include your pseudocode/algorithm for your code * Your team’s progress since the PDR * What you have yet to finish * Any questions or problems you would like answered or feedback on Teams will have **6-8 minutes** to present with a few minutes afterwards for questions. ==== 499 Students ==== Team presentation should include the following: * Update on schedule * Please include a revised schedule if you have made changes. * Updates on your progress * Issues encountered Teams will have **4 minutes** to present with a couple minutes afterwards for questions. ==== 196/296 Students ==== Team presentations should include the following: * Overall block diagram of your system * Include more detailed block diagrams of the different parts of your system * Include your pseudocode/algorithm for your code * Your team’s progress since the PDR * What you have yet to finish * Any questions or problems you would like answered or feedback on Teams will have **4-6 minutes** to present with a couple minutes afterwards for questions. ---- ===== Final Presentation ===== Attire: [[.:attire#businesscasual|Business Casual]] ==== 396/496 Students ==== Team presentations should include the following: * Project background and motivation * Goal for your project * Block diagram * How you accomplished your goal * Description of your overall design * Methods/Procedure * Major problems you ran into and how you solved them * Power Budget and BOM * Final status of your project * Any remaining problems * Future improvements Teams will have **6-10 minutes** to present with **5 minutes** afterwards for questions. //Please keep in mind that this presentation should summarize all the work you have completed this semester and will serve as a resource to students continuing the projects in the future.// ==== 499 Students ==== Team presentations should include the following: * Updates on your progress and any issues encountered * Final status of your project * Any remaining problems * Future improvements Teams will have **4 minutes** to present with a couple minutes afterwards for questions. ==== 196/296 Students ==== Team presentations should include the following: * Project background and motivation * Goal for your project * Overall block diagram of your system * Include more detailed block diagrams of the different parts of your system * Include your pseudocode/algorithm for your code * Final status of your project * Any remaining problems * Future improvements * Any questions or problems you would like answered or feedback on Teams will have **4-6 minutes** to present with a couple minutes afterwards for questions.