This week represents the culmination of your learning journey in AI Applications in Engineering. You will present and demonstrate your group's final project, showcasing practical AI implementations on the NVIDIA Jetson Orin Nano platform. This is your opportunity to demonstrate technical mastery, creative problem-solving, and effective communication of complex AI concepts to both technical and non-technical audiences.
What You'll Demonstrate
- Technical Implementation: Working AI application deployed on Jetson Orin Nano
- Presentation Skills: Clear, organized communication of technical concepts
- Problem-Solving: Design decisions, challenges faced, and solutions implemented
- Innovation: Creative application of course concepts to real-world problems
- Teamwork: Effective collaboration and division of responsibilities
- Documentation: Comprehensive project report with code, results, and analysis
💡 Why This Matters
The ability to design, implement, and effectively communicate AI solutions is crucial in today's technology-driven world. Project presentations develop essential professional skills including technical communication, demonstration techniques, and the ability to explain complex concepts clearly. These skills are highly valued in industry, research, and academia, preparing you for careers where you'll need to present technical work to diverse audiences including managers, clients, and stakeholders.
Assessment Weight
This project presentation and demonstration is worth 25% of your final course grade, making it one of the most significant assessments in the course. The evaluation encompasses your technical implementation, presentation quality, demonstration effectiveness, documentation completeness, and your ability to respond to questions about your work.
⚠️ Group Collaboration:
This is a group project with 2-3 students per group. All group members must participate equally in the presentation and be prepared to answer questions about any aspect of the project. Individual contribution and understanding will be assessed during the Q&A session.
By the end of this presentation session, you will be able to:
-
Present technical AI projects professionally with clear organization, appropriate technical depth, and effective visual aids that communicate complex concepts to diverse audiences.
-
Demonstrate working AI implementations on the Jetson Orin Nano platform, showcasing real-time functionality and practical applications of course concepts.
-
Explain design decisions and architectural choices including model selection, hardware utilization, optimization strategies, and trade-offs considered during development.
-
Analyze and present experimental results with appropriate metrics, visualizations, and quantitative evaluation of your AI system's performance.
-
Discuss challenges encountered and solutions implemented demonstrating problem-solving skills, debugging techniques, and adaptive learning throughout the project.
-
Respond to technical questions confidently showing deep understanding of your project's implementation, underlying AI concepts, and potential improvements or extensions.
-
Collaborate effectively in technical teams by dividing responsibilities appropriately, integrating individual contributions, and presenting cohesively as a group.
Effective Technical Presentations
Technical presentations require a unique blend of clarity, accuracy, and engagement. Unlike general presentations, technical talks must balance detailed technical content with accessibility for audiences with varying levels of expertise. Effective technical presenters organize their content logically, starting with motivation and context before diving into implementation details. They use visual aids strategically—diagrams for architectures, graphs for performance metrics, and live demonstrations to showcase functionality. The goal is not just to inform but to make complex technical concepts understandable and compelling.
Key elements of successful technical presentations include: clear problem definition and motivation, systematic explanation of your approach, honest discussion of limitations and challenges, quantitative results with appropriate visualizations, and thoughtful conclusions about lessons learned and future directions. Remember that your audience wants to understand not just what you built, but why you made specific design choices and what you learned in the process.
Project Documentation Best Practices
Comprehensive project documentation is essential for reproducibility, knowledge transfer, and professional practice. Good documentation includes multiple components: a clear README explaining project purpose and setup instructions, well-commented code that explains complex logic and design decisions, a technical report detailing methodology and results, and visual documentation through diagrams and screenshots. Documentation should be written with future users in mind—someone should be able to understand and build upon your work without direct communication with you.
For AI projects specifically, documentation should cover the problem being solved, dataset characteristics and preprocessing steps, model architecture and rationale, training process and hyperparameters, evaluation metrics and results, deployment considerations on edge hardware, known limitations, and potential improvements. Version control through Git and clear file organization are also crucial aspects of professional project documentation.
Demonstration Techniques for AI Systems
Demonstrating AI systems effectively requires careful planning and backup strategies. Live demonstrations are powerful but risky—they show real functionality but can fail due to technical issues. Best practices include thorough testing beforehand, having backup recorded videos, preparing interesting test cases that showcase capabilities, and having contingency plans for common failure modes. When demonstrating, narrate what you're doing and why, highlight interesting behaviors or edge cases, and be honest about limitations rather than trying to hide them.
For edge AI demonstrations on Jetson Orin Nano, consider factors like lighting conditions for computer vision tasks, physical setup and positioning of cameras or robots, performance metrics displayed in real-time, and comparison with baseline approaches when relevant. Interactive demonstrations where audience members can provide input or test cases are particularly engaging. Always time your demonstrations during practice to ensure they fit within allocated time.
Group Collaboration in Technical Projects
Successful technical teamwork requires clear communication, well-defined roles, and mutual accountability. Effective teams establish regular meeting schedules, use collaborative tools for code sharing and documentation, divide work based on individual strengths while ensuring everyone understands all components, and integrate individual contributions through code reviews and testing. When presenting as a group, coordination is crucial—transitions between speakers should be smooth, content should not overlap unnecessarily, and all members should be prepared to answer questions about any aspect of the project.
Common pitfalls in group projects include unequal distribution of work, poor integration of individual components, lack of communication leading to duplicated effort or incompatible code, and inadequate preparation for the presentation. Avoid these by establishing clear expectations early, maintaining regular communication, conducting integration testing throughout development rather than at the end, and practicing the presentation multiple times as a group with feedback from each other.
💡 Tips for Successful Presentations
- Practice extensively - Rehearse your presentation multiple times, timing yourself and refining content
- Know your audience - Balance technical depth with clarity for peers and instructors
- Tell a story - Structure your presentation as a narrative with clear motivation, approach, and conclusions
- Use visuals effectively - Avoid text-heavy slides; use diagrams, charts, and demonstrations
- Anticipate questions - Think about what might be asked and prepare thoughtful responses
- Test everything - Verify your demonstration works with the actual presentation setup
- Have backups - Prepare video recordings in case live demos fail
- Be honest about limitations - Acknowledge what didn't work and explain why
Presentation Requirements
- Duration: 10 minutes presentation + 5 minutes Q&A per group
- Format: PowerPoint, Google Slides, or similar presentation software
- Required Slides:
- Title slide with project name, group members, date
- Problem statement and motivation (why this project matters)
- Approach and methodology (what you did and how)
- System architecture and implementation details
- Results and evaluation with metrics/visualizations
- Challenges and solutions
- Demonstration (live or video)
- Conclusions and future work
- References (if applicable)
- All group members must participate in the presentation
- Visual aids: Use diagrams, charts, and images (avoid text-heavy slides)
Demonstration Requirements
- Live demonstration: Preferred, showing real-time functionality
- Backup video: Required in case of technical difficulties (1-2 minutes max)
- Test cases: Prepare multiple examples showcasing different capabilities
- Narration: Explain what's happening during the demonstration
- Setup check: Arrive 15 minutes early to test equipment and connectivity
Documentation Requirements
- Project Report: 5-8 pages comprehensive written documentation
- Source Code: Complete, commented code in organized repository
- Demo Video: 1-2 minute video showing project functionality
- README: Setup instructions, dependencies, and usage guide
- Due Date: All materials due on presentation day before your scheduled time
⚠️ Group Coordination:
Schedule multiple practice sessions with your group before presentation day. Ensure smooth transitions between speakers, consistent terminology, and that all members can answer questions about any aspect of the project. Test your demonstration equipment in the actual presentation environment if possible.
📝 Pre-lab Quiz
Instructions: Complete this quiz to assess your readiness for the presentation. These questions test your understanding of effective technical communication, project documentation, and demonstration best practices.
Question 1: What is the primary goal of a technical presentation?
- A) To impress the audience with complex terminology
- B) To clearly communicate technical concepts and results to the intended audience
- C) To show every line of code written for the project
- D) To avoid discussing any challenges or limitations
Question 2: What is the ideal structure for a technical presentation?
- A) Start with technical details, then explain the problem
- B) Start with motivation/problem, then approach, results, and conclusions
- C) Present all code first, then explain what it does
- D) Focus only on successful results without discussing methodology
Question 3: Why is a backup video demonstration important?
- A) To avoid doing a live demonstration entirely
- B) To ensure you can still show functionality if technical issues occur during live demo
- C) To make the presentation longer
- D) Because live demonstrations are not professional
Question 4: What should good project documentation include?
- A) Only the final working code without any comments
- B) Just a list of what works, without explaining how
- C) Clear explanation of problem, methodology, code with comments, results, and setup instructions
- D) Only screenshots without any written explanation
Question 5: How should you handle questions you don't know the answer to during Q&A?
- A) Make up an answer to appear knowledgeable
- B) Ignore the question and move on quickly
- C) Honestly acknowledge you don't know, and offer to investigate and follow up
- D) Blame other team members for not knowing
Question 6: What is the recommended approach for slides in technical presentations?
- A) Use as much text as possible on each slide
- B) Use visuals like diagrams and charts with minimal text
- C) Include complete paragraphs that you read verbatim
- D) Use complex animations and transitions for every element
Question 7: What is the purpose of discussing challenges and limitations in your presentation?
- A) It makes your project look weak and unprofessional
- B) It shows honest self-reflection, problem-solving skills, and learning process
- C) It's unnecessary if the project works
- D) It's only mentioned to fill time in the presentation
Question 8: How should team members coordinate in a group presentation?
- A) One person presents everything while others stand silently
- B) Each person only knows their own section and can't answer questions about others' work
- C) All members participate, with smooth transitions and collective understanding of the entire project
- D) Divide presentation randomly without practice
Question 9: What metrics should be included when presenting AI project results?
- A) Only subjective opinions about how well it works
- B) Quantitative metrics (accuracy, speed, etc.) with visualizations and comparisons
- C) Metrics are not necessary for demonstrations
- D) Only the best results, hiding any failures
Question 10: What should you do if your live demonstration fails during the presentation?
- A) Panic and apologize repeatedly while trying to fix it on the spot
- B) Calmly switch to your backup video while briefly explaining what went wrong
- C) Skip the demonstration entirely and move to conclusions
- D) Blame the equipment or setup and get defensive
Note: Review your answers with your group members and ensure everyone understands these presentation best practices before your scheduled presentation time.
This section outlines the procedures and schedule for presentation day. Each group will have 15 minutes total: 10 minutes for presentation and demonstration, followed by 5 minutes for questions and answers. Presentations will be evaluated by the instructor and potentially by peers using standardized rubrics.
⚠️ Arrival and Setup:
1. Arrive 15 minutes early to set up and test your equipment and connectivity.
2. Submit all documentation (report, code, video) before your presentation begins.
3. Test your demonstration with the actual presentation setup and projector.
4. Load your presentation and backup video on the presentation computer.
Phase 1: Equipment Setup and Testing (15 minutes before)
Before your scheduled presentation time, verify that all technical components are working correctly. This includes connecting your Jetson Orin Nano (if demonstrating live), testing video playback, verifying presentation slides display correctly, and ensuring any additional equipment (cameras, sensors, displays) is functional. This preparation time is crucial for smooth presentation delivery.
Setup Checklist:
- Connect Jetson Orin Nano to power and display/projector
- Test network connectivity if required for your project
- Verify presentation slides load correctly
- Test backup demo video playback
- Position camera/sensors optimally for demonstration
- Run a quick test of your AI application to ensure it's functioning
- Confirm all group members' equipment works (clickers, notes, etc.)
Phase 2: Formal Presentation (10 minutes)
Deliver your prepared presentation covering all required components: problem motivation, approach and methodology, system architecture, implementation details, results and evaluation, and conclusions. All group members should participate in presenting, with smooth transitions between speakers. Maintain professional demeanor, speak clearly and confidently, make eye contact with the audience, and use your visual aids effectively. Time management is crucial—practice beforehand to ensure you fit within 10 minutes.
Presentation Components:
- Introduction (1 min): Problem statement, motivation, and project objectives
- Methodology (2 min): Approach, algorithms, and system design
- Implementation (2 min): Architecture, key technologies, and development process
- Demonstration (3 min): Live demo or video showing functionality
- Results & Discussion (1.5 min): Performance metrics, evaluation, and analysis
- Conclusion (0.5 min): Summary, challenges, lessons learned, future work
Phase 3: Live Demonstration (Integrated in Presentation)
The demonstration is the most critical part of your presentation—it proves your project works and showcases your technical achievement. Present your demonstration during the appropriate section of your presentation. Narrate what you're doing and explain the AI processes happening in real-time. Show multiple test cases that highlight different capabilities or interesting edge cases. If the live demonstration encounters issues, smoothly transition to your backup video without excessive apology or panic.
Demonstration Best Practices:
- Prepare diverse test cases that showcase different features
- Explain what the AI system is doing at each step
- Highlight interesting behaviors or challenging scenarios
- Show performance metrics or confidence scores if applicable
- Have your backup video ready to play if technical issues occur
- Be honest about limitations and failure cases
Phase 4: Questions and Answers (5 minutes)
After your presentation, the instructor and potentially other students will ask questions about your project. All group members should be prepared to answer questions about any aspect of the work—technical implementation, design decisions, challenges faced, or potential improvements. Listen carefully to questions, take a moment to think before responding, and provide thoughtful, complete answers. If you don't know an answer, it's better to admit it honestly and offer to follow up later than to guess or provide incorrect information.
Q&A Guidelines:
- Listen to the complete question before responding
- Repeat or rephrase the question if needed for clarity
- Provide concise but complete answers
- Any group member can answer, but all should be prepared
- Be honest if you don't know something
- Relate answers back to your project specifics
- Thank questioners for their interest
💡 Time Management Tips
- Practice with a timer - Rehearse multiple times to nail the 10-minute target
- Designate a timekeeper - One team member should monitor time during presentation
- Have shortened versions ready - Know what to cut if running over time
- Don't rush the demo - It's the most important part; allocate sufficient time
- Leave buffer time - Aim for 9-9.5 minutes to avoid going over
Presentation Schedule
Groups will present in alphabetical order by group name. Each group has a strict 15-minute window. If your presentation exceeds 10 minutes, the instructor may stop you to ensure time for Q&A and to stay on schedule.
Arriving late to your scheduled time slot will result in reduced time or potential rescheduling penalties.
Below are suggested project ideas organized by difficulty level. These are meant to inspire your group—feel free to propose your own original ideas that demonstrate AI applications on the Jetson Orin Nano. All projects should involve AI/ML components and practical implementations on the Jetson platform.
🟢 Beginner Level Projects
These projects build directly on course labs with moderate extensions:
- Custom Image Classifier: Train classifier for specific UAE context (e.g., local vehicles, traditional objects, desert wildlife)
- Real-time Object Counter: Count specific objects in video stream with visual display and statistics
- Gesture Recognition System: Recognize hand gestures for controlling applications or simple commands
- Face Mask Detector: Detect whether people are wearing masks using computer vision
- Plant Disease Detector: Identify diseases in plant leaves from camera images for agricultural applications
- Sign Language Translator: Recognize basic sign language gestures and convert to text
- Smart Attendance System: Face recognition-based attendance tracking with database
🟡 Intermediate Level Projects
These projects require integration of multiple concepts and more complex implementation:
- Multi-Object Tracking System: Track multiple objects across video frames with unique IDs and trajectories
- Smart Parking Detector: Detect available parking spots using overhead camera with occupancy statistics
- Activity Recognition: Classify human activities (walking, running, sitting, etc.) from video stream
- Traffic Flow Analyzer: Count and classify vehicles, measure speed, analyze traffic patterns
- Quality Control Inspector: Detect defects or anomalies in manufactured products using vision
- Emotion Recognition: Detect facial expressions and classify emotions in real-time
- Document Scanner & OCR: Capture, correct perspective, and extract text from document images
- Real-time Language Translator: Detect text in images and translate to another language
🔴 Advanced Level Projects
These projects demonstrate mastery and involve significant technical challenges:
- Autonomous Navigation System: Indoor/outdoor navigation with obstacle avoidance and path planning
- Pose Estimation Application: Track human body keypoints for fitness tracking or sports analysis
- Scene Understanding: Semantic segmentation with object detection for comprehensive scene analysis
- Multi-Camera Surveillance: Coordinate multiple cameras for tracking across different views
- Real-time Video Analytics: Combine detection, tracking, and behavior analysis for security applications
- 3D Object Detection: Depth estimation and 3D bounding boxes using stereo vision or depth sensors
- Model Optimization Study: Comparative analysis of different model architectures and optimization techniques for edge deployment
💡 Open-Ended / Student-Proposed Projects
Original ideas that demonstrate AI applications relevant to your interests:
- UAE-Specific Applications: Projects addressing local challenges or opportunities
- Healthcare AI: Medical image analysis, patient monitoring, or diagnostic assistance
- Environmental Monitoring: Wildlife tracking, pollution detection, or climate analysis
- Smart Agriculture: Crop monitoring, irrigation optimization, or pest detection
- Accessibility Tools: Assistive technologies for people with disabilities
- Educational Applications: Interactive learning tools or tutoring systems
- Arts & Creativity: AI-powered art generation, music creation, or style transfer
- Your Original Idea: Propose any project that demonstrates AI on Jetson Orin Nano (subject to instructor approval)
⚠️ Project Selection Guidelines:
• Projects must involve AI/ML components (not just traditional programming)
• Must run on Jetson Orin Nano (not just laptop/cloud)
• Should be demonstrable in 2-3 minutes
• Original ideas require instructor approval by Week 10
• Consider feasibility within available time and resources
Hardware & Software Requirements
- Platform: NVIDIA Jetson Orin Nano Developer Kit
- Camera: USB or CSI camera for vision projects (available in lab)
- Software: Python 3, PyTorch, OpenCV, TensorRT (pre-installed)
- Optional: Additional sensors (ultrasonic, IMU) available upon request
- Storage: Ensure sufficient SD card space for datasets and models
Presentation Materials
Templates and resources available for download:
- Presentation Template: PowerPoint template with recommended structure
- Project Report Template: Word/LaTeX template for final report
- Code Documentation Guide: Best practices for README and code comments
- Evaluation Rubric: Detailed grading criteria for self-assessment
Note: Templates will be shared via course LMS and email by Week 10.
Technical Presentation Guides
Project Documentation Resources
Jetson & AI Development Resources
Example AI Project Presentations
- Stanford CS231n Project Videos: Examples of excellent student project presentations
- MIT 6.S191 Final Projects: Deep learning project demonstrations and talks
- NVIDIA GTC Sessions: Professional AI project presentations and demos
Your final project is worth 25% of your course grade and will be evaluated based on multiple components including technical implementation, presentation quality, demonstration effectiveness, documentation completeness, and teamwork. This assessment measures both your technical skills and your ability to communicate complex concepts effectively.
⚠️ Submission Deadline:
All required materials (project report, source code, and demo video) must be submitted on presentation day before your scheduled presentation time. Late submissions will not be accepted and will result in zero credit for missing components.
Required Deliverables
Your project submission must include the following components:
1. Project Report (5-8 pages)
- Title page with project name, group members, date
- Abstract (150-200 words summarizing the project)
- Introduction and motivation
- Related work and background
- Methodology and approach
- System architecture and implementation details
- Experiments and results with visualizations
- Discussion of findings and limitations
- Conclusions and future work
- References (if applicable)
2. Source Code & Documentation
- Complete, well-organized source code
- Comprehensive code comments explaining logic
- README with setup instructions and dependencies
- Usage examples and command-line instructions
- Requirements.txt or environment.yml for dependencies
- Pre-trained model files (if size permits) or download instructions
3. Demonstration Video (1-2 minutes)
- Clear recording showing system functionality
- Multiple test cases demonstrating capabilities
- Narration or text explaining what's happening
- Visible performance metrics if applicable
- Professional quality (good lighting, steady camera, clear audio)
📋 Pre-Submission Checklist
Before submitting, verify you have completed:
- ✓ Project report is 5-8 pages, professionally formatted
- ✓ All code is well-commented and organized
- ✓ README includes complete setup instructions
- ✓ Demonstration video is 1-2 minutes, high quality
- ✓ All group members' names appear on all documents
- ✓ Code has been tested and runs without errors
- ✓ Presentation slides are finalized and practiced
- ✓ Backup video is ready in case live demo fails
- ✓ All required visualizations and results are included
- ✓ Files follow naming conventions specified below
📤 Submission Format
- Method: Upload to university LMS before presentation
- Project Report: PDF format only
- Filename:
Week13_Group[X]_ProjectReport.pdf
- Example:
Week13_Group3_ProjectReport.pdf
- Source Code: ZIP file containing all code and documentation
- Filename:
Week13_Group[X]_SourceCode.zip
- Include folder structure, README, and all necessary files
- Demo Video: MP4 or MOV format
- Filename:
Week13_Group[X]_Demo.mp4
- Maximum 100MB file size (compress if needed)
- Presentation Slides: PowerPoint or PDF
- Filename:
Week13_Group[X]_Presentation.pptx
Important Submission Notes:
- Total submission size should not exceed 200MB
- Ensure all files are virus-free and not corrupted
- Test that ZIP files extract correctly before submitting
- Keep backup copies of all submitted materials
📊 Evaluation Rubric (100 points = 25% of course grade)
| Component |
Points |
Evaluation Criteria |
| Presentation Quality |
20 |
Clear organization, effective communication, time management, visual aids |
| Technical Implementation |
30 |
Working system, code quality, proper AI integration, edge deployment |
| Innovation & Creativity |
15 |
Originality, problem-solving approach, technical challenges addressed |
| Documentation |
20 |
Complete report, code comments, README, setup instructions |
| Demonstration |
10 |
Working demo, clear narration, multiple test cases, professionalism |
| Q&A Performance |
5 |
Thoughtful answers, technical depth, all members participate |
| Total |
100 |
25% of Final Course Grade |
Detailed Grading Criteria:
Presentation Quality (20 points):
- Clear structure and logical flow (5 points)
- Effective visual aids and slides (5 points)
- Time management (within 10 minutes) (3 points)
- Speaking clarity and professionalism (4 points)
- Equal participation of all group members (3 points)
Technical Implementation (30 points):
- System functionality and correctness (10 points)
- Code quality, organization, and comments (8 points)
- Proper AI/ML integration and usage (7 points)
- Successful edge deployment on Jetson (5 points)
Innovation & Creativity (15 points):
- Originality and creativity of approach (5 points)
- Technical challenges addressed (5 points)
- Problem-solving and critical thinking (5 points)
Documentation (20 points):
- Project report completeness and quality (8 points)
- Code documentation and comments (5 points)
- README and setup instructions (4 points)
- Technical writing quality (3 points)
Demonstration (10 points):
- Live demo works correctly or quality backup video (5 points)
- Multiple test cases shown (2 points)
- Clear narration and explanation (2 points)
- Professional presentation (1 point)
Q&A Performance (5 points):
- Correct and complete answers (3 points)
- Technical depth demonstrated (2 points)
Penalty Conditions:
- Presentation exceeds 10 minutes: -5 points
- Missing documentation component: -10 points per missing item
- Code doesn't run or has major errors: Up to -15 points
- Unequal group participation evident: Individual grade adjustments
- Late submission of materials: Not accepted (0 points for missing items)
- Plagiarism or copied work: Zero credit and academic integrity violation
🎓 Individual vs. Group Assessment
While this is a group project, individual contributions are considered:
- Each member must present part of the presentation
- All members must be able to answer questions about any aspect
- Instructor may assign different grades to group members based on participation
- Peer evaluation may be used to assess individual contributions
- Unequal contribution will result in grade adjustments