Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
x96_syllabus:presentation_guidelines [2016/09/10 02:43] tfagaran [Submission Requirements] |
x96_syllabus:presentation_guidelines [2021/09/19 21:59] (current) |
||
---|---|---|---|
Line 9: | Line 9: | ||
==== Submission Requirements ==== | ==== Submission Requirements ==== | ||
- | * Presentations should be saved or shared to the Google Drive (SCEL > FALL 2016 > General Documents > Presentations & Papers > x96 > <Name of presentation> Presentations) **at least 30 minutes before the meeting starts** | + | * Presentations should be saved or shared to the Google Drive (SCEL > Spring 2018 > General Documents > Presentations & Papers > x96 > <Name of presentation> 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”. | * 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”. | ||
Line 43: | Line 43: | ||
* Goals for this semester | * Goals for this semester | ||
* Timeline/schedule for the semester | * Timeline/schedule for the semester | ||
- | Teams will have **6 minutes** to present with a couple minutes afterwards for questions. | + | Teams will have **4-8 minutes** to present with a couple minutes afterwards for questions. |
---- | ---- | ||
===== Preliminary Design Review (PDR) ===== | ===== Preliminary Design Review (PDR) ===== | ||
- | Attire: [[.:attire#businesscasual|Business Casual]] | + | 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 ==== | ==== 396/496 Students ==== | ||
Line 56: | Line 60: | ||
* Your team’s progress since the Proposal Presentation | * Your team’s progress since the Proposal Presentation | ||
* What you have yet to finish | * What you have yet to finish | ||
- | Teams will have **8 minutes** to present with a couple minutes afterwards for questions. | + | Teams will have **4-8 minutes** to present with a couple minutes afterwards for questions. |
+ | |||
+ | ---- | ||
==== 499 Students ==== | ==== 499 Students ==== | ||
Line 73: | Line 79: | ||
* Your team’s progress since the Proposal Presentation | * Your team’s progress since the Proposal Presentation | ||
* What you have yet to finish | * What you have yet to finish | ||
- | Teams will have **6 minutes** to present with a couple minutes afterwards for questions. | + | * Timeline/schedule for the semester |
+ | Teams will have **4-8 minutes** to present with a couple minutes afterwards for questions. | ||
---- | ---- | ||
===== Critical Design Review (CDR) ===== | ===== Critical Design Review (CDR) ===== | ||
- | Attire: [[.:attire#casual|Casual]] | + | Attire: [[.:attire#casual|Business Casual]] |
==== 396/496 Students ==== | ==== 396/496 Students ==== | ||
Team presentations should include the following: | Team presentations should include the following: | ||
* Overall block diagram of your system | * Overall block diagram of your system | ||
- | * Hardware teams: include more detailed block diagrams of the different parts 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 | * Software teams: include your pseudocode/algorithm for your code | ||
* Your team’s progress since the PDR | * Your team’s progress since the PDR | ||
* What you have yet to finish | * What you have yet to finish | ||
* Any questions or problems you would like answered or feedback on | * Any questions or problems you would like answered or feedback on | ||
- | Teams will have **8 minutes** to present with **7 minutes** afterwards for questions. | + | Teams will have **6-8 minutes** to present with a few minutes afterwards for questions. |
==== 499 Students ==== | ==== 499 Students ==== | ||
Line 106: | Line 115: | ||
* What you have yet to finish | * What you have yet to finish | ||
* Any questions or problems you would like answered or feedback on | * Any questions or problems you would like answered or feedback on | ||
- | Teams will have **6 minutes** to present with a **5 minutes** afterwards for questions. | + | Teams will have **4-6 minutes** to present with a couple minutes afterwards for questions. |
---- | ---- | ||
Line 126: | Line 135: | ||
* Any remaining problems | * Any remaining problems | ||
* Future improvements | * Future improvements | ||
- | Teams will have **12 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.// | + | 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 ==== | ==== 499 Students ==== | ||
Line 137: | Line 146: | ||
==== 196/296 Students ==== | ==== 196/296 Students ==== | ||
- | Teams will demonstrate their final product. Teams should bring their final product. | + | Team presentations should include the following: |
- | In the demonstration, teams should have a few slides that include the following: | + | * Project background and motivation |
- | * An explanation of how it works | + | * Goal for your project |
- | * Insight into your design choices | + | * Overall block diagram of your system |
- | * Any special features of your product | + | * Include more detailed block diagrams of the different parts of your system |
- | Teams will have **6 minutes** to present with a couple minutes afterwards for questions. | + | * 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. | ||