- Project name
- Your name, advisor, program
- One simple image (e.g., system diagram/photo)
Keep it clean—this acts as your “start” since you cannot use an outline slide.
Slides: 1
- Clear statement of the final goal
- What the system must achieve (success criteria)
- One diagram showing input → system → output
Advisor said start with COMPLETE GOAL.
Slides: 2–3
- What domain your project lies in
- Why the domain matters
- What users need / real-world challenges
- Visual-heavy: photos, diagrams, scenarios
Advisor said “can go OVERBOARD” on domain.
Slides: 2
- Existing approaches (industry + academia)
- What they can do
- What they cannot do (your gap)
- Bullet-point comparison chart
Keep it honest: “DONT MAKE STUFF UP.”
Slides: 2
-
Requirements (functional + non-functional)
-
Methodology:
- iteration cycles
- experiments
- failures + how you fixed them
-
A timeline / flowchart showing how the project evolved
Advisor wants PROCESS + methodology emphasized.
Slides: 2
- Main diagram of the entire pipeline
- Data flow from microphone/camera → models → planner → robot
- Subsystem responsibilities
Make sure structure matches your final report.
Slides: 1–2
- Model choice, dataset
- Benchmark accuracy/WER
- Limitations
- Spectrogram or model diagram
Slides: 1–2
- What detections you perform
- Metrics/benchmark
- Pipeline diagram
Slides: 1–2
- How planning works in your system
- Performance, constraints
- Latency, success rate
Keep each subsystem visually intuitive.
Slides: 1–2
- Simulation environment
- Real hardware configuration
- Images, connection diagrams
- Key constraints you solved (latency, safety, coordinate transform issues)
Slides: 1
- End-to-end performance
- Success rates, timings
- Before/after improvements
This section shows that the whole system works, not just parts.
Slides: 1
- A video or image sequence
- System performing the final task
Short & focused.
Slides: 1
- Clear next steps (realistic)
- No speculation
Advisor said “don’t make stuff up.”
Your appendix should contain:
- Model architectures
- Hyperparameters
- Data preprocessing
- Training curves
- Hardware communication details
- ROS2 action flow diagrams
- What failed in ASR, vision, planning
- How you debugged it
- Ablation studies
- Different architectures tested
- Logs
- Testing methodology
- Edge cases
- Validation steps
- Definitions
- Additional diagrams
- System block comparisons
TOTAL APPENDIX: ~20 slides
These exist ONLY to answer questions.
| Current Structure | Improved Structure Based on Feedback |
|---|---|
| Introduction/background | → Goal + domain + problem → strong contextual start |
| Architecture overview | ✔ Still included, but expanded and placed AFTER motivation & related work |
| ASR, Vision, Planning results | ✔ Still included but reorganized under “Subsystem results” |
| Simulation + hardware | ✔ Still included |
| Demo | ✔ Still included |
| ❌ No related work | ✔ Added related work + gap analysis |
| ❌ No process methodology | ✔ Added engineering process section |
| ❌ No application domain emphasis | ✔ Added domain section with extra depth |
| ❌ No future plans | ✔ Added a realistic “Future work” slide |
| ❌ No appendix | ✔ Added 20-slide appendix for Q&A |
Just tell me!