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 [2017/04/25 18:32] tfagaran [196/296 Students] |
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 48: | Line 48: | ||
| ===== 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. | 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. | ||
| Line 90: | Line 90: | ||
| 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 | ||
| Line 145: | Line 147: | ||
| ==== 196/296 Students ==== | ==== 196/296 Students ==== | ||
| Team presentations should include the following: | Team presentations should include the following: | ||
| + | * Project background and motivation | ||
| + | * Goal for your project | ||
| * Overall block diagram of your system | * Overall block diagram of your system | ||
| * Include more detailed block diagrams of the different parts of your system | * Include more detailed block diagrams of the different parts of your system | ||
| * Include your pseudocode/algorithm for your code | * Include your pseudocode/algorithm for your code | ||
| - | * Your team’s progress since the PDR | + | * Final status of your project |
| - | * What you have yet to finish | + | * Any remaining problems |
| + | * Future improvements | ||
| * 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 **4-6 minutes** to present with a couple minutes afterwards for questions. | Teams will have **4-6 minutes** to present with a couple minutes afterwards for questions. | ||