moodle (Turn in slides)
May 5, 1:30–4:30 PM
On May 5, each person will give a final presentation and demo of their software development project.
Each presentation will be 15 minutes total, including approximately 5 minutes for demo and questions.
Your goal is to clearly explain what you built, how it works, how you used AI, and what you learned from the process.
Presentation Requirements
Your presentation should include the following sections.
1. Project Overview
Begin by explaining the purpose of your project.
Include:
- What your application does
- Who it is for
- What problem it solves
- The major features of the system
This should give the audience enough context to understand the rest of the presentation.
2. System Features
Explain the main working features of your application.
Focus on what is complete and functional.
You should discuss:
- The main user workflows
- The most important pages
- CRUD features
- Authentication or access control
- Any important business logic
Do not spend much time on features that are unfinished. If you reduced your original scope, explain what subset you completed and why.
3. Database Schema
Explain your database design.
Include:
- The main tables
- What each table stores
- How the tables relate to each other
- Why you designed the schema this way
You do not need to explain every column in detail, but you should show that your database design supports the application.
4. API and System Architecture
Briefly explain how your application is organized.
Include:
- React frontend
- Node.js / Express backend
- MariaDB database
- API routes
- Authentication method
- Deployment using PM2
- CI/CD testing and deployment setup
The goal is to show that you understand how the pieces of the system work together.
5. How You Used AI
Explain how AI was used during the project.
Be specific.
Discuss:
- How AI helped with design
- How AI helped with coding
- How AI helped with debugging
- How AI helped with testing or documentation
- How you guided the AI
- How you checked whether AI-generated code was correct
You should make clear that AI was a tool, but you were responsible for the design decisions, testing, integration, and final product.
6. Lessons Learned
Discuss what you learned from the project.
Include both technical and AI-related lessons.
You might discuss:
- What you learned about React
- What you learned about Node.js and Express
- What you learned about MariaDB
- What you learned about API design
- What you learned about authentication
- What you learned about CI/CD
- What you learned about using AI effectively
- What mistakes you made and how you fixed them
This is an important part of the presentation. Be honest and thoughtful.
7. Full System Demo
Your demo should show the working application.
You should demonstrate:
- The application running on your assigned port
- The main user workflow
- Creating, reading, updating, and deleting data where appropriate
- Any login or role-based behavior
- The most important business logic
- The polished parts of the UI
Practice your demo ahead of time. Make sure your application is running before your presentation begins.
Presentation Expectations
A strong presentation will:
- Stay within the time limit
- Clearly explain the purpose of the project
- Show a working system
- Demonstrate understanding of the code and architecture
- Explain the database design
- Explain how AI was used thoughtfully
- Discuss real lessons learned
- Avoid spending time on excuses or unfinished features
Remember: the goal is not to claim that everything is perfect. The goal is to show that you built a real, working application and that you understand how it works.
Final Presentation Rubric (May 5)
| Category | Excellent (Full Credit) | Adequate (Partial) | Needs Work (Low) | Points |
|---|---|---|---|---|
| Project Overview | Clear purpose, users, and features explained | Basic explanation; some gaps | Unclear or confusing | /10 |
| System Features | Key features clearly explained and connected | Some features explained; lacks clarity | Missing or unclear explanation | /10 |
| Database Explanation | Schema clearly explained with relationships | Basic schema explanation | Minimal or incorrect explanation | /10 |
| Architecture & API | Clear explanation of system structure and API | Partial understanding shown | Weak or incorrect explanation | /10 |
| Use of AI | Specific, thoughtful explanation of AI use and limits | General explanation | Vague or minimal discussion | /10 |
| Lessons Learned | Insightful reflection on technical + AI learning | Some reflection | Minimal or superficial | /10 |
| Demo Quality | Smooth, working demo showing key features | Demo works but limited or rough | Demo fails or unclear | /20 |
| Clarity & Organization | Well-structured, clear, within time | Some organization issues | Disorganized or over time | /10 |
| Preparedness | Well practiced; confident delivery | Some hesitation | Unprepared | /10 |
Total: /100